@swc/html-linux-x64-musl
Super-fast HTML minifier
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 |
|---|---|---|---|---|
| provenance | missing-githead | AI (provenance): SWC publishes via CI with SLSA/Sigstore attestation; missing gitHead is a minor metadata gap, not a supply chain risk. | ai | |
| npm-metadata | bundled-binaries | AI (npm-metadata): Platform-specific native .node binary is the entire purpose of this SWC sub-package; expected and attested via SLSA provenance. | ai | |
| bogus-package | bogus-package | AI (bogus-package): No-deps and sparse README are normal for a platform-specific binary distribution package in the @swc/* namespace. | ai |
Versions (showing 24 of 24)
| Version | Deps | Published |
|---|---|---|
| 1.15.46 | 0 / 0 | |
| 1.15.43 | 0 / 0 | |
| 1.15.41 | 0 / 0 | |
| 1.15.40 | 0 / 0 | |
| 1.15.33 | 0 / 0 | |
| 1.15.32 | 0 / 0 | |
| 1.15.30 | 0 / 0 | |
| 1.15.26 | 0 / 0 | |
| 1.15.24 | 0 / 0 | |
| 1.15.21 | 0 / 0 | |
| 1.15.18 | 0 / 0 | |
| 1.15.17 | 0 / 0 | |
| 1.15.13 | 0 / 0 | |
| 1.15.11 | 0 / 0 | |
| 1.15.10 | 0 / 0 | |
| 1.15.8 | 0 / 0 | |
| 1.15.7 | 0 / 0 | |
| 1.15.6 | 0 / 0 | |
| 1.15.5 | 0 / 0 | |
| 1.15.4 | 0 / 0 | |
| 1.15.3 | 0 / 0 | |
| 1.15.2 | 0 / 0 | |
| 1.15.1 | 0 / 0 | |
| 1.15.0 | 0 / 0 |
v1.15.46
2 findingsPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
[Accepted risk] This version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: GitHub Actions.
v1.15.21
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v1.15.18
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v1.15.17
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v1.15.13
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v1.15.11
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v1.15.10
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v1.15.8
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v1.15.7
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v1.15.6
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v1.15.5
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v1.15.4
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v1.15.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.15.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.15.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.15.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.