@esotericsoftware/spine-core
The official Spine Runtimes for the web.
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/attachments/HasTextureRegion.js | AI (source-diff): Standard TS-compiled JS with inline source maps; expected build output for this package. | ai | |
| source-diff | obfuscated-file:dist/Updatable.js | AI (source-diff): Standard TS-compiled JS with inline source maps; expected build output for this package. | ai | |
| source-diff | obfuscated-file:dist/Constraint.js | AI (source-diff): Inline sourcemap base64 triggers long-line detector; readable compiled TS, not malicious. | ai | |
| source-diff | obfuscated-file:dist/DrawOrder.js | AI (source-diff): Inline sourcemap base64 triggers long-line detector; readable compiled TS, not malicious. | ai | |
| source-diff | obfuscated-file:dist/attachments/HasSequence.js | AI (source-diff): Inline sourcemap base64 triggers long-line detector; readable compiled TS, not malicious. | ai | |
| source-diff | obfuscated-file:dist/IkConstraintPose.js | AI (source-diff): Inline sourcemap base64 triggers long-line detector; readable compiled TS, not malicious. | ai | |
| source-diff | obfuscated-file:dist/PathConstraintPose.js | AI (source-diff): Inline sourcemap base64 triggers long-line detector; readable compiled TS, not malicious. | ai | |
| source-diff | obfuscated-file:dist/Physics.js | AI (source-diff): Inline sourcemap base64 triggers long-line detector; readable compiled TS, not malicious. | ai | |
| source-diff | obfuscated-file:dist/PhysicsConstraintPose.js | AI (source-diff): Inline sourcemap base64 triggers long-line detector; readable compiled TS, not malicious. | ai | |
| source-diff | obfuscated-file:dist/Posed.js | AI (source-diff): Inline sourcemap base64 triggers long-line detector; readable compiled TS, not malicious. | ai | |
| source-diff | obfuscated-file:dist/PosedActive.js | AI (source-diff): Inline sourcemap base64 triggers long-line detector; readable compiled TS, not malicious. | ai | |
| source-diff | obfuscated-file:dist/SkeletonRendererCore.js | AI (source-diff): Inline sourcemap base64 triggers long-line detector; readable compiled TS, not malicious. | ai | |
| source-diff | obfuscated-file:dist/Slider.js | AI (source-diff): Inline sourcemap base64 triggers long-line detector; readable compiled TS, not malicious. | ai | |
| source-diff | obfuscated-file:dist/SliderData.js | AI (source-diff): Inline sourcemap base64 triggers long-line detector; readable compiled TS, not malicious. | ai | |
| source-diff | obfuscated-file:dist/SliderPose.js | AI (source-diff): Inline sourcemap base64 triggers long-line detector; readable compiled TS, not malicious. | ai | |
| source-diff | obfuscated-file:dist/SlotPose.js | AI (source-diff): Inline sourcemap base64 triggers long-line detector; readable compiled TS, not malicious. | ai | |
| source-diff | obfuscated-file:dist/TransformConstraintPose.js | AI (source-diff): Inline sourcemap base64 triggers long-line detector; readable compiled TS, not malicious. | ai | |
| source-diff | obfuscated-file:dist/Update.js | AI (source-diff): Inline sourcemap base64 triggers long-line detector; readable compiled TS, not malicious. | ai | |
| source-diff | large-new-source-files | AI (source-diff): 38 new files are a v4.3 API refactor of the official Spine runtime, not injected code. | ai | |
| bogus-package | bogus-package | AI (bogus-package): Official Esoteric Software runtime; no deps by design (pure TS library), short README is normal for a scoped SDK package. | ai | |
| source-diff | obfuscated-file:dist/PosedData.js | AI (source-diff): Inline sourcemap base64 triggers long-line detector; readable compiled TS, not malicious. | ai | |
| source-diff | obfuscated-file:dist/BonePose.js | AI (source-diff): Long lines are inline sourcemaps, not obfuscation; stable pattern for this compiled TS package. | ai | |
| source-diff | obfuscated-file:dist/PhysicsConstraint.js | AI (source-diff): Readable Spine Runtime source with license header; long lines are from bundled dist output, not obfuscation. | ai | |
| source-diff | obfuscated-file:dist/PhysicsConstraintData.js | AI (source-diff): Same pattern — legitimate ES module source with Esoteric Software license header, not obfuscated. | ai |
Versions (showing 100 of 204)
| Version | Deps | Published |
|---|---|---|
| 4.2.19 | 0 / 0 | |
| 4.2.18 | 0 / 0 | |
| 4.2.17 | 0 / 0 | |
| 4.2.16 | 0 / 0 | |
| 4.2.15 | 0 / 0 | |
| 4.2.14 | 0 / 0 | |
| 4.2.11 | 0 / 0 | |
| 4.2.10 | 0 / 0 | |
| 4.2.9 | 0 / 0 | |
| 4.2.8 | 0 / 0 | |
| 4.2.7 | 0 / 0 | |
| 4.2.6 | 0 / 0 | |
| 4.2.5 | 0 / 0 | |
| 4.2.4 | 0 / 0 | |
| 4.2.3 | 0 / 0 | |
| 4.2.2 | 0 / 0 | |
| 4.2.1 | 0 / 0 | |
| 4.1.56 | 0 / 0 | |
| 4.1.55 | 0 / 0 | |
| 4.1.54 | 0 / 0 | |
| 4.1.53 | 0 / 0 | |
| 4.1.52 | 0 / 0 | |
| 4.1.51 | 0 / 0 | |
| 4.1.50 | 0 / 0 | |
| 4.1.49 | 0 / 0 | |
| 4.1.48 | 0 / 0 | |
| 4.1.47 | 0 / 0 | |
| 4.1.46 | 0 / 0 | |
| 4.1.45 | 0 / 0 | |
| 4.1.44 | 0 / 0 | |
| 4.1.43 | 0 / 0 | |
| 4.1.42 | 0 / 0 | |
| 4.1.41 | 0 / 0 | |
| 4.1.40 | 0 / 0 | |
| 4.1.39 | 0 / 0 | |
| 4.1.38 | 0 / 0 | |
| 4.1.37 | 0 / 0 | |
| 4.1.36 | 0 / 0 | |
| 4.1.35 | 0 / 0 | |
| 4.1.34 | 0 / 0 | |
| 4.1.33 | 0 / 0 | |
| 4.1.32 | 0 / 0 | |
| 4.1.31 | 0 / 0 | |
| 4.1.30 | 0 / 0 | |
| 4.1.29 | 0 / 0 | |
| 4.1.28 | 0 / 0 | |
| 4.1.26 | 0 / 0 | |
| 4.1.25 | 0 / 0 | |
| 4.1.24 | 0 / 0 | |
| 4.1.23 | 0 / 0 | |
| 4.1.22 | 0 / 0 | |
| 4.1.21 | 0 / 0 | |
| 4.1.20 | 0 / 0 | |
| 4.1.19 | 0 / 0 | |
| 4.1.18 | 0 / 0 | |
| 4.1.17 | 0 / 0 | |
| 4.1.16 | 0 / 0 | |
| 4.1.15 | 0 / 0 | |
| 4.1.14 | 0 / 0 | |
| 4.1.13 | 0 / 0 | |
| 4.1.12 | 0 / 0 | |
| 4.1.11 | 0 / 0 | |
| 4.1.10 | 0 / 0 | |
| 4.1.9 | 0 / 0 | |
| 4.1.8 | 0 / 0 | |
| 4.1.7 | 0 / 0 | |
| 4.1.6 | 0 / 0 | |
| 4.1.5 | 0 / 0 | |
| 4.1.4 | 0 / 0 | |
| 4.1.3 | 0 / 0 | |
| 4.1.2 | 0 / 0 | |
| 4.1.1 | 0 / 0 | |
| 4.1.0 | 0 / 0 | |
| 4.0.31 | 0 / 0 | |
| 4.0.30 | 0 / 0 | |
| 4.0.29 | 0 / 0 | |
| 4.0.28 | 0 / 0 | |
| 4.0.27 | 0 / 0 | |
| 4.0.26 | 0 / 0 | |
| 4.0.25 | 0 / 0 | |
| 4.0.24 | 0 / 0 | |
| 4.0.23 | 0 / 0 | |
| 4.0.22 | 0 / 0 | |
| 4.0.21 | 0 / 0 | |
| 4.0.20 | 0 / 0 | |
| 4.0.19 | 0 / 0 | |
| 4.0.18 | 0 / 0 | |
| 4.0.17 | 0 / 0 | |
| 4.0.16 | 0 / 0 | |
| 4.0.15 | 0 / 0 | |
| 4.0.14 | 0 / 0 | |
| 4.0.13 | 0 / 0 | |
| 4.0.12 | 0 / 0 | |
| 4.0.11 | 0 / 0 | |
| 4.0.10 | 0 / 0 | |
| 4.0.9 | 0 / 0 | |
| 4.0.8 | 0 / 0 | |
| 4.0.7 | 0 / 0 | |
| 4.0.6 | 0 / 0 | |
| 4.0.5 | 0 / 0 |
v4.2.19
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.2.18
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.2.17
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.2.16
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.2.15
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.2.14
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.2.11
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.2.10
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.2.9
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.2.8
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.2.7
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.2.6
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.2.5
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.2.4
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.2.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.2.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.2.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.1.55
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.1.54
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.1.53
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.1.52
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.1.51
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.1.50
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.1.49
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.1.48
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.1.47
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.1.46
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.1.45
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.1.44
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.1.43
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.1.42
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.1.41
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.1.40
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.1.39
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.1.38
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.1.37
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.1.36
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.1.35
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.1.34
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.1.33
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.1.32
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.1.31
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.1.30
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.1.29
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.1.28
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.1.26
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.1.25
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.1.24
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.1.23
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.1.22
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.1.21
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.1.20
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.1.19
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.1.18
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.1.17
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.1.16
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.1.15
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.1.14
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.1.13
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.1.12
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.1.11
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.1.10
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.1.9
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.1.8
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.1.7
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.1.6
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.1.5
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.1.4
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.1.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.1.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.1.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.1.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.0.30
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.0.29
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.0.28
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.0.27
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.0.26
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.0.25
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.0.24
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.0.23
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.0.22
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.0.21
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.0.20
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.0.19
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.0.18
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.0.17
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.0.16
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.0.15
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.0.14
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.0.13
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.0.12
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.0.11
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.0.10
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.0.9
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.0.8
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.0.7
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.0.6
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.0.5
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.