@meistrari/otel
A lightweight OpenTelemetry library for Node.js applications with built-in support for Hono and Elysia frameworks.
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 |
|---|---|---|---|---|
| semgrep | semgrep:base64-decode | AI (semgrep): Decodes AWS SQS ReceiptHandle to extract queue ARN — standard AWS SDK pattern, not a payload hiding technique. | ai |
Versions (showing 34 of 34)
| Version | Deps | Published |
|---|---|---|
| 1.11.0 | 13 / 8 | |
| 1.10.2 | 13 / 8 | |
| 1.10.1 | 13 / 7 | |
| 1.10.0 | 13 / 7 | |
| 1.9.2 | 14 / 6 | |
| 1.9.1 | 14 / 4 | |
| 1.9.0 | 14 / 4 | |
| 1.8.5 | 14 / 4 | |
| 1.8.4 | 14 / 4 | |
| 1.8.3 | 14 / 4 | |
| 1.8.2 | 14 / 4 | |
| 1.8.1 | 14 / 4 | |
| 1.8.0 | 14 / 4 | |
| 1.7.1 | 14 / 4 | |
| 1.7.0 | 14 / 4 | |
| 1.6.1 | 14 / 4 | |
| 1.6.0 | 14 / 3 | |
| 1.5.2 | 14 / 3 | |
| 1.5.1 | 14 / 3 | |
| 1.5.0 | 14 / 3 | |
| 1.4.2 | 14 / 3 | |
| 1.4.1 | 14 / 3 | |
| 1.3.1 | 14 / 2 | |
| 1.3.0 | 14 / 2 | |
| 1.2.0 | 14 / 2 | |
| 1.1.1 | 14 / 2 | |
| 1.1.0 | 14 / 2 | |
| 1.0.8 | 12 / 2 | |
| 1.0.7 | 12 / 2 | |
| 1.0.6 | 12 / 2 | |
| 1.0.5 | 12 / 2 | |
| 1.0.4 | 12 / 2 | |
| 1.0.3 | 12 / 2 | |
| 1.0.1 | 12 / 2 |
v1.11.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.10.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.10.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.9.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.9.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.8.5
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.8.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.8.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.8.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.8.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.7.1
2 findingsThis version was published by a different npm account than previous versions on 2026-02-20. This could indicate a legitimate maintainer transition or an account compromise.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.7.0
2 findingsThis version was published by a different npm account (GitHub Actions) than the most recent previously approved version (rjmunhoz) on 2025-12-29. It has since remained available on npm for 204 days without being unpublished, which is inconsistent with an account takeover — those are typically removed by npm shortly after discovery.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.6.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.6.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.5.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.5.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.5.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.4.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.4.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.3.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.3.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.2.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.1.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.1.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.8
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.7
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.6
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.5
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.