← Home

@scalprum/react-core

6
Versions
License
No
Install Scripts
Verified
Provenance

Supply chain provenance

Status for the latest visible version.

SLSA provenance attestation npm registry signatures gitHead linked

Maintainers

hyperkidkarelhalachmulder

Accepted risks

Findings the reviewer chose to accept rather than block on.

SourceRuleReasonAccepted byWhen
provenance publisher-changed AI (provenance): Transition from human publisher to GitHub Actions CI/CD with SLSA attestation is a legitimate and expected supply chain improvement. ai
publish-pattern dormant-publish AI (publish-pattern): Dormancy followed by CI/CD-published release with SLSA provenance; consistent with a legitimate pipeline migration rather than account takeover. ai
provenance no-provenance AI (provenance): Long-lived scalprum monorepo package; provenance not historically provided, stable false positive. ai

Versions (showing 6 of 6)

Version Deps Published
0.11.2 3 / 2
0.11.1 3 / 2
0.11.0 3 / 2
0.10.2 3 / 2
0.10.1 3 / 2
0.10.0 3 / 2

v0.11.2

2 findings
HIGH Publisher changed: hyperkid → GitHub Actions (on 2026-05-11) provenance

This version was published by a different npm account than previous versions on 2026-05-11. This could indicate a legitimate maintainer transition or an account compromise.

INFO Has SLSA provenance attestation provenance

Published via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.

v0.11.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.11.0

1 finding
INFO No provenance attestation provenance

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

v0.10.2

1 finding
INFO No provenance attestation provenance

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

v0.10.1

1 finding
INFO No provenance attestation provenance

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

v0.10.0

1 finding
INFO No provenance attestation provenance

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