sbt is an interactive build tool
88%
Total Score
healthy
Active releases, strong project activity, and signed provenance outweigh the prerelease status and mostly unpinned workflow actions.
The repository name does not match this artifact and its README does not mention the package, which is a caution under the package-ownership check; the sbt organization and repository context partly reduce the concern because this appears consistent with a monorepo component.
The repository has no published security policy, which is a transparency gap for a widely used build tool, though active maintenance and dependency scanning partly compensate.
This release is a prerelease RC, so compatibility may still change, although the package is on a stable major line and prereleases are a regular part of recent development.
All 8 workflows were analyzed without audit findings or untrusted checkout/script-injection issues, and 5 use read-only permissions. However, 25 of 26 action references are unpinned, and 2 workflows grant top-level write access, creating workflow supply-chain and permission-hygiene concerns.
| Title | Versions | Severity |
|---|---|---|
AIKIDO-2026-824110 main_3 is vulnerable to Remote Code Execution in versions 2.0.0 - 2.0.5. | 2.0.0 - 2.0.5 | Critical |
No maintainer information available.
| Dependency | Last Release | Score |
|---|---|---|
org.scala-sbt:actions_3 Version 2.1.0-RC1 | — | — |
org.scala-sbt:build-file_3 Version 2.1.0-RC1 | — | — |
org.scala-sbt:main-settings_3 Version 2.1.0-RC1 | — | — |
org.scala-sbt:run_3 Version 2.1.0-RC1 | — | — |
org.scala-sbt:command_3 Version 2.1.0-RC1 | — | — |
Connect your repositories to instantly see whether vulnerable or malicious packages exist in your codebase.
Free. No credit card required.

I consent to receiving marketing communications based on Aikido’s Privacy Policy.
SOC 2Compliant
ISO 27001Compliant
ISO 42001Compliant© All Intel data is openly available and commercially licensed.