date-vir
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 |
|---|---|---|---|---|
| phantom-deps | phantom-dep:@types/luxon | AI (phantom-deps): @types/luxon is a TypeScript type package for luxon which is a direct runtime dep; phantom-dep false positive for this package. | ai | |
| license | uncommon-license:CC0 1.0 | AI (license): Package uses MIT or CC0 1.0 dual license; both are permissive and well-understood. | ai |
Versions (showing 7 of 7)
| Version | Deps | Published |
|---|---|---|
| 8.3.2 | 7 / 11 | |
| 8.3.1 | 7 / 11 | |
| 8.2.1 | 7 / 11 | |
| 8.2.0 | 7 / 11 | |
| 8.1.1 | 7 / 11 | |
| 8.1.0 | 7 / 11 | |
| 8.0.0 | 7 / 11 |
v8.3.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v8.3.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v8.2.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v8.2.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v8.1.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v8.1.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v8.0.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.