@swc/cli
CLI for the swc project
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 |
|---|---|---|---|---|
| install-scripts | install-script:postinstall | AI (install-scripts): Postinstall is a simple echo announcement about the new swcx command. No code execution or network access; purely informational and safe for this package. | ai | |
| phantom-deps | phantom-dep:@xhmikosr/bin-wrapper | AI (phantom-deps): CLI tool dependency used indirectly; phantom-deps false positive for this package type. | ai | |
| phantom-deps | phantom-dep:semver | AI (phantom-deps): CLI tool dependency used indirectly; phantom-deps false positive for this package type. | ai | |
| phantom-deps | phantom-dep:piscina | AI (phantom-deps): CLI tool dependency used indirectly; phantom-deps false positive for this package type. | ai | |
| phantom-deps | phantom-dep:commander | AI (phantom-deps): CLI tool dependency used indirectly; phantom-deps false positive for this package type. | ai | |
| phantom-deps | phantom-dep:fast-glob | AI (phantom-deps): CLI tool dependency used indirectly; phantom-deps false positive for this package type. | ai | |
| phantom-deps | phantom-dep:minimatch | AI (phantom-deps): CLI tool dependency used indirectly; phantom-deps false positive for this package type. | ai | |
| phantom-deps | phantom-dep:source-map | AI (phantom-deps): CLI tool dependency used indirectly; phantom-deps false positive for this package type. | ai | |
| phantom-deps | phantom-dep:slash | AI (phantom-deps): CLI tool dependency used indirectly; phantom-deps false positive for this package type. | ai | |
| typosquat | typosquat.levenshtein:joi | AI (typosquat): @swc/cli is the official SWC project CLI, not a typosquat of joi. The name similarity is coincidental and the packages are entirely unrelated. | ai | |
| semgrep | semgrep:child-process-import | AI (semgrep): @swc/cli is a CLI wrapper for the SWC compiler binary; child_process usage to invoke native binaries is expected and documented behavior. | ai | |
| semgrep | semgrep:dynamic-require | AI (semgrep): Dynamic require is used to read the local package.json to detect @swc/core peer dependency version — a standard CLI compatibility check pattern. | ai | |
| phantom-deps | phantom-dep:@swc/counter | AI (phantom-deps): @swc/counter is a same-org utility used across the SWC ecosystem; phantom dep finding is a false positive for this package. | ai | |
| maintainer-change | maintainer-removed | AI (maintainer-change): Maintainer removal coincides with transition to GitHub Actions publishing with SLSA attestation; consistent with legitimate automation of the release process. | ai | |
| provenance | publisher-changed | AI (provenance): Publisher changed to GitHub Actions with SLSA provenance attestation — this is a legitimate and encouraged move to automated CI/CD publishing under the official swc-project org. | ai |
Versions (showing 83 of 83)
| Version | Deps | Published |
|---|---|---|
| 0.8.1 | 9 / 12 | |
| 0.8.0 | 9 / 12 | |
| 0.7.10 | 9 / 12 | |
| 0.7.9 | 9 / 12 | |
| 0.7.8 | 9 / 12 | |
| 0.7.7 | 9 / 12 | |
| 0.7.5 | 9 / 12 | |
| 0.7.4 | 9 / 12 | |
| 0.7.3 | 9 / 12 | |
| 0.7.2 | 9 / 12 | |
| 0.7.1 | 9 / 12 | |
| 0.6.0 | 9 / 12 | |
| 0.5.2 | 9 / 12 | |
| 0.5.1 | 9 / 12 | |
| 0.5.0 | 9 / 12 | |
| 0.4.0 | 9 / 12 | |
| 0.3.14 | 9 / 12 | |
| 0.3.13 | 9 / 12 | |
| 0.3.12 | 9 / 11 | |
| 0.3.11 | 9 / 11 | |
| 0.3.10 | 9 / 11 | |
| 0.3.9 | 9 / 11 | |
| 0.3.6 | 8 / 11 | |
| 0.3.5 | 8 / 14 | |
| 0.3.4 | 8 / 14 | |
| 0.3.2 | 8 / 14 | |
| 0.3.1 | 8 / 14 | |
| 0.3.0 | 8 / 14 | |
| 0.2.3 | 8 / 14 | |
| 0.2.2 | 8 / 14 | |
| 0.2.1 | 8 / 14 | |
| 0.2.0 | 8 / 14 | |
| 0.1.65 | 7 / 14 | |
| 0.1.64 | 7 / 14 | |
| 0.1.63 | 6 / 14 | |
| 0.1.62 | 6 / 14 | |
| 0.1.61 | 6 / 14 | |
| 0.1.60 | 6 / 14 | |
| 0.1.59 | 6 / 14 | |
| 0.1.58 | 6 / 14 | |
| 0.1.57 | 4 / 13 | |
| 0.1.56 | 4 / 13 | |
| 0.1.55 | 4 / 13 | |
| 0.1.54 | 5 / 14 | |
| 0.1.53 | 5 / 11 | |
| 0.1.52 | 4 / 10 | |
| 0.1.51 | 4 / 10 | |
| 0.1.50 | 4 / 10 | |
| 0.1.49 | 4 / 10 | |
| 0.1.48 | 4 / 10 | |
| 0.1.46 | 4 / 8 | |
| 0.1.45 | 6 / 10 | |
| 0.1.44 | 6 / 9 | |
| 0.1.42 | 6 / 9 | |
| 0.1.41 | 6 / 8 | |
| 0.1.40 | 6 / 8 | |
| 0.1.39 | 6 / 8 | |
| 0.1.38 | 6 / 8 | |
| 0.1.37 | 6 / 8 | |
| 0.1.36 | 6 / 8 | |
| 0.1.35 | 6 / 8 | |
| 0.1.34 | 12 / 13 | |
| 0.1.33 | 12 / 13 | |
| 0.1.32 | 12 / 13 | |
| 0.1.31 | 12 / 13 | |
| 0.1.30 | 12 / 13 | |
| 0.1.29 | 12 / 13 | |
| 0.1.28 | 12 / 13 | |
| 0.1.27 | 12 / 13 | |
| 0.1.26 | 12 / 13 | |
| 0.1.24 | 10 / 10 | |
| 0.1.23 | 10 / 10 | |
| 0.1.22 | 10 / 10 | |
| 0.1.21 | 10 / 10 | |
| 0.1.20 | 10 / 10 | |
| 0.1.19 | 10 / 10 | |
| 0.1.18 | 10 / 10 | |
| 0.1.16 | 10 / 10 | |
| 0.1.15 | 10 / 10 | |
| 0.1.14 | 10 / 10 | |
| 0.1.13 | 10 / 10 | |
| 0.1.12 | 10 / 10 | |
| 0.1.10 | 10 / 10 |
v0.8.1
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.8.0
2 findingsThis version was published by a different npm account than previous versions on 2026-02-06. This could indicate a legitimate maintainer transition or an account compromise.
Published via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.7.10
2 findingsThis version was published by a different npm account than previous versions on 2026-01-14. This could indicate a legitimate maintainer transition or an account compromise.
Published via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.7.9
2 findingsThis version was published by a different npm account than previous versions on 2025-11-05. This could indicate a legitimate maintainer transition or an account compromise.
Published via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.7.8
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.7.7
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.7.5
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.7.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.7.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.7.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.7.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.6.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.5.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.5.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.5.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.4.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.3.14
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.3.13
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.3.12
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.3.11
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.3.10
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.3.9
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.3.6
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.3.5
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.3.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.3.2
2 findingsThis version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: kdy1.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.3.1
2 findingsThis version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: kdy1.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.3.0
2 findingsThis version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: kdy1.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.2.3
2 findingsThis version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: kdy1.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.2.2
2 findingsThis version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: kdy1.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.2.1
2 findingsThis version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: kdy1.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.2.0
2 findingsThis version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: kdy1.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.65
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.64
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.63
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.62
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.61
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.60
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.59
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.58
2 findingsScript: echo "Beta version of @swc/cli is now available via 'swcx' command. This'll be a default command for @swc/cli@1. Please give it a try and let us know if there are problems!"
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.57
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.56
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.55
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.54
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.53
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.52
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.51
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.50
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.49
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.48
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.1.46
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.1.45
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.1.44
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.1.42
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.1.41
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.1.40
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.1.39
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.1.38
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.1.37
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.1.36
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.1.35
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.1.34
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.1.33
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.1.32
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.1.31
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.1.30
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.1.29
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.1.28
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.1.27
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.1.26
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.1.24
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.1.23
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.1.22
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.1.21
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.1.20
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.1.19
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.1.18
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.1.16
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.1.15
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.1.14
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.1.13
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.1.12
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.1.10
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.