@dreamkit/solid
Supply chain provenance
Status for the latest visible version.
Without SLSA provenance there is no cryptographic link between this tarball and the public source — the axios compromise (March 2026) relied on exactly this gap.
Maintainers
Keywords
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| phantom-deps | phantom-dep:@dreamkit/ioc | AI (phantom-deps): @dreamkit/ioc is a declared runtime dep in the same org scope; phantom-dep heuristic false positive for this package. | ai | |
| dependencies | unvetted-dep:@dreamkit/utils | AI (dependencies): Same monorepo/publisher (juanrgm/dreamkit); consistent internal dependency pattern across approved versions. | ai | |
| provenance | no-provenance | AI (provenance): Consistent across all 60 versions; no provenance is the norm for this publisher. | ai |
Versions (showing 16 of 16)
| Version | Deps | Published |
|---|---|---|
| 0.0.51 | 4 / 5 | |
| 0.0.50 | 4 / 5 | |
| 0.0.48 | 4 / 5 | |
| 0.0.47 | 4 / 5 | |
| 0.0.42 | 4 / 5 | |
| 0.0.36 | 4 / 5 | |
| 0.0.24 | 4 / 5 | |
| 0.0.23 | 4 / 5 | |
| 0.0.21 | 4 / 5 | |
| 0.0.20 | 4 / 5 | |
| 0.0.18 | 4 / 5 | |
| 0.0.17 | 4 / 5 | |
| 0.0.16 | 4 / 5 | |
| 0.0.15 | 4 / 5 | |
| 0.0.14 | 4 / 5 | |
| 0.0.12 | 4 / 5 |
v0.0.51
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.50
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.48
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.47
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.42
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.36
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.24
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.23
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.21
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.20
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.18
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
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 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.15
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.14
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.12
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.