@pixi/core
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
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| typosquat | typosquat.levenshtein:cors | AI (typosquat): Legitimate PixiJS scoped package; Levenshtein match to 'cors' is a false positive. | ai | |
| semgrep | semgrep:new-function-constructor | AI (semgrep): new Function() used for WebGL uniform buffer sync code generation; established PixiJS pattern, not malicious. | ai |
Versions (showing 23 of 23)
| Version | Deps | Published |
|---|---|---|
| 7.4.3 | 8 / 0 | |
| 7.4.2 | 8 / 0 | |
| 7.4.0 | 8 / 0 | |
| 7.3.3 | 9 / 0 | |
| 7.3.2 | 9 / 0 | |
| 7.3.1 | 9 / 0 | |
| 7.3.0 | 9 / 0 | |
| 7.2.4 | 9 / 0 | |
| 7.2.3 | 9 / 0 | |
| 7.2.2 | 9 / 0 | |
| 7.2.1 | 9 / 0 | |
| 7.2.0 | 9 / 0 | |
| 7.1.4 | 8 / 0 | |
| 7.1.3 | 8 / 0 | |
| 7.1.2 | 8 / 0 | |
| 7.1.1 | 8 / 0 | |
| 7.1.0 | 8 / 0 | |
| 7.0.5 | 8 / 0 | |
| 7.0.4 | 8 / 0 | |
| 7.0.3 | 8 / 0 | |
| 7.0.2 | 8 / 0 | |
| 7.0.1 | 8 / 0 | |
| 7.0.0 | 8 / 0 |
v7.4.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v7.3.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v7.3.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v7.3.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v7.3.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v7.2.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v7.2.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v7.2.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v7.2.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v7.2.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v7.1.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v7.1.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v7.1.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v7.1.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v7.1.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v7.0.5
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v7.0.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v7.0.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v7.0.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v7.0.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v7.0.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.