@loglayer/plugin-opentelemetry
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): Transition from theo.gravity to GitHub Actions is consistent with CI/CD automation; SLSA attestation confirms integrity. | ai | |
| publish-pattern | dormant-publish | AI (publish-pattern): Dormancy followed by GitHub Actions publish with SLSA provenance; no malicious indicators in diff. | ai | |
| phantom-deps | phantom-dep:@loglayer/shared | AI (phantom-deps): Same-org sibling dep; declared as runtime dependency, phantom-dep heuristic is a false positive here. | ai |
Versions (showing 13 of 13)
| Version | Deps | Published |
|---|---|---|
| 3.1.0 | 3 / 15 | |
| 3.0.2 | 3 / 15 | |
| 3.0.1 | 3 / 15 | |
| 3.0.0 | 3 / 15 | |
| 2.1.15 | 3 / 15 | |
| 2.1.14 | 3 / 15 | |
| 2.1.13 | 3 / 15 | |
| 2.1.12 | 3 / 15 | |
| 2.1.11 | 3 / 15 | |
| 2.1.10 | 3 / 15 | |
| 2.1.9 | 3 / 15 | |
| 2.1.8 | 3 / 15 | |
| 2.1.7 | 3 / 15 |
v3.1.0
2 findingsThis version was published by a different npm account than previous versions on 2026-05-26. 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.
v3.0.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.0.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.1.15
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.1.14
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.1.13
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.1.12
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.1.11
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.1.10
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.1.9
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.1.8
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.1.7
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.