← Home

@ledgerhq/coin-modules-monitoring

npm Repository Homepage

Push monitoring metrics to Datadog

37
Versions
Apache-2.0
License
No
Install Scripts
Missing
Provenance

Supply chain provenance

Status for the latest visible version.

No SLSA provenance npm registry signatures No source commit

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

phenry-ledgersergii-shkolingbrahm-ledgerthomas.coudrayldg-github-civbouzonledger-releaser

Keywords

LedgerLedgerWalletmonitoringmetricsDatadog

Accepted risks

Findings the reviewer chose to accept rather than block on.

SourceRuleReasonAccepted byWhen
dependencies unvetted-dep:@datadog/datadog-api-client AI (dependencies): Package's stated purpose is pushing metrics to Datadog; @datadog/datadog-api-client is the official Datadog client and is expected as a core dependency. ai
semgrep semgrep:child-process-import AI (semgrep): This is a CLI tool (start: node lib/cli.js); child_process use in a CLI entrypoint is expected. No install-time execution. ai
phantom-deps phantom-dep:@ledgerhq/live-network AI (phantom-deps): Same-org phantom dep is a minor packaging issue, not a security concern. Stable false positive for this package. ai

Versions (showing 37 of 37)

Version Deps Published
2.21.0 8 / 12
2.20.0 8 / 12
2.19.0 8 / 12
2.18.1 8 / 12
2.18.0 8 / 12
2.17.0 8 / 12
2.16.0 8 / 12
2.15.1 8 / 12
2.15.0 8 / 12
2.14.1 7 / 12
2.14.0 7 / 12
2.13.0 7 / 12
2.12.1 7 / 12
2.12.0 7 / 12
2.11.0 7 / 12
2.10.1 8 / 12
2.10.0 8 / 12
2.9.0 8 / 12
2.8.0 8 / 13
2.7.2 8 / 13
2.7.1 8 / 13
2.7.0 8 / 13
2.6.4 8 / 13
2.6.3 8 / 13
2.6.2 8 / 13
2.6.1 8 / 13
2.6.0 8 / 13
2.5.0 6 / 12
2.4.0 5 / 12
2.3.1 5 / 12
2.3.0 5 / 12
2.2.0 5 / 12
2.1.3 5 / 12
2.1.2 5 / 12
2.1.1 5 / 12
2.1.0 5 / 12
2.0.0 5 / 11

v2.21.0

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v2.20.0

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v2.19.0

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v2.18.1

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v2.18.0

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v2.17.0

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v2.16.0

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v2.15.1

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v2.15.0

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v2.6.0

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v2.5.0

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v2.4.0

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v2.3.1

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v2.3.0

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v2.2.0

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v2.1.3

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v2.1.2

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v2.1.1

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v2.1.0

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v2.0.0

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.