@agent-vm/tool-portal
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 |
|---|---|---|---|---|
| source-diff | obfuscated-file:dist/index2.d.ts | AI (source-diff): Type-declaration rollup with long re-export lines, not obfuscated code. | ai | |
| source-diff | source-size-tripled | AI (source-diff): New standalone-entrypoint bundle explains size growth, matches added exports. | ai |
Versions (showing 18 of 18)
| Version | Deps | Published |
|---|---|---|
| 0.0.126 | 7 / 1 | |
| 0.0.125 | 7 / 1 | |
| 0.0.124 | 7 / 1 | |
| 0.0.123 | 7 / 1 | |
| 0.0.122 | 7 / 1 | |
| 0.0.121 | 7 / 1 | |
| 0.0.120 | 7 / 1 | |
| 0.0.119 | 7 / 1 | |
| 0.0.118 | 7 / 1 | |
| 0.0.117 | 7 / 1 | |
| 0.0.116 | 7 / 1 | |
| 0.0.115 | 7 / 1 | |
| 0.0.114 | 5 / 1 | |
| 0.0.113 | 5 / 1 | |
| 0.0.112 | 5 / 1 | |
| 0.0.111 | 5 / 1 | |
| 0.0.110 | 5 / 1 | |
| 0.0.109 | 5 / 1 |
v0.0.126
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.125
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.124
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.123
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.122
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.121
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.120
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.119
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.118
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.117
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.116
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.115
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.0.114
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.113
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.112
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.111
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.110
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.109
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.