@codefresh-io/cf-telemetry
Base utils for monitoring.
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:@opentelemetry/baggage-span-processor | AI (dependencies): Part of the OpenTelemetry ecosystem; expected dependency for a telemetry package. | ai | |
| dependencies | unvetted-dep:@christiangalsterer/mongodb-driver-prometheus-exporter | AI (dependencies): Well-known MongoDB Prometheus exporter; fits the package's metrics/mongodb export path. | ai | |
| phantom-deps | phantom-dep:pino-pretty | AI (phantom-deps): Telemetry library re-exports/configures deps for consumers; not directly imported in source but legitimately declared. | ai | |
| phantom-deps | phantom-dep:@opentelemetry/core | AI (phantom-deps): Used transitively/in config by this telemetry wrapper; phantom-dep heuristic fires as false positive. | ai | |
| phantom-deps | phantom-dep:@opentelemetry/sdk-metrics | AI (phantom-deps): Used transitively/in config by this telemetry wrapper; phantom-dep heuristic fires as false positive. | ai | |
| phantom-deps | phantom-dep:@opentelemetry/sdk-trace-node | AI (phantom-deps): Used transitively/in config by this telemetry wrapper; phantom-dep heuristic fires as false positive. | ai |
Versions (showing 14 of 14)
| Version | Deps | Published |
|---|---|---|
| 4.2.2 | 13 / 11 | |
| 4.2.1 | 13 / 11 | |
| 4.2.0 | 13 / 11 | |
| 4.1.8 | 12 / 11 | |
| 4.1.7 | 12 / 11 | |
| 4.1.6 | 12 / 11 | |
| 4.1.5 | 12 / 11 | |
| 4.1.4 | 12 / 11 | |
| 4.1.3 | 12 / 11 | |
| 4.1.2 | 12 / 11 | |
| 3.8.3 | 12 / 11 | |
| 3.8.2 | 12 / 11 | |
| 3.8.1 | 12 / 11 | |
| 3.8.0 | 12 / 11 |
v4.2.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.2.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.1.8
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.1.5
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.8.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.8.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.8.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.8.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.