@orderly.network/chart No license 32 versions

@orderly.network/chart

npm

Charting library for Orderly Network

32

Versions

—

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

orderly.productkai.jiangstognievleo_orderlygoogolev

Accepted risks

Findings the reviewer chose to accept rather than block on.

Source	Rule	Reason	Accepted by	When
typosquat	typosquat.levenshtein:chalk	AI (typosquat): Scoped charting package for Orderly Network; not a typosquat of chalk — different namespace, purpose, and audience.	ai	2026/04/29
phantom-deps	phantom-dep:d3-axis	AI (phantom-deps): d3 sub-packages are runtime deps used in build output; phantom-dep heuristic fires because direct import is in bundled dist.	ai	2026/04/29
phantom-deps	phantom-dep:d3-array	AI (phantom-deps): Same as d3-axis — bundled d3 usage not directly imported at source level.	ai	2026/04/29
phantom-deps	phantom-dep:d3-scale	AI (phantom-deps): Same as d3-axis — bundled d3 usage not directly imported at source level.	ai	2026/04/29
phantom-deps	phantom-dep:d3-shape	AI (phantom-deps): Same as d3-axis — bundled d3 usage not directly imported at source level.	ai	2026/04/29
phantom-deps	phantom-dep:d3-selection	AI (phantom-deps): Same as d3-axis — bundled d3 usage not directly imported at source level.	ai	2026/04/29

Versions (showing 32 of 32)

Version	Deps	Published
3.1.0	9 / 12	2026-05-27
3.0.4	9 / 12	2026-05-20
3.0.3	9 / 12	2026-05-07
3.0.2	9 / 12	2026-04-30
3.0.1	9 / 12	2026-04-29
3.0.0	9 / 12	2026-04-28
2.12.4	9 / 12	2026-04-21
2.12.3	9 / 12	2026-04-19
2.12.2	9 / 12	2026-04-14
2.12.1	9 / 12	2026-04-10
2.12.0	9 / 12	2026-04-01
2.11.2	9 / 12	2026-03-24
2.11.1	9 / 12	2026-03-18
2.11.0	9 / 12	2026-03-17
2.10.2	9 / 12	2026-03-16
2.10.1	9 / 12	2026-03-04
2.10.0	9 / 12	2026-03-03
2.9.1	9 / 12	2026-02-14
2.9.0	9 / 12	2026-02-13
2.8.14	9 / 12	2026-02-10
2.8.13	9 / 12	2026-01-30
2.8.12	9 / 12	2026-01-15
2.8.11	9 / 12	2026-01-14
2.8.10	9 / 12	2025-12-23
2.8.9	9 / 12	2025-12-20
2.8.8	9 / 12	2025-12-10
2.8.7	9 / 12	2025-12-09
2.8.6	9 / 12	2025-12-02
2.8.5	9 / 12	2025-11-26
2.8.4	9 / 12	2025-11-25
2.8.3	9 / 12	2025-11-19
2.8.2	9 / 12	2025-11-12

v3.1.0

1 finding

LOW No provenance attestation provenance

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

v3.0.4

1 finding

LOW No provenance attestation provenance

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

v3.0.3

1 finding

LOW No provenance attestation provenance

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

v3.0.2

1 finding

LOW No provenance attestation provenance

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

v2.12.4

1 finding

LOW No provenance attestation provenance

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

v2.12.3

1 finding

LOW No provenance attestation provenance

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

v2.12.2

1 finding

LOW No provenance attestation provenance

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

v2.12.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.12.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.11.2

1 finding

LOW No provenance attestation provenance

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

v2.11.1

1 finding

LOW No provenance attestation provenance

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

v2.11.0

1 finding

LOW No provenance attestation provenance

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

v2.10.2

1 finding

LOW No provenance attestation provenance

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

v2.10.1

1 finding

LOW No provenance attestation provenance

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

v2.10.0

1 finding

LOW No provenance attestation provenance

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

v2.9.1

1 finding

LOW No provenance attestation provenance

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

v2.9.0

1 finding

LOW No provenance attestation provenance

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

v2.8.14

1 finding

LOW No provenance attestation provenance

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

v2.8.13

1 finding

LOW No provenance attestation provenance

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

v2.8.12

1 finding

LOW No provenance attestation provenance

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

v2.8.11

1 finding

LOW No provenance attestation provenance

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

v2.8.10

1 finding

LOW No provenance attestation provenance

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

v2.8.9

1 finding

LOW No provenance attestation provenance

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

v2.8.8

1 finding

LOW No provenance attestation provenance

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

v2.8.7

1 finding

LOW No provenance attestation provenance

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

v2.8.6

1 finding

LOW No provenance attestation provenance

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

v2.8.5

1 finding

LOW No provenance attestation provenance

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

v2.8.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.

v2.8.3

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