o11y_schema
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
Keywords
Versions (showing 56 of 56)
| Version | Deps | Published |
|---|---|---|
| 264.70.0 | 0 / 0 | |
| 264.69.0 | 0 / 0 | |
| 264.68.0 | 0 / 0 | |
| 264.67.0 | 0 / 0 | |
| 264.66.0 | 0 / 0 | |
| 260.65.0 | 0 / 0 | |
| 260.63.0 | 0 / 0 | |
| 260.62.0 | 0 / 0 | |
| 260.61.0 | 0 / 0 | |
| 260.60.0 | 0 / 0 | |
| 260.59.0 | 0 / 0 | |
| 260.58.0 | 0 / 0 | |
| 260.57.0 | 0 / 0 | |
| 260.53.0 | 0 / 0 | |
| 260.52.0 | 0 / 0 | |
| 260.51.0 | 0 / 0 | |
| 260.50.0 | 0 / 0 | |
| 260.49.0 | 0 / 0 | |
| 260.48.0 | 0 / 0 | |
| 260.47.0 | 0 / 0 | |
| 260.46.0 | 0 / 0 | |
| 260.45.0 | 0 / 0 | |
| 260.44.0 | 0 / 0 | |
| 260.43.0 | 0 / 0 | |
| 260.42.0 | 0 / 0 | |
| 260.41.0 | 0 / 0 | |
| 260.40.0 | 0 / 0 | |
| 260.39.0 | 0 / 0 | |
| 260.37.0 | 0 / 0 | |
| 260.36.0 | 0 / 0 | |
| 260.35.0 | 0 / 0 | |
| 260.34.0 | 0 / 0 | |
| 260.33.0 | 0 / 0 | |
| 260.30.0 | 0 / 0 | |
| 260.23.0 | 0 / 0 | |
| 260.22.0 | 0 / 0 | |
| 260.20.0 | 0 / 0 | |
| 260.18.0 | 0 / 0 | |
| 260.17.0 | 0 / 0 | |
| 260.16.0 | 0 / 0 | |
| 260.15.0 | 0 / 0 | |
| 260.14.0 | 0 / 0 | |
| 260.13.0 | 0 / 0 | |
| 260.12.0 | 0 / 0 | |
| 260.11.0 | 0 / 0 | |
| 260.10.0 | 0 / 0 | |
| 260.9.0 | 0 / 0 | |
| 260.8.0 | 0 / 0 | |
| 260.7.0 | 0 / 0 | |
| 260.6.0 | 0 / 0 | |
| 260.5.0 | 0 / 0 | |
| 260.4.0 | 0 / 0 | |
| 260.3.0 | 0 / 0 | |
| 260.2.0 | 0 / 0 | |
| 260.1.0 | 0 / 0 | |
| 1.77.3 | 0 / 0 |
v264.70.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v264.69.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v264.68.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v264.67.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v264.66.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v260.63.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v260.62.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v260.61.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v260.60.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v260.59.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v260.58.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v260.57.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v260.48.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v260.40.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v260.37.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v260.18.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v260.12.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v260.11.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v260.10.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v260.9.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v260.8.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v260.7.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v260.6.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v260.5.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v260.4.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v260.3.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v260.2.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v260.1.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.