@blueprintjs/datetime2
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 |
|---|---|---|---|---|
| publish-pattern | new-deps-added | AI (publish-pattern): New deps are same-org @blueprintjs/* packages; no third-party supply chain risk. | ai | |
| phantom-deps | phantom-dep:tslib | AI (phantom-deps): tslib is a known implicit runtime dep for TypeScript compiled packages; stable FP for this package. | ai | |
| phantom-deps | phantom-dep:date-fns | AI (phantom-deps): date-fns referenced in config files; re-export package pattern makes direct import detection unreliable. | ai | |
| phantom-deps | phantom-dep:@blueprintjs/core | AI (phantom-deps): Same-org monorepo sibling; phantom-dep heuristic is unreliable for re-export packages. | ai | |
| phantom-deps | phantom-dep:@blueprintjs/icons | AI (phantom-deps): Same-org monorepo sibling; stable FP for this package. | ai | |
| phantom-deps | phantom-dep:@blueprintjs/colors | AI (phantom-deps): Same-org monorepo sibling; stable FP for this package. | ai |
Versions (showing 26 of 26)
| Version | Deps | Published |
|---|---|---|
| 3.1.1 | 7 / 7 | |
| 3.1.0 | 7 / 7 | |
| 3.0.24 | 7 / 7 | |
| 3.0.23 | 7 / 7 | |
| 3.0.22 | 7 / 7 | |
| 3.0.21 | 7 / 7 | |
| 3.0.20 | 7 / 7 | |
| 3.0.19 | 7 / 7 | |
| 3.0.18 | 7 / 7 | |
| 3.0.17 | 7 / 7 | |
| 3.0.16 | 7 / 7 | |
| 3.0.15 | 7 / 7 | |
| 3.0.14 | 7 / 7 | |
| 3.0.13 | 7 / 7 | |
| 3.0.12 | 7 / 7 | |
| 3.0.11 | 7 / 7 | |
| 3.0.10 | 7 / 7 | |
| 3.0.9 | 7 / 7 | |
| 3.0.8 | 7 / 7 | |
| 3.0.6 | 5 / 6 | |
| 3.0.5 | 5 / 6 | |
| 3.0.4 | 5 / 6 | |
| 3.0.3 | 5 / 6 | |
| 3.0.2 | 5 / 6 | |
| 3.0.1 | 5 / 6 | |
| 3.0.0 | 5 / 6 |
v3.1.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.1.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.0.24
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.0.23
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.0.22
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.0.21
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.0.20
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.0.19
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.0.18
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.0.17
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.0.16
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.0.15
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.0.14
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.0.13
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.0.12
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.0.11
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.0.10
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.0.9
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.0.8
2 findingsThis version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: blueprintjs.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.0.6
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.0.5
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.0.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.0.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.0.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.0.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.0.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.