@ottocode/database
Database and persistence layer for ottocode
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 |
|---|---|---|---|---|
| dependencies | unvetted-dep:@ottocode/sdk | AI (dependencies): Sibling package in the same @ottocode namespace, co-versioned at the same version number. Expected intra-namespace dependency for this package. | ai | |
| provenance | no-provenance | AI (provenance): No provenance is common (~88% of npm packages lack it); no other risk signals elevate this to a concern for this package. | ai |
Versions (showing 26 of 26)
| Version | Deps | Published |
|---|---|---|
| 0.1.275 | 2 / 3 | |
| 0.1.274 | 2 / 3 | |
| 0.1.272 | 2 / 3 | |
| 0.1.268 | 2 / 3 | |
| 0.1.267 | 2 / 3 | |
| 0.1.266 | 2 / 3 | |
| 0.1.265 | 2 / 3 | |
| 0.1.263 | 2 / 3 | |
| 0.1.262 | 2 / 3 | |
| 0.1.260 | 2 / 3 | |
| 0.1.259 | 2 / 3 | |
| 0.1.258 | 2 / 3 | |
| 0.1.257 | 2 / 3 | |
| 0.1.256 | 2 / 3 | |
| 0.1.254 | 2 / 3 | |
| 0.1.253 | 2 / 3 | |
| 0.1.252 | 2 / 3 | |
| 0.1.251 | 2 / 3 | |
| 0.1.249 | 2 / 3 | |
| 0.1.248 | 2 / 3 | |
| 0.1.247 | 2 / 3 | |
| 0.1.246 | 2 / 3 | |
| 0.1.245 | 2 / 3 | |
| 0.1.243 | 2 / 3 | |
| 0.1.242 | 2 / 3 | |
| 0.1.173 | 2 / 3 |
v0.1.275
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.274
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.272
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.268
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.267
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.266
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.265
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.263
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.262
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.260
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.259
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.252
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.1.251
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.1.249
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.1.248
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.1.247
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.1.246
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.1.245
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.1.243
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.1.242
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.1.173
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.