@swissquote/crafty-preset-lightningcss
<table> <tr><th>Compatible Runners</th><td>
Supply chain provenance
Status for the latest visible version.
Without SLSA provenance there is no cryptographic link between this tarball and the public source, so a manually published version cannot be tied back to a reviewed commit.
Maintainers
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| provenance | no-provenance | AI (provenance): Established org package; lack of provenance is consistent across all versions and not a risk indicator here. | ai |
Versions (showing 15 of 15)
| Version | Deps | Published |
|---|---|---|
| 1.30.2 | 5 / 3 | |
| 1.30.1 | 5 / 3 | |
| 1.30.0 | 5 / 3 | |
| 1.29.0 | 5 / 3 | |
| 1.28.1 | 5 / 3 | |
| 1.28.0 | 5 / 3 | |
| 1.27.0 | 5 / 3 | |
| 1.26.0 | 5 / 3 | |
| 1.25.0 | 5 / 3 | |
| 1.24.0 | 5 / 3 | |
| 1.23.0 | 5 / 3 | |
| 1.22.3 | 5 / 3 | |
| 1.22.2 | 5 / 3 | |
| 1.22.1 | 5 / 3 | |
| 1.22.0 | 5 / 3 |
v1.30.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.28.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.27.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.26.0
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.25.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.24.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.23.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.22.3
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.22.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.22.1
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.22.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.