@vtj/base
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
Keywords
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| source-diff | encoded-string-file:dist/index.cjs | AI (source-diff): Long base64 strings are RSA key constants for the package's own JSEncrypt crypto helpers, not hidden payloads. | ai | |
| source-diff | encoded-string-file:dist/index.mjs | AI (source-diff): Same RSA key constants in the ESM build; stable false positive for this package. | ai | |
| phantom-deps | phantom-dep:@types/numeral | AI (phantom-deps): Type-only package; phantom-dep false positive for this library. | ai | |
| phantom-deps | phantom-dep:@types/lodash-es | AI (phantom-deps): Type-only package; phantom-dep false positive for this library. | ai | |
| phantom-deps | phantom-dep:reflect-metadata | AI (phantom-deps): Known implicit runtime polyfill; not directly imported by convention. | ai |
Versions (showing 32 of 32)
| Version | Deps | Published |
|---|---|---|
| 0.13.1 | 0 / 12 | |
| 0.13.0 | 0 / 12 | |
| 0.12.4 | 0 / 12 | |
| 0.12.3 | 3 / 10 | |
| 0.12.2 | 3 / 10 | |
| 0.12.1 | 3 / 10 | |
| 0.12.0 | 3 / 10 | |
| 0.11.2 | 3 / 10 | |
| 0.11.1 | 3 / 10 | |
| 0.10.2 | 3 / 10 | |
| 0.10.1 | 3 / 10 | |
| 0.10.0 | 3 / 10 | |
| 0.9.5 | 3 / 11 | |
| 0.9.4 | 3 / 11 | |
| 0.9.3 | 3 / 11 | |
| 0.9.2 | 3 / 11 | |
| 0.9.1 | 3 / 11 | |
| 0.9.0 | 3 / 11 | |
| 0.8.12 | 3 / 11 | |
| 0.8.11 | 3 / 11 | |
| 0.8.10 | 3 / 11 | |
| 0.8.9 | 3 / 11 | |
| 0.8.8 | 3 / 11 | |
| 0.8.7 | 3 / 11 | |
| 0.8.6 | 3 / 11 | |
| 0.8.5 | 3 / 11 | |
| 0.8.4 | 3 / 11 | |
| 0.8.3 | 3 / 11 | |
| 0.7.3 | 3 / 9 | |
| 0.7.2 | 3 / 9 | |
| 0.7.1 | 3 / 9 | |
| 0.7.0 | 3 / 9 |
v0.13.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.12.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.11.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.11.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.10.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.10.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.10.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.9.5
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.9.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.9.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.9.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.9.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.9.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.8.12
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.8.11
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.8.10
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.8.9
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.8.8
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.8.7
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.8.6
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.8.5
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.8.4
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.8.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.7.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.7.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.7.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.7.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.