@google/adk-devtools
Google ADK JS Development Tools
Supply chain provenance
Status for the latest visible version.
Without SLSA provenance there is no cryptographic link between this tarball and the public source, so a manually published version cannot be tied back to a reviewed commit.
Maintainers
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| phantom-deps | phantom-dep:esbuild-shim-plugin | AI (phantom-deps): Used by build config. | ai | |
| source-diff | obfuscated-file:dist/cli_entrypoint.mjs | AI (source-diff): esbuild bundle output for CLI entrypoint, not obfuscation. | ai | |
| phantom-deps | phantom-dep:cors | AI (phantom-deps): Used via config/runtime, not a real gap. | ai | |
| phantom-deps | phantom-dep:esbuild | AI (phantom-deps): Known implicit runtime dep. | ai | |
| phantom-deps | phantom-dep:@clack/prompts | AI (phantom-deps): Config-referenced CLI dep. | ai | |
| phantom-deps | phantom-dep:@mikro-orm/mssql | AI (phantom-deps): Optional DB driver declared as runtime dep for user selection; not directly imported by the package itself. | ai | |
| phantom-deps | phantom-dep:@mikro-orm/mysql | AI (phantom-deps): Optional DB driver declared as runtime dep for user selection; not directly imported by the package itself. | ai | |
| phantom-deps | phantom-dep:@mikro-orm/sqlite | AI (phantom-deps): Optional DB driver declared as runtime dep for user selection; not directly imported by the package itself. | ai | |
| phantom-deps | phantom-dep:@mikro-orm/mariadb | AI (phantom-deps): Optional DB driver declared as runtime dep for user selection; not directly imported by the package itself. | ai | |
| phantom-deps | phantom-dep:@mikro-orm/postgresql | AI (phantom-deps): Optional DB driver declared as runtime dep for user selection; not directly imported by the package itself. | ai |
Versions (showing 17 of 17)
| Version | Deps | Published |
|---|---|---|
| 1.4.0 | 19 / 12 | |
| 1.3.0 | 19 / 12 | |
| 1.2.0 | 19 / 11 | |
| 1.1.0 | 19 / 11 | |
| 1.0.0 | 19 / 11 | |
| 0.6.1 | 19 / 11 | |
| 0.6.0 | 19 / 11 | |
| 0.5.0 | 19 / 11 | |
| 0.4.0 | 15 / 11 | |
| 0.3.0 | 9 / 11 | |
| 0.2.5 | 9 / 11 | |
| 0.2.4 | 9 / 11 | |
| 0.2.3 | 9 / 11 | |
| 0.2.2 | 9 / 11 | |
| 0.2.1 | 8 / 11 | |
| 0.2.0 | 8 / 11 | |
| 0.1.3 | 8 / 11 |
v1.4.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.6.0
2 findingsNewly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.5.0
2 findingsNewly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.4.0
2 findingsNewly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator. Artifact: bundled (esbuild) — bundler banner in the scanned head, but the file is larger than the scan window and its remainder is unclassified, so this is not a clean bill of health.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.3.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.2.5
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.2.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.2.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.2.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.2.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.2.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.