@elastic/apm-rum-react
Supply chain provenance
Status for the latest visible version.
Maintainers
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| bogus-package | bogus-package | AI (bogus-package): Established Elastic SDK package; sparse README/keywords are cosmetic, not spam indicators. | ai | |
| dependencies | unvetted-dep:@elastic/apm-rum | AI (dependencies): Same Elastic org namespace; core dependency of this SDK, not a suspicious third-party dep. | ai |
Versions (showing 8 of 8)
| Version | Deps | Published |
|---|---|---|
| 2.0.11 | 2 / 0 | |
| 2.0.10 | 2 / 0 | |
| 2.0.9 | 2 / 0 | |
| 2.0.8 | 2 / 0 | |
| 2.0.6 | 2 / 0 | |
| 2.0.5 | 2 / 0 | |
| 2.0.4 | 2 / 0 | |
| 2.0.3 | 2 / 0 |
v2.0.11
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v2.0.6
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.0.5
2 findingsThis version was published by a different npm account (obltmachine) than the most recent previously approved version (elasticmachine) on 2025-01-10. It has since remained available on npm for 554 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.
v2.0.4
2 findingsThis version was published by a different npm account (obltmachine) than the most recent previously approved version (elasticmachine) on 2025-01-09. It has since remained available on npm for 555 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.
v2.0.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.