@pixi/react
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): Known pixijs org maintainer transition, not a takeover indicator. | ai | |
| publish-pattern | new-deps-added | AI (publish-pattern): its-fine/react-reconciler are standard, well-known React internals deps. | ai | |
| phantom-deps | phantom-dep:lodash.isnil | AI (phantom-deps): Config-only references in established package; stable pattern. | ai | |
| phantom-deps | phantom-dep:lodash.times | AI (phantom-deps): Config-only references in established package; stable pattern. | ai | |
| phantom-deps | phantom-dep:performance-now | AI (phantom-deps): Config-only references in established package; stable pattern. | ai |
v8.0.4
3 findingsThis version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: bigtimebuddy.
This version was published by a different npm account than previous versions on 2025-11-18. This could indicate a legitimate maintainer transition or an account compromise.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.