@vtj/node
Supply chain provenance
Status for the latest visible version.
Without SLSA provenance there is no cryptographic link between this tarball and the public source — the axios compromise (March 2026) relied on exactly this gap.
Maintainers
Keywords
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| typosquat | typosquat.levenshtein:zod | AI (typosquat): Scoped @vtj/* package in an established low-code ecosystem; Levenshtein match to 'zod' is coincidental. | ai | |
| phantom-deps | phantom-dep:@types/fs-extra | AI (phantom-deps): @types/fs-extra is a type declaration package used at compile time, not imported at runtime; stable false positive for this package. | ai |
Versions (showing 6 of 6)
| Version | Deps | Published |
|---|---|---|
| 0.12.6 | 4 / 2 | |
| 0.12.5 | 4 / 2 | |
| 0.12.4 | 4 / 2 | |
| 0.12.3 | 4 / 2 | |
| 0.12.2 | 4 / 2 | |
| 0.12.1 | 4 / 2 |
v0.12.5
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.12.4
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.12.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.12.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.12.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.