← Home

@dreamkit/app

npm Repository Homepage
26
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

Accepted risks

Findings the reviewer chose to accept rather than block on.

SourceRuleReasonAccepted byWhen
provenance no-provenance AI (provenance): Established package with consistent publish history; no provenance is a process gap, not a security signal here. ai
typosquat typosquat.levenshtein:hapi AI (typosquat): Scoped @dreamkit package; not a typosquat of hapi. ai
typosquat typosquat.levenshtein:pg AI (typosquat): Scoped @dreamkit package; not a typosquat of pg. ai
typosquat typosquat.levenshtein:yup AI (typosquat): Scoped @dreamkit package; not a typosquat of yup. ai
typosquat typosquat.levenshtein:ajv AI (typosquat): Scoped @dreamkit package; not a typosquat of ajv. ai

Versions (showing 26 of 26)

Version Deps Published
0.0.49 6 / 2
0.0.48 6 / 2
0.0.46 6 / 2
0.0.45 6 / 2
0.0.44 6 / 2
0.0.41 6 / 2
0.0.37 6 / 2
0.0.36 6 / 2
0.0.35 6 / 2
0.0.31 6 / 2
0.0.26 6 / 2
0.0.24 6 / 2
0.0.22 6 / 2
0.0.19 6 / 2
0.0.16 6 / 2
0.0.11 6 / 2
0.0.10 6 / 2
0.0.9 6 / 2
0.0.8 6 / 2
0.0.7 6 / 2
0.0.6 6 / 2
0.0.5 6 / 2
0.0.4 5 / 2
0.0.3 3 / 1
0.0.2 3 / 1
0.0.1 3 / 1

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. Only ~12% of npm packages have provenance, so this is common but not ideal.

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.