← Home

@ledgerhq/lumen-ui-react-visualization

npm
17
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

reactuivisualizationchartsdesign-system

Accepted risks

Findings the reviewer chose to accept rather than block on.

SourceRuleReasonAccepted byWhen
source-diff obfuscated-file:dist/lib/Components/ReferenceLine/constants.d.ts AI (source-diff): Long line is a TypeScript union type of CSS variable names, not obfuscation. Stable pattern for this design-system package. ai
source-diff large-new-source-files AI (source-diff): Size growth matches addition of d3 visualization deps; expected for a chart/visualization package. ai
source-diff source-size-tripled AI (source-diff): Tripling explained by bundling d3-array/d3-scale/d3-shape for a new visualization component. ai
phantom-deps phantom-dep:d3-array AI (phantom-deps): d3-array is a declared runtime dep; phantom-dep heuristic false positive for this visualization package. ai
phantom-deps phantom-dep:d3-shape AI (phantom-deps): d3-shape is a declared runtime dep; phantom-dep heuristic false positive for this visualization package. ai
phantom-deps phantom-dep:@ledgerhq/lumen-utils-shared AI (phantom-deps): Same-org internal dep; phantom-dep heuristic false positive for this monorepo-style package. ai

Versions (showing 17 of 17)

Version Deps Published
0.1.17 4 / 3
0.1.16 4 / 3
0.1.15 4 / 3
0.1.14 4 / 3
0.1.13 4 / 3
0.1.12 4 / 3
0.1.11 4 / 3
0.1.10 4 / 3
0.1.9 4 / 3
0.1.8 4 / 3
0.1.7 4 / 3
0.1.6 4 / 3
0.1.5 4 / 3
0.1.4 4 / 3
0.1.3 4 / 3
0.1.2 0 / 0
0.1.1 0 / 0

v0.1.17

1 finding
LOW No provenance attestation provenance

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

v0.1.16

1 finding
LOW No provenance attestation provenance

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

v0.1.15

2 findings
HIGH New obfuscated file: dist/lib/Components/ReferenceLine/constants.d.ts source-diff

Newly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.

LOW No provenance attestation provenance

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

v0.1.14

2 findings
HIGH New obfuscated file: dist/lib/Components/ReferenceLine/constants.d.ts source-diff

Newly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.

LOW No provenance attestation provenance

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

v0.1.13

2 findings
HIGH New obfuscated file: dist/lib/Components/ReferenceLine/constants.d.ts source-diff

Newly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.

LOW No provenance attestation provenance

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

v0.1.12

2 findings
HIGH New obfuscated file: dist/lib/Components/ReferenceLine/constants.d.ts source-diff

Newly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.

LOW No provenance attestation provenance

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

v0.1.11

1 finding
LOW No provenance attestation provenance

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

v0.1.10

1 finding
LOW No provenance attestation provenance

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

v0.1.9

1 finding
LOW No provenance attestation provenance

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

v0.1.8

1 finding
LOW No provenance attestation provenance

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

v0.1.7

1 finding
LOW No provenance attestation provenance

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

v0.1.6

1 finding
LOW No provenance attestation provenance

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

v0.1.5

1 finding
LOW No provenance attestation provenance

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

v0.1.4

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.

v0.1.3

1 finding
LOW No provenance attestation provenance

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

v0.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.

v0.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.