← Home

@react-spring/rafz

npm Repository Homepage

react-spring's fork of rafz one frameloop to rule them all

5
Versions
MIT
License
No
Install Scripts
Verified
Provenance

Supply chain provenance

Status for the latest visible version.

SLSA provenance attestation npm registry signatures No source commit

Maintainers

tdfka_rick

Keywords

animatedanimationhooksmotionreactreact-nativespringtypescriptvelocity

Accepted risks

Findings the reviewer chose to accept rather than block on.

SourceRuleReasonAccepted byWhen
provenance publisher-changed AI (provenance): Legitimate migration from manual publish to GitHub Actions CI/CD with SLSA provenance. ai
provenance missing-githead AI (provenance): Expected when switching to GitHub Actions publish workflow; SLSA provenance compensates. ai
publish-pattern dormant-publish AI (publish-pattern): Mature monorepo package; dormancy is normal for stable libraries. ai

Versions (showing 5 of 5)

Version Deps Published
10.1.0 0 / 0
10.0.4 0 / 0
10.0.3 0 / 0
10.0.2 0 / 0
10.0.1 0 / 0

v10.1.0

2 findings
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.

INFO Missing gitHead — previous versions had it provenance

[Accepted risk] This version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: GitHub Actions.

v10.0.4

3 findings
HIGH Missing gitHead — previous versions had it provenance

This version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: GitHub Actions.

HIGH Publisher changed: tdfka_rick → GitHub Actions (on 2026-05-21) provenance

This version was published by a different npm account than previous versions on 2026-05-21. 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.

v10.0.2

1 finding
LOW No provenance attestation provenance

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

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