@ottocode/web-sdk
Reusable React components, hooks, and utilities for building ottocode web interfaces
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
Keywords
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| dependencies | unvetted-dep:@ottocode/themes | AI (dependencies): First-party @ottocode monorepo package, versioned in lockstep; stable false positive for this package. | ai | |
| source-diff | large-new-source-files | AI (source-diff): Actively developed UI SDK; incremental file additions are expected across its 119-version history. | ai | |
| source-diff | obfuscated-file:dist/components/tunnel/TunnelSidebar.js | AI (source-diff): File is readable tsc-compiled React output; long lines are normal for bundled JSX, not obfuscation. | ai | |
| publish-pattern | new-deps-added | AI (publish-pattern): New deps are established @codemirror/* packages; consistent with adding CodeMirror editor support. | ai | |
| dependencies | unvetted-dep:ghostty-web | AI (dependencies): ghostty-web is a WebAssembly terminal emulator; its use in a web SDK is plausible and no malicious signals are associated with it. Acceptable for this package. | ai | |
| dependencies | unvetted-dep:@ottocode/sdk | AI (dependencies): Sibling package in the same @ottocode monorepo, pinned to the same version. Consistent with coordinated monorepo releases by the same publisher. | ai | |
| provenance | no-provenance | AI (provenance): Young private-ecosystem package; lack of provenance is common (~88% of npm) and not a security signal for this package. | ai | |
| phantom-deps | phantom-dep:axios | AI (phantom-deps): axios is a declared runtime dependency; phantom-dep finding reflects it being referenced in config rather than directly imported — a packaging style choice, not a security issue. | ai |
Versions (showing 51 of 151)
| Version | Deps | Published |
|---|---|---|
| 0.1.332 | 25 / 14 | |
| 0.1.331 | 25 / 14 | |
| 0.1.327 | 24 / 14 | |
| 0.1.326 | 24 / 14 | |
| 0.1.325 | 24 / 14 | |
| 0.1.324 | 24 / 14 | |
| 0.1.323 | 24 / 14 | |
| 0.1.322 | 24 / 14 | |
| 0.1.321 | 24 / 14 | |
| 0.1.320 | 24 / 14 | |
| 0.1.319 | 24 / 14 | |
| 0.1.318 | 24 / 14 | |
| 0.1.317 | 24 / 14 | |
| 0.1.316 | 24 / 14 | |
| 0.1.315 | 24 / 14 | |
| 0.1.314 | 24 / 14 | |
| 0.1.313 | 24 / 14 | |
| 0.1.312 | 24 / 14 | |
| 0.1.311 | 24 / 14 | |
| 0.1.310 | 24 / 14 | |
| 0.1.309 | 24 / 14 | |
| 0.1.308 | 24 / 14 | |
| 0.1.307 | 24 / 14 | |
| 0.1.306 | 24 / 14 | |
| 0.1.305 | 24 / 14 | |
| 0.1.304 | 24 / 14 | |
| 0.1.303 | 24 / 14 | |
| 0.1.302 | 24 / 14 | |
| 0.1.301 | 24 / 14 | |
| 0.1.300 | 24 / 14 | |
| 0.1.299 | 24 / 14 | |
| 0.1.298 | 24 / 14 | |
| 0.1.297 | 24 / 14 | |
| 0.1.296 | 24 / 14 | |
| 0.1.295 | 23 / 14 | |
| 0.1.294 | 23 / 14 | |
| 0.1.293 | 23 / 14 | |
| 0.1.292 | 23 / 14 | |
| 0.1.291 | 23 / 14 | |
| 0.1.290 | 23 / 14 | |
| 0.1.289 | 23 / 14 | |
| 0.1.288 | 23 / 14 | |
| 0.1.287 | 23 / 14 | |
| 0.1.286 | 23 / 14 | |
| 0.1.285 | 23 / 14 | |
| 0.1.284 | 22 / 14 | |
| 0.1.283 | 22 / 14 | |
| 0.1.282 | 22 / 14 | |
| 0.1.281 | 22 / 14 | |
| 0.1.280 | 22 / 14 | |
| 0.1.279 | 22 / 14 |
v0.1.332
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.331
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.327
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.326
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.325
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.324
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.323
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.322
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.321
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.320
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.319
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.318
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.317
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.316
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.315
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.314
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.313
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.312
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.311
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.310
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.309
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.308
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.307
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.305
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.304
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.303
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.302
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.301
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.300
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.299
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.298
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.295
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.294
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.293
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.292
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.290
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.289
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.288
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.287
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.284
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.283
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.281
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.