← Home

@times-components/article-main-comment

npm Repository Homepage

Main Comment Article Template

11
Versions
BSD-3-Clause
License
No
Install Scripts
Missing
Provenance

Supply chain provenance

Status for the latest visible version.

No SLSA provenance npm registry signatures gitHead linked

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

marcincubernewsuknews-tools

Keywords

reactarticle-main-commentcomponent

Accepted risks

Findings the reviewer chose to accept rather than block on.

SourceRuleReasonAccepted byWhen
phantom-deps phantom-dep:@times-components/ad AI (phantom-deps): Same-org monorepo dep; used transitively, not a phantom in the malicious sense. ai
phantom-deps phantom-dep:@times-components/responsive AI (phantom-deps): Same-org monorepo dep; used transitively, not a phantom in the malicious sense. ai
phantom-deps phantom-dep:@times-components/user-state AI (phantom-deps): Same-org monorepo dep; used transitively, not a phantom in the malicious sense. ai

Versions (showing 11 of 112)

Version Deps Published
2.99.6 15 / 19
2.99.5 15 / 19
2.99.4 15 / 19
2.99.3 15 / 19
2.99.2 15 / 19
2.99.1 15 / 19
2.99.0 15 / 19
2.98.0 15 / 19
2.97.5 15 / 19
2.97.4 15 / 19
2.97.3 15 / 19

v2.99.6

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v2.99.5

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v2.99.4

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v2.99.3

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v2.99.2

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v2.99.1

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v2.99.0

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v2.98.0

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v2.97.5

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v2.97.4

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v2.97.3

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.