@dreamkit/func
Functions builder with IoC and input validation.
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 |
|---|---|---|---|---|
| dependencies | unvetted-dep:@dreamkit/utils | AI (dependencies): Internal dreamkit monorepo package from the same trusted publisher; stable false positive for this package. | ai | |
| provenance | no-provenance | AI (provenance): Consistent across all 38 versions of this package; no provenance is the norm for this publisher. | ai | |
| phantom-deps | phantom-dep:@dreamkit/utils | AI (phantom-deps): Same-org monorepo dep; phantom-dep heuristic is unreliable for re-exported transitive deps in this package family. | ai |
Versions (showing 10 of 10)
| Version | Deps | Published |
|---|---|---|
| 0.0.31 | 4 / 1 | |
| 0.0.30 | 4 / 1 | |
| 0.0.26 | 4 / 1 | |
| 0.0.25 | 4 / 1 | |
| 0.0.13 | 4 / 1 | |
| 0.0.12 | 4 / 1 | |
| 0.0.10 | 4 / 1 | |
| 0.0.8 | 4 / 1 | |
| 0.0.6 | 4 / 1 | |
| 0.0.5 | 4 / 1 |
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.30
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
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.25
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.13
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.12
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.10
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.8
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.6
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.5
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.