@jx3box/jx3box-data
Supply chain provenance
Status for the latest visible version.
Maintainers
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| npm-metadata | bundled-binaries | AI (npm-metadata): lua51.dll/lua51.exe are standard Lua 5.1 runtime files expected in this JX3 game data package; stable across versions. | ai |
Versions (showing 38 of 38)
| Version | Deps | Published |
|---|---|---|
| 3.9.6 | 0 / 7 | |
| 3.9.5 | 0 / 7 | |
| 3.9.4 | 0 / 7 | |
| 3.9.3 | 0 / 7 | |
| 3.9.2 | 0 / 7 | |
| 3.9.1 | 0 / 7 | |
| 3.9.0 | 0 / 7 | |
| 3.8.9 | 0 / 7 | |
| 3.8.8 | 0 / 7 | |
| 3.8.7 | 0 / 7 | |
| 3.8.6 | 0 / 7 | |
| 3.8.5 | 0 / 7 | |
| 3.8.4 | 0 / 7 | |
| 3.8.3 | 0 / 7 | |
| 3.8.2 | 0 / 7 | |
| 3.8.1 | 0 / 7 | |
| 3.8.0 | 0 / 7 | |
| 3.7.9 | 0 / 7 | |
| 3.7.8 | 0 / 7 | |
| 3.7.7 | 0 / 7 | |
| 3.7.6 | 0 / 7 | |
| 3.7.5 | 0 / 7 | |
| 3.7.4 | 0 / 7 | |
| 3.7.3 | 0 / 7 | |
| 3.7.2 | 0 / 7 | |
| 3.7.1 | 0 / 7 | |
| 3.7.0 | 0 / 7 | |
| 3.6.9 | 0 / 7 | |
| 3.6.8 | 0 / 7 | |
| 3.6.7 | 0 / 7 | |
| 3.6.6 | 0 / 7 | |
| 3.6.5 | 0 / 7 | |
| 3.6.4 | 0 / 7 | |
| 3.6.3 | 0 / 7 | |
| 3.6.2 | 0 / 7 | |
| 3.6.1 | 0 / 7 | |
| 3.6.0 | 0 / 7 | |
| 3.5.9 | 0 / 7 |
v3.9.6
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v3.8.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.8.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.8.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.7.9
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.7.8
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.7.7
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.7.6
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.7.5
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.7.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.7.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.7.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.7.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.7.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.6.9
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.6.8
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.6.7
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.6.6
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.6.5
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.6.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.6.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.6.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.6.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.6.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.5.9
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.