sbt is an interactive build tool
88%
Total Score
100
100
94
75
100
The repository name does not match this artifact and its README does not mention the package. This may be normal for an sbt monorepo, but the lack of an explicit package reference warrants caution about source-to-artifact traceability.
No repository security policy was found, leaving disclosure and response guidance less transparent despite the project's otherwise active maintenance.
All eight workflows were analyzed with no audit findings or untrusted checkout/script-injection paths, and five use read-only permissions. However, 25 of 26 action references are unpinned and two workflows have top-level write permissions, creating a moderate reproducibility and token-scope hygiene concern.
| Title | Versions | Severity |
|---|---|---|
AIKIDO-2026-191613 main_2.12 is vulnerable to Remote Code Execution in versions 1.1.0 - 1.12.14. | 1.1.0 - 1.12.14 | Critical |
No maintainer information available.
| Dependency | Last Release | Score |
|---|---|---|
org.scala-lang:scala-library Version 2.12.21 | — | — |
org.scala-sbt:logic_2.12 Version 1.12.15 | — | — |
org.scala-sbt:actions_2.12 Version 1.12.15 | — | — |
org.scala-sbt:main-settings_2.12 Version 1.12.15 | — | — |
org.scala-sbt:run_2.12 Version 1.12.15 | — | — |
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.