@spinajs/util
utility functions shared across @spinajs framework
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
Keywords
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 @spinajs framework utility package; name similarity to uuid is coincidental, not impersonation. | ai |
Versions (showing 4 of 104)
| Version | Deps | Published |
|---|---|---|
| 2.0.363 | 2 / 0 | |
| 2.0.362 | 2 / 0 | |
| 2.0.361 | 2 / 0 | |
| 2.0.360 | 2 / 0 |
v2.0.363
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.0.362
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.0.361
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.0.360
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.