@esotericsoftware/spine-pixi-v8
The official Spine Runtimes for PixiJS v8.
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 |
|---|---|---|---|---|
| source-diff | obfuscated-file:dist/assets/atlasLoader.js | AI (source-diff): Minified build output from official Spine Runtimes; stable pattern for this package. | ai | |
| source-diff | obfuscated-file:dist/assets/skeletonLoader.js | AI (source-diff): Minified build output from official Spine Runtimes; stable pattern for this package. | ai | |
| source-diff | obfuscated-file:dist/assets/AtlasLoader.js | AI (source-diff): Standard minified dist output from official Spine Runtimes; long lines are bundled JS, not malicious obfuscation. | ai | |
| source-diff | obfuscated-file:dist/assets/SkeletonLoader.js | AI (source-diff): Standard minified dist output from official Spine Runtimes; long lines are bundled JS, not malicious obfuscation. | ai | |
| source-diff | obfuscated-file:dist/CanvasSkeletonRenderer.js | AI (source-diff): Minified dist output from official Spine Runtimes build pipeline; not malicious obfuscation. | ai | |
| provenance | no-provenance | AI (provenance): Esoteric Software does not use Sigstore provenance; consistent across their package family. | ai |
Versions (showing 66 of 66)
| Version | Deps | Published |
|---|---|---|
| 4.3.12 | 1 / 0 | |
| 4.3.11 | 1 / 0 | |
| 4.3.10 | 1 / 0 | |
| 4.3.7 | 1 / 0 | |
| 4.3.6 | 1 / 0 | |
| 4.3.5 | 1 / 0 | |
| 4.3.4 | 1 / 0 | |
| 4.3.3 | 1 / 0 | |
| 4.3.2 | 1 / 0 | |
| 4.3.1 | 1 / 0 | |
| 4.3.0 | 1 / 0 | |
| 4.2.119 | 1 / 0 | |
| 4.2.118 | 1 / 0 | |
| 4.2.117 | 1 / 0 | |
| 4.2.116 | 1 / 0 | |
| 4.2.115 | 1 / 0 | |
| 4.2.114 | 1 / 0 | |
| 4.2.113 | 1 / 0 | |
| 4.2.112 | 1 / 0 | |
| 4.2.111 | 1 / 0 | |
| 4.2.110 | 1 / 0 | |
| 4.2.109 | 1 / 0 | |
| 4.2.108 | 1 / 0 | |
| 4.2.107 | 1 / 0 | |
| 4.2.106 | 1 / 0 | |
| 4.2.105 | 1 / 0 | |
| 4.2.104 | 1 / 0 | |
| 4.2.103 | 1 / 0 | |
| 4.2.102 | 1 / 0 | |
| 4.2.101 | 1 / 0 | |
| 4.2.100 | 1 / 0 | |
| 4.2.99 | 1 / 0 | |
| 4.2.98 | 1 / 0 | |
| 4.2.97 | 1 / 0 | |
| 4.2.96 | 1 / 0 | |
| 4.2.95 | 1 / 0 | |
| 4.2.94 | 1 / 0 | |
| 4.2.93 | 1 / 0 | |
| 4.2.92 | 1 / 0 | |
| 4.2.91 | 1 / 0 | |
| 4.2.90 | 1 / 0 | |
| 4.2.89 | 1 / 0 | |
| 4.2.88 | 1 / 0 | |
| 4.2.87 | 1 / 0 | |
| 4.2.86 | 1 / 0 | |
| 4.2.85 | 1 / 0 | |
| 4.2.84 | 1 / 0 | |
| 4.2.83 | 1 / 0 | |
| 4.2.82 | 1 / 0 | |
| 4.2.81 | 1 / 0 | |
| 4.2.78 | 1 / 0 | |
| 4.2.77 | 1 / 0 | |
| 4.2.76 | 1 / 0 | |
| 4.2.75 | 1 / 0 | |
| 4.2.74 | 1 / 0 | |
| 4.2.73 | 1 / 0 | |
| 4.2.72 | 1 / 0 | |
| 4.2.71 | 1 / 0 | |
| 4.2.70 | 1 / 0 | |
| 4.2.69 | 1 / 0 | |
| 4.2.68 | 1 / 0 | |
| 4.2.67 | 1 / 0 | |
| 4.2.66 | 1 / 0 | |
| 4.2.65 | 1 / 0 | |
| 4.2.64 | 1 / 0 | |
| 4.2.63 | 1 / 0 |
v4.3.12
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v4.3.11
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v4.3.10
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 (daaaaa) on 2026-07-06, 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.
v4.2.78
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.2.77
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.2.76
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.2.75
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.2.74
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.2.73
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.2.72
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.2.71
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.2.70
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.2.69
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.2.68
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.2.67
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.2.66
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.2.65
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.2.64
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.2.63
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.