@esotericsoftware/spine-phaser-v4
The official Spine Runtimes for the Phaser v4.
51
Versions
LicenseRef-LICENSE
License
No
Install Scripts
Verified
Provenance
Supply chain provenance
Status for the latest visible version.
SLSA provenance attestation
npm registry signatures
gitHead linked
Maintainers
badlogicnathansweetdaaaaa
Keywords
gamedevanimations2dspinegame-devruntimesskeletal
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| provenance | no-provenance | AI (provenance): Established Esoteric Software package; lack of provenance is common and not a risk signal here. | ai |
Versions (showing 51 of 51)
| Version | Deps | Published |
|---|---|---|
| 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.2.80
1 finding
INFO
No provenance attestation
provenance
[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.2.79
1 finding
INFO
No provenance attestation
provenance
[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.2.78
1 finding
INFO
No provenance attestation
provenance
[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.2.77
1 finding
INFO
No provenance attestation
provenance
[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.