@atlaskit/range Apache-2.0 22 versions

@atlaskit/range

npm Repository Homepage

A range lets users choose an approximate value on a slider.

22

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

atlassianartifactteam

Keywords

atlaskitreactui

Accepted risks

Findings the reviewer chose to accept rather than block on.

Source	Rule	Reason	Accepted by	When
phantom-deps	phantom-dep:@atlaskit/css	AI (phantom-deps): Same-org Atlaskit dependency; phantom detection is a false positive for monorepo packages where deps may be used via compiled CSS artifacts rather than direct JS imports.	ai	2026/04/25
phantom-deps	phantom-dep:@atlaskit/theme	AI (phantom-deps): Same-org Atlaskit dependency; phantom detection is a false positive for monorepo packages where deps may be used via compiled CSS artifacts rather than direct JS imports.	ai	2026/04/25
phantom-deps	phantom-dep:@atlaskit/tokens	AI (phantom-deps): Same-org Atlaskit dependency; phantom detection is a false positive for monorepo packages where deps may be used via compiled CSS artifacts rather than direct JS imports.	ai	2026/04/25

Versions (showing 22 of 22)

Version	Deps	Published
10.1.2	7 / 18	2026-05-25
10.1.1	7 / 18	2026-05-22
10.1.0	7 / 17	2026-04-30
10.0.7	7 / 17	2026-04-14
10.0.6	7 / 17	2026-04-13
10.0.5	7 / 17	2026-04-10
10.0.4	7 / 17	2026-04-09
10.0.3	7 / 17	2026-04-08
10.0.2	7 / 16	2026-04-02
10.0.1	7 / 16	2026-03-30
10.0.0	7 / 16	2026-03-19
9.3.7	7 / 15	2026-03-16
9.3.6	7 / 15	2026-03-04
9.3.5	7 / 15	2026-02-03
9.3.4	7 / 15	2026-02-02
9.3.3	7 / 15	2026-01-16
9.3.2	7 / 15	2025-12-18
9.3.1	7 / 15	2025-12-16
9.3.0	7 / 15	2025-12-10
9.2.15	7 / 16	2025-11-24
9.2.14	7 / 16	2025-11-20
9.2.13	7 / 16	2025-11-07

v10.1.2

1 finding

LOW No provenance attestation provenance

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

v10.1.1

1 finding

LOW No provenance attestation provenance

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

v10.1.0

1 finding

LOW No provenance attestation provenance

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

v10.0.7

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.

v10.0.6

1 finding

LOW No provenance attestation provenance

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

v10.0.5

1 finding

LOW No provenance attestation provenance

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

v10.0.4

1 finding

LOW No provenance attestation provenance

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

v10.0.3

1 finding

LOW No provenance attestation provenance

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

v10.0.2

1 finding

LOW No provenance attestation provenance

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

v10.0.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.

v10.0.0

1 finding

LOW No provenance attestation provenance

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

v9.3.7

1 finding

LOW No provenance attestation provenance

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

v9.3.6

1 finding

LOW No provenance attestation provenance

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

v9.3.5

1 finding

LOW No provenance attestation provenance

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

v9.3.4

1 finding

LOW No provenance attestation provenance

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

v9.3.3

1 finding

LOW No provenance attestation provenance

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

v9.3.2

1 finding

LOW No provenance attestation provenance

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

v9.3.1

1 finding

LOW No provenance attestation provenance

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

v9.3.0

1 finding

LOW No provenance attestation provenance

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

v9.2.15

1 finding

LOW No provenance attestation provenance

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

v9.2.14

1 finding

LOW No provenance attestation provenance

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

v9.2.13

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.