o11y
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 |
|---|---|---|---|---|
| dependencies | unvetted-dep:protobufjs | AI (dependencies): protobufjs is a well-known protobuf serialization library; its use in an observability/telemetry package for data serialization is expected and appropriate across all versions. | ai | |
| phantom-deps | phantom-dep:web-vitals | AI (phantom-deps): web-vitals is intentionally externalized via rollup config and exposed as a module export; not a direct import by design. Stable pattern for this package. | ai | |
| provenance | no-provenance | AI (provenance): Established Salesforce instrumentation package with 164 versions and clean publisher history; lack of Sigstore provenance is not a risk signal here. | ai |
Versions (showing 18 of 18)
| Version | Deps | Published |
|---|---|---|
| 264.6.0 | 3 / 21 | |
| 264.5.0 | 3 / 21 | |
| 262.6.0 | 3 / 21 | |
| 262.5.0 | 3 / 21 | |
| 262.4.0 | 3 / 21 | |
| 260.24.0 | 3 / 21 | |
| 260.23.0 | 3 / 21 | |
| 260.22.0 | 3 / 21 | |
| 260.21.0 | 3 / 21 | |
| 260.20.0 | 3 / 21 | |
| 260.19.0 | 3 / 21 | |
| 260.12.0 | 3 / 23 | |
| 260.11.0 | 3 / 23 | |
| 260.10.0 | 3 / 23 | |
| 260.0.0 | 3 / 23 | |
| 258.22.0 | 3 / 21 | |
| 258.21.0 | 3 / 21 | |
| 258.19.0 | 3 / 21 |
v264.6.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v264.5.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v262.6.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v262.4.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.