@choonkeat/swe-swe-win32-arm64
swe-swe binary for windows/arm64
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): Platform binary shim package; .exe is the intended deliverable for win32/arm64. | ai | |
| bogus-package | bogus-package | AI (bogus-package): Minimal metadata is normal for platform-specific binary shim packages in a multi-package distribution. | ai |
Versions (showing 7 of 7)
| Version | Deps | Published |
|---|---|---|
| 2.24.0 | 0 / 0 | |
| 2.23.0 | 0 / 0 | |
| 2.22.0 | 0 / 0 | |
| 2.21.1 | 0 / 0 | |
| 2.21.0 | 0 / 0 | |
| 0.1.4 | 0 / 0 | |
| 0.1.3 | 0 / 0 |
v2.24.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.23.0
2 findingsPackage contains compiled binaries that could be backdoors: • bin/swe-swe.exe
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.22.0
2 findingsPackage contains compiled binaries that could be backdoors: • bin/swe-swe.exe
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.21.1
2 findingsPackage contains compiled binaries that could be backdoors: • bin/swe-swe.exe
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.21.0
2 findingsPackage contains compiled binaries that could be backdoors: • bin/swe-swe.exe
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.1.4
2 findingsPackage contains compiled binaries that could be backdoors: • bin/swe-swe.exe
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.1.3
2 findingsPackage contains compiled binaries that could be backdoors: • bin/swe-swe.exe
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.