@dreamkit/dev No license 26 versions

@dreamkit/dev

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 — the axios compromise (March 2026) relied on exactly this gap.

Maintainers

juanrgm

Accepted risks

Findings the reviewer chose to accept rather than block on.

Source	Rule	Reason	Accepted by	When
provenance	no-provenance	AI (provenance): Established monorepo package; no provenance is consistent across all versions.	ai	2026/05/24
typosquat	typosquat.levenshtein:ajv	AI (typosquat): Scoped @dreamkit package; Levenshtein match to 'ajv' is coincidental, not a squatting attempt.	ai	2026/05/15
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	2026/05/15
phantom-deps	phantom-dep:@types/babel__traverse	AI (phantom-deps): Type-only package loaded by convention; not directly imported but legitimately declared.	ai	2026/05/15
phantom-deps	phantom-dep:@types/babel__generator	AI (phantom-deps): Type-only package loaded by convention; not directly imported but legitimately declared.	ai	2026/05/15

Versions (showing 26 of 26)

Version	Deps	Published
0.0.58	20 / 5	2026-05-13
0.0.57	20 / 5	2026-05-12
0.0.55	20 / 5	2026-04-29
0.0.52	20 / 5	2026-03-26
0.0.51	20 / 5	2026-03-25
0.0.47	20 / 5	2026-01-02
0.0.45	20 / 5	2025-12-31
0.0.44	20 / 5	2025-12-10
0.0.39	20 / 5	2025-11-14
0.0.38	20 / 5	2025-11-02
0.0.37	20 / 5	2025-11-01
0.0.36	20 / 5	2025-10-20
0.0.35	20 / 5	2025-10-18
0.0.34	20 / 5	2025-10-17
0.0.33	20 / 5	2025-10-17
0.0.31	20 / 5	2025-10-16
0.0.30	20 / 5	2025-10-16
0.0.28	20 / 5	2025-10-15
0.0.27	20 / 5	2025-10-08
0.0.26	20 / 5	2025-09-05
0.0.25	20 / 5	2025-09-03
0.0.22	20 / 5	2025-08-29
0.0.20	20 / 5	2025-08-28
0.0.19	20 / 5	2025-08-28
0.0.18	20 / 5	2025-08-26
0.0.17	20 / 5	2025-05-30

v0.0.58

1 finding

LOW No provenance attestation provenance

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

v0.0.57

1 finding

LOW No provenance attestation provenance

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

v0.0.55

1 finding

LOW No provenance attestation provenance

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

v0.0.52

1 finding

LOW No provenance attestation provenance

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

v0.0.51

1 finding

LOW No provenance attestation provenance

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

v0.0.47

1 finding

LOW No provenance attestation provenance

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

v0.0.45

1 finding

LOW No provenance attestation provenance

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

v0.0.44

1 finding

LOW No provenance attestation provenance

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

v0.0.39

1 finding

LOW No provenance attestation provenance

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

v0.0.38

1 finding

LOW No provenance attestation provenance

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

v0.0.37

1 finding

LOW No provenance attestation provenance

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

v0.0.36

1 finding

LOW No provenance attestation provenance

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

v0.0.35

1 finding

LOW No provenance attestation provenance

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

v0.0.34

1 finding

LOW No provenance attestation provenance

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

v0.0.33

1 finding

LOW No provenance attestation provenance

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

v0.0.31

1 finding

LOW No provenance attestation provenance

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

v0.0.30

1 finding

LOW No provenance attestation provenance

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

v0.0.28

1 finding

LOW No provenance attestation provenance

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

v0.0.27

1 finding

LOW No provenance attestation provenance

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

v0.0.26

1 finding

LOW No provenance attestation provenance

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

v0.0.25

1 finding

LOW No provenance attestation provenance

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

v0.0.22

1 finding

LOW No provenance attestation provenance

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

v0.0.20

1 finding

LOW No provenance attestation provenance

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

v0.0.19

1 finding

LOW No provenance attestation provenance

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

v0.0.18

1 finding

LOW No provenance attestation provenance

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

v0.0.17

1 finding

LOW No provenance attestation provenance

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