elastic-apm-node
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 |
|---|---|---|---|---|
| semgrep | semgrep:dynamic-require | AI (semgrep): Reads the host app's own package.json for metadata; not arbitrary module loading. | ai | |
| semgrep | semgrep:child-process-import | AI (semgrep): Used only for hostname detection via spawnSync; documented APM agent behavior. | ai | |
| semgrep | semgrep:shady-links-raw-ip | AI (semgrep): 127.0.0.1:8200 is the default local APM server address; not exfiltration. | ai | |
| semgrep | semgrep:base64-decode | AI (semgrep): Decodes inline source maps; standard source-map processing. | ai | |
| semgrep | semgrep:hex-decode | AI (semgrep): Parses W3C trace-context binary format; standard tracing protocol handling. | ai | |
| phantom-deps | phantom-dep:module-details-from-path | AI (phantom-deps): Listed as runtime dep in package.json; phantom-dep heuristic false positive for this package. | ai |
Versions (showing 16 of 16)
| Version | Deps | Published |
|---|---|---|
| 4.15.0 | 37 / 81 | |
| 4.14.0 | 37 / 81 | |
| 4.13.0 | 37 / 80 | |
| 4.12.0 | 37 / 80 | |
| 4.11.2 | 37 / 80 | |
| 4.11.1 | 37 / 80 | |
| 4.11.0 | 37 / 81 | |
| 4.10.0 | 37 / 82 | |
| 4.9.0 | 37 / 82 | |
| 4.8.1 | 37 / 82 | |
| 4.8.0 | 37 / 82 | |
| 4.7.3 | 37 / 82 | |
| 4.7.2 | 37 / 82 | |
| 4.7.1 | 37 / 82 | |
| 4.7.0 | 37 / 84 | |
| 4.6.0 | 37 / 84 |
v4.15.0
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v4.14.0
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v4.13.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.12.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.11.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.11.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.11.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.10.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.9.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.8.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.8.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.7.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.7.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.7.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.7.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.6.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.