@sebspark/tracing
Use Opentelemetry for collecting traces and exporting to Cloud Trace
Supply chain provenance
Status for the latest visible version.
Without SLSA provenance there is no cryptographic link between this tarball and the public source, so a manually published version cannot be tied back to a reviewed commit.
Maintainers
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| phantom-deps | phantom-dep:@google-cloud/trace-agent | AI (phantom-deps): Framework-scoped package loaded by convention in tracing setups; stable false positive for this package. | ai | |
| phantom-deps | phantom-dep:@opentelemetry/core | AI (phantom-deps): Referenced in config files; indirect usage pattern stable for this tracing package. | ai | |
| phantom-deps | phantom-dep:@opentelemetry/exporter-zipkin | AI (phantom-deps): Config-referenced exporter; indirect usage pattern stable for this tracing package. | ai |
Versions (showing 6 of 6)
| Version | Deps | Published |
|---|---|---|
| 0.1.2 | 14 / 1 | |
| 0.1.1 | 12 / 1 | |
| 0.1.0 | 12 / 1 | |
| 0.0.3 | 12 / 1 | |
| 0.0.2 | 12 / 1 | |
| 0.0.1 | 12 / 1 |
v0.1.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.