@olane/o-context
Generic async context primitive with platform-specific implementations (AsyncLocalStorage for Node, variable swap for browser/RN)
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
Versions (showing 14 of 14)
| Version | Deps | Published |
|---|---|---|
| 0.9.0 | 0 / 20 | |
| 0.8.21 | 0 / 20 | |
| 0.8.20 | 0 / 20 | |
| 0.8.19 | 0 / 20 | |
| 0.8.18 | 0 / 20 | |
| 0.8.17 | 0 / 19 | |
| 0.8.16 | 0 / 19 | |
| 0.8.15 | 0 / 19 | |
| 0.8.14 | 0 / 19 | |
| 0.8.13 | 0 / 19 | |
| 0.8.12 | 0 / 19 | |
| 0.8.11 | 0 / 19 | |
| 0.8.10 | 0 / 19 | |
| 0.8.9 | 0 / 19 |
v0.9.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.8.21
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.8.20
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.8.19
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.8.16
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.8.15
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.8.14
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.8.13
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.8.12
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.8.11
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.8.10
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.8.9
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.