← Home

@ornikar/repo-config-react

npm Repository

🔧⚛️ react repo config

5
Versions
ISC
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

abarreir-ornikar

Accepted risks

Findings the reviewer chose to accept rather than block on.

SourceRuleReasonAccepted byWhen
phantom-deps phantom-dep:svgo AI (phantom-deps): Config-tool package; svgo referenced in config files, not imported directly — stable false positive. ai
phantom-deps phantom-dep:cross-env AI (phantom-deps): Config-tool package; cross-env referenced in config files, not imported directly — stable false positive. ai

Versions (showing 5 of 5)

Version Deps Published
13.0.6 3 / 0
13.0.5 3 / 0
13.0.2 3 / 0
13.0.1 3 / 0
13.0.0 3 / 0

v13.0.6

1 finding
LOW No provenance attestation provenance

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

v13.0.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.

v13.0.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.

v13.0.1

1 finding
LOW No provenance attestation provenance

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

v13.0.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.