@superblocksteam/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, so a manually published version cannot be tied back to a reviewed commit.
Maintainers
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| semgrep | semgrep:shady-links-raw-ip | AI (semgrep): Raw IP references are in test files using localhost/127.0.0.1 — standard test fixtures, not malicious. | ai | |
| phantom-deps | phantom-dep:lodash | AI (phantom-deps): lodash is explicitly declared in dependencies; phantom-dep heuristic is a false positive here. | ai | |
| typosquat | typosquat.levenshtein:uuid | AI (typosquat): Scoped org package @superblocksteam/util; Levenshtein match to 'uuid' is coincidental, not a squatting attempt. | ai |
Versions (showing 21 of 121)
| Version | Deps | Published |
|---|---|---|
| 1.9.2 | 3 / 7 | |
| 1.9.1 | 3 / 7 | |
| 1.9.0 | 3 / 7 | |
| 1.8.2 | 3 / 7 | |
| 1.8.0 | 3 / 7 | |
| 1.7.0 | 3 / 7 | |
| 1.6.0 | 3 / 7 | |
| 1.5.2 | 3 / 7 | |
| 1.5.1 | 3 / 7 | |
| 1.5.0 | 3 / 7 | |
| 1.4.2 | 3 / 7 | |
| 1.4.1 | 3 / 7 | |
| 1.3.1 | 3 / 7 | |
| 1.3.0 | 3 / 7 | |
| 1.2.1 | 3 / 7 | |
| 1.2.0 | 3 / 7 | |
| 1.1.2 | 3 / 7 | |
| 1.1.1 | 3 / 7 | |
| 1.1.0 | 3 / 7 | |
| 1.0.2 | 3 / 7 | |
| 1.0.0 | 3 / 7 |
v1.9.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.9.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.9.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.8.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.8.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.7.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.6.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.5.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.5.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.5.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.4.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.4.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.3.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.3.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.2.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.2.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.1.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.1.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.1.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.