@react-three/fiber
Supply chain provenance
Status for the latest visible version.
Without SLSA provenance there is no cryptographic link between this tarball and the public source, so a manually published version cannot be tied back to a reviewed commit.
Maintainers
Keywords
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| maintainer-change | maintainer-added | AI (maintainer-change): krispya already in maintainers list; established team member. | ai | |
| provenance | publisher-changed | AI (provenance): krispya is a listed maintainer of pmndrs/react-three-fiber; legitimate team publish. | ai | |
| source-diff | obfuscated-file:dist/events-f19bcc32.cjs.dev.js | AI (source-diff): Standard bundled CJS build output with readable imports; not obfuscated. | ai | |
| phantom-deps | phantom-dep:@types/react-reconciler | AI (phantom-deps): Type-only dependency; loaded by convention, not direct import. | ai | |
| phantom-deps | phantom-dep:@types/webxr | AI (phantom-deps): @types/webxr is a type-only ambient package legitimately declared as a dependency for TypeScript consumers; not directly imported by convention. | ai | |
| provenance | no-provenance | AI (provenance): Established pmndrs package with 288 versions; lack of Sigstore provenance is common and not a risk signal for this well-known project. | ai | |
| phantom-deps | phantom-dep:use-sync-external-store | AI (phantom-deps): use-sync-external-store is referenced via config/build tooling in a React renderer; phantom detection is a false positive for this package. | ai | |
| phantom-deps | phantom-dep:@babel/runtime | AI (phantom-deps): @babel/runtime is a build-time/runtime helper injected by Babel transforms; not directly imported in source but legitimately required. | ai |
Versions (showing 18 of 18)
| Version | Deps | Published |
|---|---|---|
| 9.6.1 | 10 / 2 | |
| 9.6.0 | 10 / 2 | |
| 9.5.0 | 10 / 2 | |
| 9.4.2 | 12 / 0 | |
| 9.4.1 | 12 / 0 | |
| 9.4.0 | 12 / 0 | |
| 9.3.0 | 12 / 0 | |
| 9.2.0 | 12 / 0 | |
| 9.1.4 | 12 / 0 | |
| 9.1.3 | 12 / 0 | |
| 9.1.2 | 12 / 0 | |
| 9.1.1 | 12 / 0 | |
| 9.1.0 | 12 / 0 | |
| 9.0.4 | 12 / 0 | |
| 9.0.3 | 12 / 0 | |
| 9.0.2 | 12 / 0 | |
| 9.0.1 | 12 / 0 | |
| 9.0.0 | 11 / 0 |
v9.1.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v9.1.1
2 findingsThis version was published by a different npm account than previous versions on 2025-03-31. This could indicate a legitimate maintainer transition or an account compromise.
[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v9.1.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v9.0.4
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v9.0.3
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v9.0.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v9.0.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v9.0.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.