@times-components/article-skeleton
The article skeleton
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:mockdate | AI (phantom-deps): mockdate is explicitly listed in both devDependencies and dependencies in package.json; not a true phantom dep. | ai |
Versions (showing 7 of 112)
| Version | Deps | Published |
|---|---|---|
| 1.165.2 | 32 / 26 | |
| 1.165.1 | 32 / 26 | |
| 1.165.0 | 32 / 26 | |
| 1.164.1 | 32 / 26 | |
| 1.164.0 | 32 / 26 | |
| 1.163.0 | 32 / 26 | |
| 1.162.3 | 32 / 26 |
v1.165.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.165.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.165.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.164.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.164.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.163.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.162.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.