← Home

@react-foundry/docs-components

npm
11
Versions
—
License
No
Install Scripts
Missing
Provenance

Supply chain provenance

Status for the latest visible version.

No SLSA provenance npm registry signatures No source commit

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

daniel-ac-martin

Keywords

react-components

Accepted risks

Findings the reviewer chose to accept rather than block on.

SourceRuleReasonAccepted byWhen
provenance no-provenance AI (provenance): Only ~12% of npm has provenance; not a blocker for established packages with strong publisher history. ai
dependencies unvetted-dep:prismjs AI (dependencies): prismjs is a widely-used, well-maintained syntax highlighting library; no malware indicators. ai
dependencies unvetted-dep:prismjs-github AI (dependencies): prismjs-github is a standard PrismJS theme package; low risk. ai
dependencies unvetted-dep:@react-foundry/tabs AI (dependencies): Same-org package from the same publisher; consistent with the package's purpose. ai

Versions (showing 11 of 11)

Version Deps Published
0.3.0 9 / 5
0.2.1 9 / 5
0.1.9 9 / 5
0.1.7 9 / 5
0.1.6 9 / 5
0.1.5 9 / 5
0.1.4 9 / 5
0.1.3 9 / 5
0.1.2 9 / 5
0.1.1 9 / 5
0.1.0 9 / 5

v0.3.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.

v0.1.7

1 finding
LOW No provenance attestation provenance

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

v0.1.6

1 finding
LOW No provenance attestation provenance

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

v0.1.5

1 finding
LOW No provenance attestation provenance

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

v0.1.4

1 finding
LOW No provenance attestation provenance

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

v0.1.3

1 finding
LOW No provenance attestation provenance

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

v0.1.2

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.

v0.1.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.

v0.1.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.