← Home

@dreamkit/solid

npm Repository Homepage
27
Versions
—
License
No
Install Scripts
Missing
Provenance

Supply chain provenance

Status for the latest visible version.

No SLSA provenance npm registry signatures No source commit

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

juanrgm

Keywords

solidsolidjscontrolledinputcomponents

Accepted risks

Findings the reviewer chose to accept rather than block on.

SourceRuleReasonAccepted byWhen
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 27 of 27)

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
0.0.11 4 / 5
0.0.10 4 / 5
0.0.9 4 / 5
0.0.8 3 / 5
0.0.7 3 / 5
0.0.6 3 / 4
0.0.5 3 / 4
0.0.4 3 / 4
0.0.3 3 / 4
0.0.2 3 / 4
0.0.1 3 / 4

v0.0.11

1 finding
INFO No provenance attestation provenance

[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v0.0.10

1 finding
INFO No provenance attestation provenance

[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v0.0.9

1 finding
INFO No provenance attestation provenance

[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v0.0.8

1 finding
INFO No provenance attestation provenance

[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v0.0.7

1 finding
INFO No provenance attestation provenance

[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v0.0.6

1 finding
INFO No provenance attestation provenance

[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v0.0.5

1 finding
INFO No provenance attestation provenance

[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v0.0.4

1 finding
INFO No provenance attestation provenance

[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v0.0.3

1 finding
INFO No provenance attestation provenance

[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v0.0.2

1 finding
INFO No provenance attestation provenance

[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v0.0.1

1 finding
INFO No provenance attestation provenance

[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.