react-native-worklets
The React Native multithreading library
Supply chain provenance
Status for the latest visible version.
Maintainers
Keywords
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| semgrep | semgrep:eval-usage | AI (semgrep): eval() is the core mechanism of the worklets runtime — it evaluates serialized worklet functions on background threads. This is the intentional, documented design of the library, not a supply-chain risk. | ai | |
| semgrep | semgrep:dynamic-require | AI (semgrep): Dynamic require in validate-react-native-version.js loads a local package.json via __dirname-relative path for version validation. Benign build/validation script pattern. | ai | |
| phantom-deps | phantom-dep:@babel/plugin-transform-classes | AI (phantom-deps): Babel transform plugins are loaded by convention through the Babel plugin system, not via direct imports. Standard pattern for Babel-based tooling. | ai | |
| phantom-deps | phantom-dep:@babel/plugin-transform-unicode-regex | AI (phantom-deps): Babel transform plugins are loaded by convention through the Babel plugin system, not via direct imports. Standard pattern for Babel-based tooling. | ai | |
| phantom-deps | phantom-dep:@babel/plugin-transform-class-properties | AI (phantom-deps): Babel transform plugins are loaded by convention through the Babel plugin system, not via direct imports. Standard pattern for Babel-based tooling. | ai |
Versions (showing 20 of 20)
| Version | Deps | Published |
|---|---|---|
| 0.9.1 | 11 / 18 | |
| 0.9.0 | 11 / 18 | |
| 0.8.3 | 11 / 20 | |
| 0.8.2 | 11 / 20 | |
| 0.7.4 | 11 / 18 | |
| 0.7.3 | 11 / 18 | |
| 0.7.2 | 11 / 18 | |
| 0.7.1 | 11 / 18 | |
| 0.7.0 | 11 / 18 | |
| 0.6.1 | 11 / 18 | |
| 0.6.0 | 11 / 18 | |
| 0.5.2 | 11 / 18 | |
| 0.5.1 | 11 / 18 | |
| 0.5.0 | 11 / 18 | |
| 0.4.2 | 10 / 18 | |
| 0.4.1 | 10 / 18 | |
| 0.4.0 | 10 / 18 | |
| 0.3.0 | 10 / 18 | |
| 0.2.0 | 0 / 16 | |
| 0.1.0 | 0 / 16 |
v0.9.1
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.9.0
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.8.3
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.8.2
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.7.4
2 findingsThis version was published without provenance, but prior versions were published via CI/CD with attestations. This is a strong signal of a potential account compromise or unauthorized publish. The axios attack (March 2026) exhibited exactly this pattern.
This version was published by a different npm account than previous versions on 2026-02-16. This could indicate a legitimate maintainer transition or an account compromise.
v0.7.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.7.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.7.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.7.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.6.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.6.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.5.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.5.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.5.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.4.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.4.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.4.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.3.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.2.0
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.1.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.