@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 100 of 121)
| Version | Deps | Published |
|---|---|---|
| 2.0.143 | 8 / 13 | |
| 2.0.142 | 8 / 13 | |
| 2.0.141 | 8 / 13 | |
| 2.0.140 | 9 / 14 | |
| 2.0.139 | 9 / 14 | |
| 2.0.138 | 9 / 14 | |
| 2.0.137 | 9 / 14 | |
| 2.0.136 | 9 / 14 | |
| 2.0.135 | 9 / 14 | |
| 2.0.134 | 9 / 14 | |
| 2.0.133 | 9 / 14 | |
| 2.0.132 | 9 / 14 | |
| 2.0.131 | 9 / 14 | |
| 2.0.130 | 9 / 14 | |
| 2.0.129 | 9 / 14 | |
| 2.0.128 | 9 / 14 | |
| 2.0.127 | 9 / 14 | |
| 2.0.126 | 9 / 14 | |
| 2.0.125 | 9 / 14 | |
| 2.0.124 | 9 / 14 | |
| 2.0.123 | 9 / 14 | |
| 2.0.122 | 9 / 14 | |
| 2.0.121 | 9 / 14 | |
| 2.0.120 | 9 / 14 | |
| 2.0.119 | 9 / 14 | |
| 2.0.118 | 9 / 14 | |
| 2.0.117 | 9 / 14 | |
| 2.0.116 | 9 / 14 | |
| 2.0.115 | 9 / 13 | |
| 2.0.114 | 9 / 13 | |
| 2.0.113 | 9 / 13 | |
| 2.0.112 | 9 / 13 | |
| 2.0.111 | 9 / 13 | |
| 2.0.110 | 9 / 13 | |
| 2.0.109 | 9 / 13 | |
| 2.0.108 | 9 / 13 | |
| 2.0.107 | 9 / 13 | |
| 2.0.106 | 9 / 13 | |
| 2.0.105 | 9 / 13 | |
| 2.0.104 | 9 / 13 | |
| 2.0.103 | 9 / 13 | |
| 2.0.102 | 9 / 13 | |
| 2.0.101 | 9 / 13 | |
| 2.0.100 | 9 / 13 | |
| 2.0.99 | 9 / 13 | |
| 2.0.98 | 9 / 13 | |
| 2.0.97 | 9 / 13 | |
| 2.0.96 | 9 / 13 | |
| 2.0.95 | 9 / 13 | |
| 2.0.94 | 9 / 13 | |
| 2.0.93 | 9 / 14 | |
| 2.0.92 | 9 / 14 | |
| 2.0.91 | 9 / 14 | |
| 2.0.90 | 9 / 14 | |
| 2.0.89 | 9 / 14 | |
| 2.0.88 | 9 / 14 | |
| 2.0.87 | 9 / 14 | |
| 2.0.86 | 9 / 14 | |
| 2.0.85 | 9 / 14 | |
| 2.0.84 | 9 / 14 | |
| 2.0.83 | 9 / 14 | |
| 2.0.82 | 9 / 14 | |
| 2.0.81 | 9 / 14 | |
| 2.0.80 | 9 / 16 | |
| 2.0.79 | 9 / 16 | |
| 2.0.78 | 9 / 16 | |
| 2.0.77 | 9 / 16 | |
| 2.0.76 | 9 / 16 | |
| 2.0.75 | 9 / 16 | |
| 2.0.74 | 9 / 16 | |
| 2.0.73 | 9 / 16 | |
| 2.0.72 | 9 / 16 | |
| 2.0.71 | 9 / 16 | |
| 2.0.70 | 9 / 16 | |
| 2.0.69 | 9 / 16 | |
| 2.0.68 | 9 / 16 | |
| 2.0.67 | 9 / 16 | |
| 2.0.66 | 9 / 16 | |
| 2.0.65 | 9 / 16 | |
| 2.0.64 | 9 / 18 | |
| 2.0.63 | 9 / 18 | |
| 2.0.62 | 9 / 18 | |
| 2.0.61 | 9 / 18 | |
| 2.0.60 | 9 / 18 | |
| 2.0.59 | 9 / 18 | |
| 2.0.58 | 9 / 18 | |
| 2.0.57 | 9 / 18 | |
| 2.0.56 | 9 / 18 | |
| 2.0.55 | 9 / 18 | |
| 1.14.4 | 6 / 11 | |
| 1.14.3 | 6 / 11 | |
| 1.14.2 | 6 / 11 | |
| 1.14.1 | 5 / 12 | |
| 1.14.0 | 5 / 12 | |
| 1.13.1 | 5 / 12 | |
| 1.13.0 | 5 / 12 | |
| 1.12.0 | 5 / 11 | |
| 1.11.0 | 5 / 11 | |
| 1.10.0 | 3 / 7 | |
| 1.9.3 | 3 / 7 |
v2.0.143
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.0.142
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.0.141
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.0.140
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.0.139
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.0.138
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.0.137
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.0.136
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.14.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.14.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.13.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.13.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.12.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.11.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.10.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.9.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.