← Home

@dreamkit/dev

npm Repository Homepage
42
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 monorepo package; no provenance is consistent across all versions. ai
typosquat typosquat.levenshtein:ajv AI (typosquat): Scoped @dreamkit package; Levenshtein match to 'ajv' is coincidental, not a squatting attempt. ai
phantom-deps phantom-dep:@dreamkit/utils AI (phantom-deps): Same-org sibling dep; phantom-dep heuristic is a stable false positive for this package. ai
phantom-deps phantom-dep:@types/babel__traverse AI (phantom-deps): Type-only package loaded by convention; not directly imported but legitimately declared. ai
phantom-deps phantom-dep:@types/babel__generator AI (phantom-deps): Type-only package loaded by convention; not directly imported but legitimately declared. ai

Versions (showing 42 of 42)

Version Deps Published
0.0.58 20 / 5
0.0.57 20 / 5
0.0.55 20 / 5
0.0.52 20 / 5
0.0.51 20 / 5
0.0.47 20 / 5
0.0.45 20 / 5
0.0.44 20 / 5
0.0.39 20 / 5
0.0.38 20 / 5
0.0.37 20 / 5
0.0.36 20 / 5
0.0.35 20 / 5
0.0.34 20 / 5
0.0.33 20 / 5
0.0.31 20 / 5
0.0.30 20 / 5
0.0.28 20 / 5
0.0.27 20 / 5
0.0.26 20 / 5
0.0.25 20 / 5
0.0.22 20 / 5
0.0.20 20 / 5
0.0.19 20 / 5
0.0.18 20 / 5
0.0.17 20 / 5
0.0.16 20 / 5
0.0.15 20 / 5
0.0.14 20 / 5
0.0.13 16 / 5
0.0.12 16 / 5
0.0.11 16 / 5
0.0.10 16 / 5
0.0.9 15 / 5
0.0.8 15 / 5
0.0.7 15 / 5
0.0.6 15 / 5
0.0.5 15 / 5
0.0.4 15 / 5
0.0.3 15 / 5
0.0.2 15 / 5
0.0.1 14 / 6

v0.0.16

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.15

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.14

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.13

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.12

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

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.