@times-components/utils
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 |
|---|---|---|---|---|
| provenance | no-provenance | AI (provenance): Established monorepo package; lack of provenance is consistent across all versions and not a risk indicator here. | ai | |
| publish-pattern | dormant-publish | AI (publish-pattern): Publisher has 22 approved packages, no rejections, and this version has no material changes vs prior approved release. | ai |
Versions (showing 7 of 7)
| Version | Deps | Published |
|---|---|---|
| 6.43.0 | 11 / 13 | |
| 6.37.0 | 11 / 13 | |
| 6.36.2 | 11 / 13 | |
| 6.36.1 | 11 / 13 | |
| 6.35.1 | 11 / 13 | |
| 6.34.2 | 11 / 13 | |
| 6.31.8 | 11 / 13 |
v6.43.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.37.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.36.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.36.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.35.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.34.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v6.31.8
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.