@olane/o-tool
oLane base tool class
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 |
|---|---|---|---|---|
| bogus-package | bogus-package | AI (bogus-package): Early-stage package (v0.1.1) with minimal README is normal; no spam indicators present. | ai | |
| phantom-deps | phantom-dep:debug | AI (phantom-deps): debug is declared in dependencies and used in dev script; stable false positive. | ai | |
| phantom-deps | phantom-dep:dotenv | AI (phantom-deps): dotenv is declared in dependencies; stable false positive. | ai |
Versions (showing 20 of 120)
| Version | Deps | Published |
|---|---|---|
| 0.3.9 | 2 / 22 | |
| 0.3.8 | 2 / 21 | |
| 0.3.7 | 2 / 21 | |
| 0.3.6 | 2 / 21 | |
| 0.3.5 | 2 / 20 | |
| 0.3.4 | 2 / 20 | |
| 0.3.3 | 3 / 21 | |
| 0.3.2 | 3 / 21 | |
| 0.3.1 | 3 / 21 | |
| 0.2.3 | 3 / 21 | |
| 0.2.2 | 3 / 21 | |
| 0.2.1 | 2 / 20 | |
| 0.2.0 | 2 / 20 | |
| 0.1.6 | 2 / 30 | |
| 0.1.5 | 2 / 30 | |
| 0.1.4 | 2 / 30 | |
| 0.1.3 | 2 / 30 | |
| 0.1.2 | 2 / 30 | |
| 0.1.1 | 2 / 30 | |
| 0.1.0 | 2 / 29 |
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.