@pagopa/azure-tracing
A package that contains some utilities to enable Azure tracing on Node.js applications.
Supply chain provenance
Status for the latest visible version.
Maintainers
Keywords
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| provenance | publisher-changed | AI (provenance): Publisher changed to GitHub Actions CI/CD with SLSA attestation — provenance IMPROVED, not a risk. | ai | |
| maintainer-change | maintainer-added | AI (maintainer-change): Maintainer transition within pagopa org; accompanied by CI/CD provenance attestation. | ai | |
| maintainer-change | maintainer-removed | AI (maintainer-change): Part of same maintainer transition; no hostile signals present. | ai | |
| provenance | missing-githead | AI (provenance): Package publishes via GitHub Actions with SLSA attestation; gitHead absence is a CI config artifact, not a supply-chain risk. | ai | |
| dependencies | unvetted-dep:@azure/monitor-opentelemetry-exporter | AI (dependencies): Official Microsoft Azure SDK package; stable dependency for this Azure tracing utility. | ai | |
| phantom-deps | phantom-dep:@azure/monitor-opentelemetry-exporter | AI (phantom-deps): Transitively used via @azure/monitor-opentelemetry; framework-scoped package loaded by convention, not direct import. | ai |
Versions (showing 11 of 11)
| Version | Deps | Published |
|---|---|---|
| 0.5.4 | 10 / 14 | |
| 0.5.0 | 10 / 9 | |
| 0.4.18 | 9 / 9 | |
| 0.4.14 | 9 / 9 | |
| 0.4.4 | 10 / 6 | |
| 0.3.3 | 10 / 6 | |
| 0.3.2 | 10 / 6 | |
| 0.3.1 | 10 / 6 | |
| 0.3.0 | 10 / 6 | |
| 0.2.0 | 10 / 7 | |
| 0.1.0 | 8 / 6 |
v0.4.14
3 findingsThis version was published by a different npm account than previous versions on 2026-03-25. This could indicate a legitimate maintainer transition or an account compromise.
Published via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
[Accepted risk] This version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: GitHub Actions.
v0.4.4
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.3.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.3.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.3.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.2.0
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. Only ~12% of npm packages have provenance, so this is common but not ideal.