@react-three/postprocessing
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 |
|---|---|---|---|---|
| source-diff | obfuscated-file:dist/index.js | AI (source-diff): Vite-bundled ESM output, not obfuscation; canonical pmndrs build artifact. | ai | |
| source-diff | source-size-tripled | AI (source-diff): Bundled dist size growth on established build tool; benign. | ai | |
| provenance | no-provenance | AI (provenance): Established pmndrs ecosystem package with 119 versions and 2037-day history; lack of provenance is common and not a risk signal here. | ai |
Versions (showing 5 of 5)
| Version | Deps | Published |
|---|---|---|
| 3.0.4 | 3 / 22 | |
| 3.0.3 | 3 / 21 | |
| 3.0.2 | 3 / 22 | |
| 3.0.1 | 3 / 22 | |
| 3.0.0 | 3 / 22 |
v3.0.3
4 findingsThis version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: codyjasonbennett.
Newly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
This version was published by a different npm account (codyjasonbennett) than the most recent previously approved version (drcmda) on 2025-02-19, but codyjasonbennett is listed as a maintainer on prior approved versions (matched on name). This looks like a manual publish by a known maintainer rather than a publisher change. Recorded as INFO for audit trail.
v3.0.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.0.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.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.