@swc/core-linux-arm64-musl
Super-fast alternative for babel
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 |
|---|---|---|---|---|
| npm-metadata | bundled-binaries | AI (npm-metadata): This package's sole purpose is distributing the SWC native .node binary for Linux ARM64 musl. Bundled binary is expected and legitimate for this platform-specific sub-package. | ai | |
| bogus-package | bogus-package | AI (bogus-package): Platform-specific binary sub-packages intentionally have minimal READMEs and no runtime dependencies. These signals are false positives for this package type. | ai |
Versions (showing 17 of 417)
| Version | Deps | Published |
|---|---|---|
| 1.2.75 | 0 / 0 | |
| 1.2.74 | 0 / 0 | |
| 1.2.73 | 0 / 0 | |
| 1.2.72 | 0 / 0 | |
| 1.2.71 | 0 / 0 | |
| 1.2.70 | 0 / 0 | |
| 1.2.69 | 0 / 0 | |
| 1.2.68 | 0 / 0 | |
| 1.2.67 | 0 / 0 | |
| 1.2.66 | 0 / 0 | |
| 1.2.65 | 0 / 0 | |
| 1.2.64 | 0 / 0 | |
| 1.2.63 | 0 / 0 | |
| 1.2.62 | 0 / 0 | |
| 1.2.61 | 0 / 0 | |
| 1.2.60 | 0 / 0 | |
| 0.3.17 | 0 / 0 |
v1.2.75
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.2.74
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.2.73
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.2.72
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.2.71
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.2.70
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.2.69
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.2.68
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.2.67
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.2.66
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.2.65
2 findingsPackage contains compiled binaries that could be backdoors: • swc.linux-arm64-musl.node
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.2.64
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.2.63
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.2.62
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.2.61
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.2.60
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.3.17
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.