@times-components/article-main-standard
Main Standard Article Template
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 |
|---|---|---|---|---|
| dependencies | unvetted-dep:@times-components/article-skeleton | AI (dependencies): Sibling package from the same times-components monorepo; not an independent third-party risk. | ai | |
| provenance | no-provenance | AI (provenance): Established monorepo package; provenance not used across the @times-components ecosystem. | ai |
Versions (showing 10 of 114)
| Version | Deps | Published |
|---|---|---|
| 3.108.5 | 17 / 18 | |
| 3.108.4 | 17 / 18 | |
| 3.108.3 | 17 / 18 | |
| 3.108.2 | 17 / 18 | |
| 3.108.1 | 17 / 18 | |
| 3.108.0 | 17 / 18 | |
| 3.107.0 | 17 / 18 | |
| 3.106.5 | 17 / 18 | |
| 3.106.4 | 17 / 18 | |
| 3.106.3 | 17 / 18 |
v3.108.5
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.108.4
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.108.3
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.108.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.108.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.108.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.107.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.106.5
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.106.4
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.106.3
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.