@terminal3/verify_vc_core
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 |
|---|---|---|---|---|
| bogus-package | bogus-package | AI (bogus-package): Internal org package; missing metadata is consistent across all @terminal3/* packages, not a spam/malware indicator. | ai | |
| npm-metadata | no-description | AI (npm-metadata): Stable pattern across this org's packages; not indicative of malice. | ai | |
| phantom-deps | phantom-dep:ethers | AI (phantom-deps): Declared in package.json dependencies; heuristic false positive for this package. | ai | |
| phantom-deps | phantom-dep:did-jwt | AI (phantom-deps): Declared in package.json dependencies; heuristic false positive for this package. | ai | |
| phantom-deps | phantom-dep:@noble/curves | AI (phantom-deps): Declared in package.json dependencies; heuristic false positive for this package. | ai |
Versions (showing 24 of 24)
| Version | Deps | Published |
|---|---|---|
| 0.0.37 | 5 / 0 | |
| 0.0.36 | 5 / 0 | |
| 0.0.34 | 5 / 0 | |
| 0.0.33 | 5 / 0 | |
| 0.0.32 | 5 / 0 | |
| 0.0.31 | 5 / 0 | |
| 0.0.30 | 5 / 0 | |
| 0.0.29 | 5 / 0 | |
| 0.0.28 | 5 / 0 | |
| 0.0.27 | 5 / 0 | |
| 0.0.26 | 5 / 0 | |
| 0.0.25 | 5 / 0 | |
| 0.0.24 | 5 / 0 | |
| 0.0.23 | 5 / 0 | |
| 0.0.22 | 5 / 0 | |
| 0.0.19 | 5 / 0 | |
| 0.0.17 | 5 / 0 | |
| 0.0.16 | 5 / 0 | |
| 0.0.15 | 5 / 0 | |
| 0.0.14 | 5 / 0 | |
| 0.0.13 | 5 / 0 | |
| 0.0.12 | 5 / 0 | |
| 0.0.11 | 5 / 0 | |
| 0.0.10 | 5 / 1 |
v0.0.24
2 findingsThis version was published by a different npm account (phuc-t3) than the most recent previously approved version (nik-t3) on 2025-05-09. It has since remained available on npm for 435 days without being unpublished, which is inconsistent with an account takeover — those are typically removed by npm shortly after discovery.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.23
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.22
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.19
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.17
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.16
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.15
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.14
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.13
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.12
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.11
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.10
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.