dreamkit
Toolkit for building Solid/SolidStart apps.
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
Keywords
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| provenance | no-provenance | AI (provenance): Established package; lack of provenance is common and not a risk signal here. | ai |
Versions (showing 58 of 58)
| Version | Deps | Published |
|---|---|---|
| 0.0.59 | 4 / 1 | |
| 0.0.58 | 4 / 1 | |
| 0.0.57 | 4 / 1 | |
| 0.0.56 | 4 / 1 | |
| 0.0.55 | 4 / 1 | |
| 0.0.54 | 4 / 1 | |
| 0.0.53 | 4 / 1 | |
| 0.0.52 | 4 / 1 | |
| 0.0.51 | 4 / 1 | |
| 0.0.50 | 4 / 1 | |
| 0.0.49 | 4 / 1 | |
| 0.0.48 | 4 / 1 | |
| 0.0.47 | 4 / 1 | |
| 0.0.46 | 4 / 1 | |
| 0.0.45 | 4 / 1 | |
| 0.0.44 | 4 / 1 | |
| 0.0.43 | 4 / 1 | |
| 0.0.42 | 4 / 1 | |
| 0.0.41 | 4 / 1 | |
| 0.0.40 | 4 / 1 | |
| 0.0.39 | 4 / 1 | |
| 0.0.38 | 4 / 1 | |
| 0.0.37 | 4 / 1 | |
| 0.0.36 | 4 / 1 | |
| 0.0.35 | 4 / 1 | |
| 0.0.34 | 4 / 1 | |
| 0.0.33 | 4 / 1 | |
| 0.0.32 | 7 / 1 | |
| 0.0.31 | 7 / 1 | |
| 0.0.30 | 7 / 1 | |
| 0.0.29 | 7 / 1 | |
| 0.0.28 | 7 / 1 | |
| 0.0.27 | 7 / 1 | |
| 0.0.26 | 7 / 1 | |
| 0.0.25 | 7 / 1 | |
| 0.0.24 | 7 / 1 | |
| 0.0.23 | 7 / 1 | |
| 0.0.22 | 7 / 1 | |
| 0.0.21 | 7 / 1 | |
| 0.0.20 | 7 / 1 | |
| 0.0.19 | 7 / 1 | |
| 0.0.18 | 7 / 1 | |
| 0.0.17 | 7 / 1 | |
| 0.0.16 | 7 / 1 | |
| 0.0.15 | 7 / 1 | |
| 0.0.14 | 6 / 1 | |
| 0.0.13 | 6 / 1 | |
| 0.0.12 | 5 / 1 | |
| 0.0.11 | 5 / 1 | |
| 0.0.10 | 4 / 1 | |
| 0.0.9 | 4 / 1 | |
| 0.0.8 | 4 / 1 | |
| 0.0.7 | 4 / 1 | |
| 0.0.6 | 4 / 1 | |
| 0.0.5 | 4 / 1 | |
| 0.0.4 | 4 / 1 | |
| 0.0.3 | 4 / 2 | |
| 0.0.2 | 4 / 2 |
v0.0.17
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.16
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.15
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.14
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.13
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.12
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.11
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.10
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.9
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.8
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.7
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.6
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.5
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.4
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.3
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.