@esotericsoftware/spine-phaser-v3
The official Spine Runtimes for the Phaser v3.
Supply chain provenance
Status for the latest visible version.
Maintainers
Keywords
Versions (showing 52 of 52)
| Version | Deps | Published |
|---|---|---|
| 4.3.10 | 3 / 1 | |
| 4.3.7 | 3 / 1 | |
| 4.3.6 | 3 / 1 | |
| 4.3.5 | 3 / 1 | |
| 4.3.4 | 3 / 1 | |
| 4.3.3 | 3 / 1 | |
| 4.3.2 | 3 / 1 | |
| 4.3.1 | 3 / 1 | |
| 4.3.0 | 3 / 1 | |
| 4.2.119 | 3 / 1 | |
| 4.2.118 | 3 / 1 | |
| 4.2.117 | 3 / 1 | |
| 4.2.116 | 3 / 1 | |
| 4.2.115 | 3 / 1 | |
| 4.2.114 | 3 / 1 | |
| 4.2.113 | 3 / 1 | |
| 4.2.112 | 3 / 1 | |
| 4.2.111 | 3 / 1 | |
| 4.2.110 | 3 / 1 | |
| 4.2.109 | 3 / 1 | |
| 4.2.108 | 3 / 1 | |
| 4.2.107 | 3 / 1 | |
| 4.2.106 | 3 / 1 | |
| 4.2.105 | 3 / 1 | |
| 4.2.104 | 3 / 1 | |
| 4.2.103 | 3 / 1 | |
| 4.2.102 | 3 / 1 | |
| 4.2.101 | 3 / 1 | |
| 4.2.100 | 3 / 1 | |
| 4.2.99 | 3 / 1 | |
| 4.2.98 | 3 / 1 | |
| 4.2.97 | 3 / 1 | |
| 4.2.96 | 3 / 1 | |
| 4.2.95 | 3 / 1 | |
| 4.2.94 | 3 / 1 | |
| 4.2.93 | 3 / 1 | |
| 4.2.92 | 3 / 1 | |
| 4.2.91 | 3 / 1 | |
| 4.2.90 | 3 / 1 | |
| 4.2.89 | 3 / 1 | |
| 4.2.88 | 3 / 1 | |
| 4.2.87 | 3 / 1 | |
| 4.2.86 | 3 / 1 | |
| 4.2.85 | 3 / 1 | |
| 4.2.84 | 3 / 1 | |
| 4.2.83 | 3 / 1 | |
| 4.2.82 | 3 / 1 | |
| 4.2.81 | 3 / 1 | |
| 4.2.80 | 3 / 1 | |
| 4.2.79 | 3 / 1 | |
| 4.2.78 | 3 / 1 | |
| 4.2.77 | 3 / 1 |
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.80
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.2.79
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.2.78
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.2.77
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.