@swc/core-darwin-arm64
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 is a platform-specific native Node.js addon (.node file) for the SWC compiler — bundling a compiled binary is its entire purpose and is stable across all versions. | ai | |
| bogus-package | bogus-package | AI (bogus-package): Platform-specific native binary packages intentionally have no deps and minimal READMEs; this is a structural property of all @swc/core-* platform packages. | ai | |
| provenance | no-provenance | AI (provenance): Package predates widespread Sigstore provenance adoption; absence is expected for this version range. | ai |
Versions (showing 34 of 434)
| 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 | |
| 1.2.59 | 0 / 0 | |
| 1.2.58 | 0 / 0 | |
| 1.2.57 | 0 / 0 | |
| 1.2.56 | 0 / 0 | |
| 1.2.55 | 0 / 0 | |
| 1.2.54 | 0 / 0 | |
| 1.2.53 | 0 / 0 | |
| 1.2.52 | 0 / 0 | |
| 1.2.51 | 0 / 0 | |
| 1.2.50 | 0 / 0 | |
| 1.2.49 | 0 / 0 | |
| 1.2.48 | 0 / 0 | |
| 1.2.47 | 0 / 0 | |
| 1.2.46 | 0 / 0 | |
| 1.2.45 | 0 / 0 | |
| 1.2.44 | 0 / 0 | |
| 1.2.43 | 0 / 0 | |
| 0.3.17 | 0 / 0 |
v1.2.75
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.2.74
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.2.73
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.2.72
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.2.71
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.2.70
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.2.69
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.2.68
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.2.67
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.2.66
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.2.65
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.2.64
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.2.63
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.2.62
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.2.61
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.2.60
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.2.59
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.2.58
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.2.57
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.2.56
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.2.55
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.2.54
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.2.53
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.2.52
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.2.51
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.2.50
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.2.49
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.2.48
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.2.47
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.2.46
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.2.45
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.2.44
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.2.43
2 findingsPackage contains compiled binaries that could be backdoors: • swc.darwin-arm64.node
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.3.17
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.