@takeshape/util
Shared utilities
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 org package @takeshape/util; no intent to impersonate uuid. Stable false positive for this package. | ai | |
| phantom-deps | phantom-dep:tiny-invariant | AI (phantom-deps): Declared as runtime dep; phantom-dep heuristic misfires on transitive/indirect usage patterns. | ai | |
| phantom-deps | phantom-dep:@types/url-parse | AI (phantom-deps): Type-only package loaded by convention; phantom-dep heuristic correctly notes it's not directly imported. | ai |
Versions (showing 8 of 8)
| Version | Deps | Published |
|---|---|---|
| 12.19.0 | 15 / 8 | |
| 12.18.2 | 15 / 8 | |
| 12.17.3 | 15 / 8 | |
| 12.16.1 | 15 / 8 | |
| 12.16.0 | 15 / 8 | |
| 12.13.0 | 15 / 8 | |
| 12.8.0 | 15 / 8 | |
| 12.0.1 | 16 / 8 |
v12.19.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v12.18.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v12.17.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v12.16.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v12.16.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v12.13.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v12.8.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v12.0.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.