@athenna/otel
OpenTelemetry package for Athenna.
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
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| phantom-deps | phantom-dep:@opentelemetry/core | AI (phantom-deps): OpenTelemetry wrapper; dependencies declared for re-export and config use. | ai | |
| phantom-deps | phantom-dep:@opentelemetry/semantic-conventions | AI (phantom-deps): OpenTelemetry wrapper; dependencies declared for re-export and config use. | ai | |
| phantom-deps | phantom-dep:@opentelemetry/auto-instrumentations-node | AI (phantom-deps): OpenTelemetry wrapper; dependencies declared for re-export and config use. | ai | |
| phantom-deps | phantom-dep:@opentelemetry/api-logs | AI (phantom-deps): Config-referenced OpenTelemetry dependency; stable pattern for instrumentation packages. | ai | |
| phantom-deps | phantom-dep:@opentelemetry/instrumentation-runtime-node | AI (phantom-deps): Config-referenced OpenTelemetry dependency; stable pattern for instrumentation packages. | ai | |
| phantom-deps | phantom-dep:@opentelemetry/resources | AI (phantom-deps): Config-referenced OpenTelemetry dependency; stable pattern for instrumentation packages. | ai | |
| phantom-deps | phantom-dep:@opentelemetry/instrumentation | AI (phantom-deps): Config-referenced OpenTelemetry dependency; stable pattern for instrumentation packages. | ai |
Versions (showing 25 of 25)
| Version | Deps | Published |
|---|---|---|
| 5.24.0 | 22 / 22 | |
| 5.23.0 | 22 / 22 | |
| 5.22.0 | 17 / 22 | |
| 5.21.0 | 16 / 22 | |
| 5.20.0 | 16 / 22 | |
| 5.19.0 | 16 / 22 | |
| 5.18.0 | 16 / 22 | |
| 5.17.0 | 16 / 22 | |
| 5.16.0 | 16 / 22 | |
| 5.15.0 | 16 / 22 | |
| 5.14.0 | 16 / 22 | |
| 5.13.0 | 16 / 22 | |
| 5.12.0 | 16 / 22 | |
| 5.11.0 | 16 / 22 | |
| 5.10.0 | 16 / 22 | |
| 5.9.0 | 16 / 22 | |
| 5.8.0 | 16 / 22 | |
| 5.7.0 | 16 / 21 | |
| 5.6.0 | 12 / 20 | |
| 5.5.0 | 12 / 20 | |
| 5.4.0 | 12 / 20 | |
| 5.3.0 | 12 / 20 | |
| 5.2.0 | 12 / 20 | |
| 5.1.0 | 12 / 20 | |
| 5.0.0 | 12 / 20 |
v5.24.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v5.23.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.22.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.21.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.20.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.19.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.18.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.17.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.16.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.15.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.14.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v5.13.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v5.12.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v5.11.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v5.10.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v5.9.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v5.8.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v5.7.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v5.6.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v5.5.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v5.4.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v5.3.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v5.2.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v5.1.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v5.0.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.