@dreamkit/app
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
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| 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 18 of 18)
| 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 |
v0.0.49
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.48
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.46
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.45
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.44
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.41
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.37
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.36
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.35
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.31
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.26
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.24
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.22
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.19
1 findingPackage 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.11
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.10
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.9
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.