@playsthisgame/melon-linux-arm64
linux arm64 binary for @playsthisgame/melon
Supply chain provenance
Status for the latest visible version.
Without SLSA provenance there is no cryptographic link between this tarball and the public source — the axios compromise (March 2026) relied on exactly this gap.
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): Package is explicitly a platform binary distribution; bundled binary is the intended deliverable. | ai |
Versions (showing 21 of 21)
| Version | Deps | Published |
|---|---|---|
| 0.4.4 | 0 / 0 | |
| 0.4.3 | 0 / 0 | |
| 0.4.2 | 0 / 0 | |
| 0.4.1 | 0 / 0 | |
| 0.4.0 | 0 / 0 | |
| 0.3.7 | 0 / 0 | |
| 0.3.6 | 0 / 0 | |
| 0.3.5 | 0 / 0 | |
| 0.3.4 | 0 / 0 | |
| 0.3.3 | 0 / 0 | |
| 0.3.2 | 0 / 0 | |
| 0.3.1 | 0 / 0 | |
| 0.3.0 | 0 / 0 | |
| 0.2.10 | 0 / 0 | |
| 0.2.9 | 0 / 0 | |
| 0.2.8 | 0 / 0 | |
| 0.2.7 | 0 / 0 | |
| 0.2.6 | 0 / 0 | |
| 0.2.5 | 0 / 0 | |
| 0.2.4 | 0 / 0 | |
| 0.2.3 | 0 / 0 |
v0.4.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.4.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.4.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.4.1
2 findingsPackage contains compiled binaries that could be backdoors: • mln
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.4.0
2 findingsPackage contains compiled binaries that could be backdoors: • mln
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.3.7
2 findingsPackage contains compiled binaries that could be backdoors: • mln
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.3.6
2 findingsPackage contains compiled binaries that could be backdoors: • mln
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.3.5
2 findingsPackage contains compiled binaries that could be backdoors: • mln
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.3.4
2 findingsPackage contains compiled binaries that could be backdoors: • mln
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.3.2
2 findingsPackage contains compiled binaries that could be backdoors: • mln
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.3.1
2 findingsPackage contains compiled binaries that could be backdoors: • mln
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.3.0
2 findingsPackage contains compiled binaries that could be backdoors: • mln
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.2.10
2 findingsPackage contains compiled binaries that could be backdoors: • mln
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.2.9
2 findingsPackage contains compiled binaries that could be backdoors: • mln
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.2.8
2 findingsPackage contains compiled binaries that could be backdoors: • mln
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.2.7
2 findingsPackage contains compiled binaries that could be backdoors: • mln
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.2.6
2 findingsPackage contains compiled binaries that could be backdoors: • mln
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.2.5
2 findingsPackage contains compiled binaries that could be backdoors: • mln
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.2.4
2 findingsPackage contains compiled binaries that could be backdoors: • mln
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.2.3
2 findingsPackage contains compiled binaries that could be backdoors: • mln
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.