@kmamal/util
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 |
|---|---|---|---|---|
| typosquat | typosquat.levenshtein:uuid | AI (typosquat): Scoped utility package @kmamal/util; not a typosquat of uuid, different purpose and namespace. | ai | |
| semgrep | semgrep:dynamic-require | AI (semgrep): Dynamic require in build-index.js is a directory-traversal module loader, not arbitrary code execution. | ai |
Versions (showing 4 of 4)
| Version | Deps | Published |
|---|---|---|
| 0.2.31 | 3 / 3 | |
| 0.2.30 | 3 / 3 | |
| 0.2.29 | 3 / 3 | |
| 0.2.20 | 2 / 3 |
v0.2.31
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.2.30
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.2.29
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.2.20
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.