@bondsports/date-time
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
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| phantom-deps | phantom-dep:i18n | AI (phantom-deps): Declared in dependencies; used indirectly via config and type imports. | ai | |
| phantom-deps | phantom-dep:node | AI (phantom-deps): Declared in dependencies; used indirectly in config and type references. | ai | |
| phantom-deps | phantom-dep:lodash.clonedeep | AI (phantom-deps): Declared in dependencies; used indirectly via type imports and config. | ai |
Versions (showing 9 of 9)
| Version | Deps | Published |
|---|---|---|
| 3.13.0 | 4 / 24 | |
| 2.4.59 | 3 / 24 | |
| 2.4.55 | 3 / 24 | |
| 2.4.54 | 3 / 24 | |
| 2.4.53 | 4 / 24 | |
| 2.4.52 | 4 / 24 | |
| 2.4.50 | 4 / 24 | |
| 2.4.49 | 4 / 24 | |
| 2.4.48 | 4 / 24 |
v3.13.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.4.59
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.4.55
2 findingsThis version was published by a different npm account than previous versions on 2026-03-10. This could indicate a legitimate maintainer transition or an account compromise.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.4.54
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.4.53
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.4.52
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.4.50
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.4.49
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.4.48
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.