@olane/o-tool-registry
oLane server tool registry
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 |
|---|---|---|---|---|
| phantom-deps | phantom-dep:debug | AI (phantom-deps): debug is referenced in dev scripts (DEBUG=o-protocol:*); not a real phantom dep for this package. | ai | |
| phantom-deps | phantom-dep:dotenv | AI (phantom-deps): dotenv referenced in config files; consistent with monorepo dev tooling pattern. | ai | |
| phantom-deps | phantom-dep:@olane/o-config | AI (phantom-deps): Same-org sibling dep; phantom-dep heuristic unreliable for monorepo internal packages. | ai | |
| phantom-deps | phantom-dep:@olane/o-tools-common | AI (phantom-deps): Same-org sibling dep; phantom-dep heuristic unreliable for monorepo internal packages. | ai | |
| phantom-deps | phantom-dep:@huggingface/transformers | AI (phantom-deps): Referenced in config files; consistent with optional/conditional import pattern in this package. | ai |
Versions (showing 20 of 120)
| Version | Deps | Published |
|---|---|---|
| 0.3.9 | 7 / 22 | |
| 0.3.8 | 7 / 22 | |
| 0.3.7 | 7 / 22 | |
| 0.3.6 | 7 / 22 | |
| 0.3.5 | 7 / 22 | |
| 0.3.4 | 7 / 22 | |
| 0.3.3 | 8 / 23 | |
| 0.3.2 | 8 / 23 | |
| 0.3.1 | 8 / 23 | |
| 0.2.3 | 8 / 23 | |
| 0.2.2 | 8 / 23 | |
| 0.2.1 | 7 / 22 | |
| 0.2.0 | 7 / 22 | |
| 0.1.6 | 7 / 32 | |
| 0.1.5 | 7 / 32 | |
| 0.1.4 | 7 / 32 | |
| 0.1.3 | 7 / 32 | |
| 0.1.2 | 7 / 32 | |
| 0.1.1 | 7 / 32 | |
| 0.1.0 | 7 / 31 |
v0.3.9
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.3.8
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.3.7
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.3.6
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.3.5
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.3.4
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.3.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.3.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.3.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.2.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.2.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.2.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.2.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.1.6
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.1.5
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.1.4
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.1.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.1.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.1.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.1.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.