@sudobility/building_blocks
Higher-level shared UI building blocks for Sudobility apps
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 |
|---|---|---|---|---|
| source-diff | obfuscated-file:dist/SafeSubscriptionContext-Bttk78bU.js | AI (source-diff): Vite build output with hash suffix; sample shows plain readable React/router code, not obfuscation. | ai | |
| source-diff | obfuscated-file:dist/SafeSubscriptionContext-yobdw2tN.js | AI (source-diff): Vite-bundled output with readable imports and standard React code; long lines are from bundling, not obfuscation. | ai | |
| source-diff | obfuscated-file:dist/SafeSubscriptionContext-Bi7r_EZt.js | AI (source-diff): Vite-bundled output; sample shows readable React/JSX imports and standard patterns, not malicious obfuscation. | ai | |
| source-diff | obfuscated-file:dist/SafeSubscriptionContext-BN1cInbb.js | AI (source-diff): Vite build output with hash-suffixed filename; code is readable React/i18n bundle, not obfuscated. | ai | |
| source-diff | obfuscated-file:dist/SafeSubscriptionContext-C2Nxvjir.js | AI (source-diff): Standard Vite bundle output; readable imports and React component code, not obfuscated. | ai | |
| source-diff | obfuscated-file:dist/SafeSubscriptionContext-B8nGr5tC.js | AI (source-diff): Vite-bundled React component; long lines are minified bundle output, not obfuscation. Imports are fully readable and benign. | ai | |
| phantom-deps | phantom-dep:i18next-browser-languagedetector | AI (phantom-deps): i18next plugins are registered via config, not direct imports; stable false positive for this package. | ai | |
| phantom-deps | phantom-dep:i18next-http-backend | AI (phantom-deps): i18next plugins are registered via config, not direct imports; stable false positive for this package. | ai |
Versions (showing 51 of 220)
| Version | Deps | Published |
|---|---|---|
| 0.0.243 | 0 / 46 | |
| 0.0.242 | 0 / 46 | |
| 0.0.241 | 0 / 46 | |
| 0.0.240 | 0 / 46 | |
| 0.0.239 | 0 / 46 | |
| 0.0.238 | 0 / 46 | |
| 0.0.237 | 0 / 46 | |
| 0.0.236 | 0 / 46 | |
| 0.0.235 | 0 / 46 | |
| 0.0.234 | 0 / 46 | |
| 0.0.233 | 0 / 46 | |
| 0.0.232 | 0 / 46 | |
| 0.0.231 | 0 / 46 | |
| 0.0.230 | 0 / 46 | |
| 0.0.229 | 0 / 46 | |
| 0.0.228 | 0 / 46 | |
| 0.0.227 | 0 / 46 | |
| 0.0.226 | 0 / 46 | |
| 0.0.225 | 0 / 46 | |
| 0.0.224 | 0 / 46 | |
| 0.0.223 | 0 / 46 | |
| 0.0.222 | 0 / 46 | |
| 0.0.221 | 0 / 46 | |
| 0.0.220 | 0 / 46 | |
| 0.0.219 | 0 / 46 | |
| 0.0.218 | 0 / 46 | |
| 0.0.217 | 0 / 46 | |
| 0.0.216 | 0 / 46 | |
| 0.0.215 | 0 / 46 | |
| 0.0.214 | 0 / 46 | |
| 0.0.213 | 0 / 46 | |
| 0.0.212 | 0 / 46 | |
| 0.0.211 | 0 / 46 | |
| 0.0.210 | 0 / 46 | |
| 0.0.209 | 0 / 46 | |
| 0.0.208 | 0 / 46 | |
| 0.0.207 | 0 / 46 | |
| 0.0.206 | 0 / 46 | |
| 0.0.205 | 0 / 46 | |
| 0.0.204 | 0 / 46 | |
| 0.0.203 | 0 / 46 | |
| 0.0.202 | 0 / 46 | |
| 0.0.201 | 0 / 46 | |
| 0.0.200 | 0 / 46 | |
| 0.0.199 | 0 / 46 | |
| 0.0.198 | 0 / 46 | |
| 0.0.197 | 0 / 46 | |
| 0.0.196 | 0 / 46 | |
| 0.0.195 | 0 / 46 | |
| 0.0.194 | 0 / 46 | |
| 0.0.193 | 0 / 46 |
v0.0.243
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.242
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.241
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.240
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.239
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.238
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.237
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.236
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.235
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.234
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.233
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.232
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.231
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.230
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.229
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.228
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.227
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.226
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.225
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.224
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.223
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.222
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.221
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.220
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.219
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.218
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.217
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.216
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.215
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.214
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.213
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.212
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.211
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.210
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.209
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.208
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.207
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.206
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.205
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.204
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.203
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.202
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.201
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.200
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.199
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.198
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.197
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.196
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.195
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.194
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.193
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.