Credential access
Reads credentials files, environment variables, and repository config.
brew / rank 765
Install sbt with Homebrew, chocolatey, MacPorts, Nix, pacman, scoop, winget
Build tool for Scala projects. Version 2.0.9 via Homebrew; verified 2026-09-14. Also installable with nix: nix profile install nixpkgs#sbt.
agent safety
Agent safety answer
sbt builds Scala projects and can publish artifacts to repositories.
Remote mutation
Can run tasks and plugins that publish or call remote services.
Publish/artifact risk
Can publish jars, plugins, and release metadata.
Recommended control
Gate publish, release, and credentialed repository tasks.
Agent-use guidance
Allow compile/test; require approval for publish, release, and secret-backed tasks.
install
Additional install commands
macOS
Homebrewverified · 100%
brew install sbtlocal Homebrew formula metadata
MacPortsverified · 94%
sudo port install sbtMacPorts ports tree · devel/sbt/Portfile · source: api.github.com
Linux
Nixverified · 92%
nix profile install nixpkgs#sbtnixpkgs package indexes · pkgs/by-name/sb/sbt/package.nix · source: api.github.com
Arch Linux pacmanverified · 92%
sudo pacman -S sbtArch Linux sync databases · sbt · source: geo.mirror.pkgbuild.com
Windows
Chocolateyverified · 92%
choco install sbtChocolatey community package catalog · sbt · source: community.chocolatey.org
Scoopverified · 92%
scoop install main/sbtScoop official bucket manifest trees · bucket/sbt.json · source: api.github.com
Windows Package Managerverified · 92%
winget install --id sbt.sbt -eWindows Package Manager source index · sbt.sbt · source: cdn.winget.microsoft.com
overview
Package summary
Build tool for Scala projects
Project links
Commands and aliases
- sbt
history
Project history and usage
sbt is an interactive, extensible build tool for Scala and other JVM projects. A build is normally checked into the project as build.sbt plus supporting files under project/, while user-wide settings live under ~/.sbt.
Project history
sbt evolved as a JVM build tool centered on Scala projects. Its long-running 0.x line was followed by sbt 1.x, whose reference documentation records migration from 0.13 and continued changes across the 1.x series.
Adoption history
sbt became closely associated with Scala development and is distributed by numerous operating-system package managers. Its plugin ecosystem and support for Java and Scala sources broaden its role beyond a simple Scala compiler front end.
How it is used
Developers commonly run sbt interactively or invoke commands such as compile, test, run, package, and publish from a project base directory. Dependencies, plugins, repositories, credentials, and custom tasks are expressed through the build definition and supporting files.
Why package nerds care
sbt is notable for treating a build as a programmable, scoped graph of settings and tasks. Package enthusiasts also encounter its layered caches, launcher configuration, project-local build definition, global settings, plugin resolution, and repository credentials—details that strongly affect reproducibility and CI behavior.
Timeline
- 2017: The sbt 1.0 release line succeeded the widely used 0.13 series.
- Current 1.x era: The project maintains a versioned reference manual and migration documentation.
Related projects
- Scala is sbt's primary language ecosystem.
- Ivy-compatible and Maven repositories supply dependencies.
- sbt plugins extend the build definition and participate in their own dependency graph.
Sources
security posture
Risk level: yellow
generalized runtime or code generation signal.
Risk classifier
yellow risk · medium confidence · runtime
Why
- generalized runtime or code generation signal
Signals
- text:build tool
Install behavior
- No Homebrew post-install hook is recorded in formula metadata.
- Homebrew bottle metadata is available for 1 platform targets.
- Installs with 1 runtime dependencies.
Recommended review
Before unattended agent use, check whether the tool reads plaintext credentials, writes remote state, publishes artifacts, or shells out to plugins.
local files
Configuration and credential file locations
These source-backed paths show where this package keeps local settings or durable credentials. Automic Vault can use them as review targets for secret scanning, migration, and command approval.
Configuration files
Config paths the tool may read or write during local use.
- Unix
./build.sbt./*.sbt./project/*.sbt./project/*.scala~/.sbt/1.0/global.sbt~/.sbt/1.0/*.sbt~/.sbt/repositories
Credential files
Credential-bearing paths to review before unattended agent runs.
- Unix
~/.sbt/.credentials
executables
Installed executables
| Command | Kind | Exposure | Note |
|---|---|---|---|
sbt | cli | global executable |
freshness
Version and freshness
These signals separate page generation age, package-manager activity, and upstream release comparison. Version lag is warned only when an evidence URL and comparable versions are present.
page generated2026-09-19
manager version2.0.9
manager updated2026-09-14
local dataok
upstreamnot checked
latest detectednot detected
- infoNo cached GitHub release or tag data was available.https://github.com/sbt/sbtnone confidence
install metadata
Package metadata
| Package key | brew:sbt |
|---|---|
| Version | 2.0.9 |
| Package manager | Homebrew |
| Package manager page | https://formulae.brew.sh/formula/sbt |
| Homepage | https://www.scala-sbt.org/ |
| Repository | https://github.com/sbt/sbt |
| Upstream docs | https://www.scala-sbt.org/ |
| License | Apache-2.0 |
| Source archive | https://github.com/sbt/sbt/releases/download/v2.0.8/sbt-2.0.8.tgz |
| Last updated | 2026-09-14T09:52:54Z |
| Pulse | updated |
| Dependencies | openjdk |
| Bottle | available (on all) |
| Homebrew post-install | not defined |
| Service | none declared |
| Caveats | You can use $SBT_OPTS to pass additional JVM options to sbt. Project specific options should be placed in .sbtopts in the root of your project. Global settings should be placed in $HOMEBREW_PREFIX/etc/sbtopts The installation does not include `sbtn`. |
registry facts
Source database details
| Source Database | Homebrew formula API |
|---|---|
| Tap | homebrew/core |
| Full Name | sbt |
| Aliases |
|
| Version Scheme | 0 |
| Revision | 0 |
| Bottle Stable Root URL | https://ghcr.io/v2/homebrew/core |
| Deprecated | no |
| Disabled | no |
| Keg Only | no |
| URL Keys |
|
source database matches
Other package-manager records
Matches are pulled from external package-manager indexes and kept separate from local Automic Vault package links.
Nix95%
sbt
nix profile install nixpkgs#sbt- normalized package name match
- Matched by: Sbt
pacman95%
sbt 1:2.0.6-1
The interactive build tool
sudo pacman -S sbt- License: Apache-2.0
- Architecture: any
- 2 dependencies
- 1 optional deps
- normalized package name match
- Matched by: Sbt
MacPorts95%
sbt
sudo port install sbt- normalized package name match
- Matched by: Sbt
Chocolatey95%
sbt
choco install sbt- normalized package name match
- Matched by: Sbt
Scoop95%
main/sbt
scoop install main/sbt- normalized package name match
- Matched by: Sbt
winget95%
sbt.sbt
winget install --id sbt.sbt -e- normalized package name match
- Matched by: Sbt
source trail
Generated from repository data
This page is generated by av-web from the private package SQLite artifact built by scripts/generate-pkg-sqlite.py.
Combined YAML source
View the package source record on GitHub.
Used sources
- Geiger risk classifier
- cross-ecosystem install command graph
- curated agent safety answer
- curated configuration and credential file locations
- curated package history
- external package-manager database matches
- package relationship graph
- package version freshness
- package-page enrichment
- pkg.so package database
- pkgdb category and tag curation