@olane/o-config
oLane Network Config
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:@libp2p/webtransport | AI (phantom-deps): Config package declares transport deps for consumer use; not directly imported by design. | ai | |
| phantom-deps | phantom-dep:@libp2p/webrtc | AI (phantom-deps): Config package declares transport deps for consumer use; not directly imported by design. | ai | |
| phantom-deps | phantom-dep:@libp2p/websockets | AI (phantom-deps): Config package declares transport deps for consumer use; not directly imported by design. | ai | |
| phantom-deps | phantom-dep:@libp2p/interface-connection | AI (phantom-deps): Interface dep declared for consumer use; not directly imported by design. | ai | |
| phantom-deps | phantom-dep:@libp2p/interface-registrar | AI (phantom-deps): Interface dep declared for consumer use; not directly imported by design. | ai | |
| phantom-deps | phantom-dep:@libp2p/interface-transport | AI (phantom-deps): Interface dep declared for consumer use; not directly imported by design. | ai | |
| phantom-deps | phantom-dep:@libp2p/pubsub | AI (phantom-deps): @libp2p/pubsub is a declared runtime dependency in a libp2p config package; phantom-dep heuristic is a false positive here. | ai |
Versions (showing 18 of 118)
| Version | Deps | Published |
|---|---|---|
| 0.4.0 | 19 / 21 | |
| 0.3.9 | 19 / 21 | |
| 0.3.8 | 18 / 20 | |
| 0.3.7 | 18 / 20 | |
| 0.3.6 | 17 / 20 | |
| 0.3.5 | 17 / 20 | |
| 0.3.4 | 17 / 20 | |
| 0.3.3 | 20 / 20 | |
| 0.3.2 | 21 / 20 | |
| 0.3.1 | 21 / 20 | |
| 0.2.1 | 31 / 20 | |
| 0.1.6 | 31 / 31 | |
| 0.1.5 | 31 / 31 | |
| 0.1.4 | 31 / 31 | |
| 0.1.3 | 31 / 31 | |
| 0.1.2 | 31 / 31 | |
| 0.1.1 | 31 / 27 | |
| 0.1.0 | 31 / 26 |
v0.4.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
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.1
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.