@nativescript/canvas-pixi
Plugin for using pixi.js in NativeScript
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 |
|---|---|---|---|---|
| phantom-deps | phantom-dep:pixi-filters | AI (phantom-deps): Referenced in config files as peer/re-export deps; not directly imported by design in this plugin. | ai | |
| phantom-deps | phantom-dep:pixi.js-legacy | AI (phantom-deps): Same pattern — declared for consumer use, referenced in config, not directly imported. | ai |
Versions (showing 35 of 35)
| Version | Deps | Published |
|---|---|---|
| 2.1.16 | 4 / 0 | |
| 2.1.15 | 4 / 0 | |
| 2.1.13 | 4 / 0 | |
| 2.1.12 | 4 / 0 | |
| 2.1.11 | 4 / 0 | |
| 2.1.10 | 4 / 0 | |
| 2.1.7 | 4 / 0 | |
| 2.1.2 | 4 / 0 | |
| 2.1.1 | 4 / 0 | |
| 2.1.0 | 4 / 0 | |
| 2.0.32 | 4 / 0 | |
| 2.0.31 | 4 / 0 | |
| 2.0.30 | 4 / 0 | |
| 2.0.29 | 4 / 0 | |
| 2.0.28 | 4 / 0 | |
| 2.0.27 | 4 / 0 | |
| 2.0.26 | 4 / 0 | |
| 2.0.25 | 4 / 0 | |
| 2.0.24 | 4 / 0 | |
| 2.0.23 | 4 / 0 | |
| 2.0.22 | 4 / 0 | |
| 2.0.20 | 4 / 0 | |
| 2.0.18 | 4 / 0 | |
| 2.0.16 | 4 / 0 | |
| 2.0.14 | 4 / 0 | |
| 2.0.12 | 4 / 0 | |
| 2.0.11 | 4 / 0 | |
| 2.0.8 | 4 / 0 | |
| 2.0.7 | 4 / 0 | |
| 2.0.6 | 4 / 0 | |
| 2.0.4 | 4 / 0 | |
| 2.0.3 | 4 / 0 | |
| 2.0.2 | 4 / 0 | |
| 2.0.1 | 4 / 0 | |
| 2.0.0 | 4 / 0 |
v2.1.16
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v2.1.15
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v2.1.13
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v2.1.12
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v2.1.11
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v2.1.10
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v2.1.7
2 findingsPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
This version was published by a different npm account (GitHub Actions) than the most recent previously approved version (nativescript-bot) on 2026-07-10, but it carries Sigstore provenance attestation. This means the package moved to a trusted publisher (CI/CD with OIDC, e.g. GitHub Actions) — a supply-chain integrity improvement, not a compromise, since a stolen npm token cannot forge provenance bound to the source repository. Recorded as INFO for audit trail.
v2.1.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.1.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.0.32
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.0.31
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.0.30
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.