react-accessible-treeview No license 36 versions

react-accessible-treeview

npm Repository Homepage

36

Versions

—

License

No

Install Scripts

Missing

Provenance

Supply chain provenance

Status for the latest visible version.

No SLSA provenance npm registry signatures gitHead linked

Without SLSA provenance there is no cryptographic link between this tarball and the public source, so a manually published version cannot be tied back to a reviewed commit.

Maintainers

dgreene1lissitzyhy1mellis481

Keywords

reacttreeviewa11yaccessibilityreact-componenttree

Versions (showing 36 of 36)

Version	Deps	Published
2.11.2	0 / 40	2025-06-27
2.11.1	0 / 40	2025-03-10
2.11.0	0 / 40	2025-01-27
2.10.0	0 / 40	2024-11-05
2.9.1	0 / 40	2024-06-13
2.9.0	0 / 40	2024-04-26
2.8.3	0 / 40	2024-01-12
2.8.2	0 / 40	2024-01-05
2.8.1	0 / 40	2023-12-05
2.8.0	0 / 40	2023-08-24
2.7.0	0 / 40	2023-08-23
2.6.3	0 / 40	2023-07-21
2.6.2	0 / 40	2023-07-12
2.6.1	0 / 40	2023-06-16
2.6.0	0 / 40	2023-06-08
2.5.6	0 / 40	2023-05-26
2.5.5	0 / 40	2023-05-26
2.5.4	0 / 40	2023-05-22
2.5.3	0 / 40	2023-05-19
2.5.2	0 / 40	2023-05-18
2.5.1	0 / 40	2023-05-12
2.5.0	0 / 40	2023-05-09
2.4.0	0 / 40	2023-04-27
2.3.5	0 / 40	2023-04-11
2.3.4	0 / 40	2023-03-16
2.3.3	0 / 40	2023-03-06
2.3.2	0 / 40	2023-02-07
2.3.1	0 / 40	2022-10-26
2.3.0	0 / 40	2022-10-18
2.2.0	0 / 40	2022-09-29
2.1.4	0 / 33	2022-07-17
2.1.3	0 / 28	2019-08-20
2.1.2	0 / 28	2019-08-19
2.1.1	0 / 28	2019-08-19
2.1.0	0 / 26	2019-08-19
2.0.0	0 / 29	2019-08-17

v2.11.1

2 findings

LOW No provenance attestation provenance

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

INFO Publisher changed: mellis481 → yhy1 (on 2025-03-10, known maintainer) provenance

This version was published by a different npm account (yhy1) than the most recent previously approved version (mellis481) on 2025-03-10, but yhy1 is listed as a maintainer on prior approved versions (matched on name). This looks like a manual publish by a known maintainer rather than a publisher change. Recorded as INFO for audit trail.

v2.11.0

2 findings

LOW No provenance attestation provenance

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

INFO Publisher changed: mellis481 → yhy1 (on 2025-01-27, known maintainer) provenance

This version was published by a different npm account (yhy1) than the most recent previously approved version (mellis481) on 2025-01-27, but yhy1 is listed as a maintainer on prior approved versions (matched on name). This looks like a manual publish by a known maintainer rather than a publisher change. Recorded as INFO for audit trail.

v2.10.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.9.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.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.3

1 finding

LOW No provenance attestation provenance

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

v2.8.2

1 finding

LOW No provenance attestation provenance

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

v2.8.1

2 findings

LOW No provenance attestation provenance

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

INFO Publisher changed: mellis481 → yhy1 (on 2023-12-05, known maintainer) provenance

This version was published by a different npm account (yhy1) than the most recent previously approved version (mellis481) on 2023-12-05, but yhy1 is listed as a maintainer on prior approved versions (matched on name). This looks like a manual publish by a known maintainer rather than a publisher change. Recorded as INFO for audit trail.

v2.8.0

1 finding

LOW No provenance attestation provenance

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

v2.7.0

1 finding

LOW No provenance attestation provenance

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

v2.6.3

2 findings

LOW No provenance attestation provenance

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

INFO Publisher changed: yhy1 → mellis481 (on 2023-07-21, known maintainer) provenance

This version was published by a different npm account (mellis481) than the most recent previously approved version (yhy1) on 2023-07-21, but mellis481 is listed as a maintainer on prior approved versions (matched on name). This looks like a manual publish by a known maintainer rather than a publisher change. Recorded as INFO for audit trail.

v2.6.2

2 findings

LOW No provenance attestation provenance

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

INFO Publisher changed: yhy1 → mellis481 (on 2023-07-12, known maintainer) provenance

This version was published by a different npm account (mellis481) than the most recent previously approved version (yhy1) on 2023-07-12, but mellis481 is listed as a maintainer on prior approved versions (matched on name). This looks like a manual publish by a known maintainer rather than a publisher change. Recorded as INFO for audit trail.

v2.6.1

2 findings

LOW No provenance attestation provenance

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

INFO Publisher changed: mellis481 → yhy1 (on 2023-06-16, known maintainer) provenance

This version was published by a different npm account (yhy1) than the most recent previously approved version (mellis481) on 2023-06-16, but yhy1 is listed as a maintainer on prior approved versions (matched on name). This looks like a manual publish by a known maintainer rather than a publisher change. Recorded as INFO for audit trail.

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

1 finding

LOW No provenance attestation provenance

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

v2.5.5

2 findings

LOW No provenance attestation provenance

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

INFO Publisher changed: mellis481 → yhy1 (on 2023-05-26, known maintainer) provenance

This version was published by a different npm account (yhy1) than the most recent previously approved version (mellis481) on 2023-05-26, but yhy1 is listed as a maintainer on prior approved versions (matched on name). This looks like a manual publish by a known maintainer rather than a publisher change. Recorded as INFO for audit trail.

v2.5.4

1 finding

LOW No provenance attestation provenance

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

v2.5.3

1 finding

LOW No provenance attestation provenance

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

v2.5.2

1 finding

LOW No provenance attestation provenance

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

v2.5.1

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

2 findings

LOW No provenance attestation provenance

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

INFO Publisher changed: yhy1 → mellis481 (on 2023-05-09, known maintainer) provenance

This version was published by a different npm account (mellis481) than the most recent previously approved version (yhy1) on 2023-05-09, but mellis481 is listed as a maintainer on prior approved versions (matched on name). This looks like a manual publish by a known maintainer rather than a publisher change. Recorded as INFO for audit trail.

v2.4.0

2 findings

LOW No provenance attestation provenance

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

INFO Publisher changed: yhy1 → mellis481 (on 2023-04-27, known maintainer) provenance

This version was published by a different npm account (mellis481) than the most recent previously approved version (yhy1) on 2023-04-27, but mellis481 is listed as a maintainer on prior approved versions (matched on name). This looks like a manual publish by a known maintainer rather than a publisher change. Recorded as INFO for audit trail.

v2.3.5

1 finding

LOW No provenance attestation provenance

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

v2.3.4

2 findings

LOW No provenance attestation provenance

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

INFO Publisher changed: yhy1 → mellis481 (on 2023-03-16, known maintainer) provenance

This version was published by a different npm account (mellis481) than the most recent previously approved version (yhy1) on 2023-03-16, but mellis481 is listed as a maintainer on prior approved versions (matched on name). This looks like a manual publish by a known maintainer rather than a publisher change. Recorded as INFO for audit trail.

v2.3.3

1 finding

LOW No provenance attestation provenance

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

v2.3.2

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

2 findings

MEDIUM Publisher changed: lissitz → yhy1 (on 2022-09-29, unremoved on npm for 1395d) provenance

This version was published by a different npm account (yhy1) than the most recent previously approved version (lissitz) on 2022-09-29. It has since remained available on npm for 1395 days without being unpublished, which is inconsistent with an account takeover — those are typically removed by npm shortly after discovery.

LOW No provenance attestation provenance

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

v2.1.4

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. Consider requesting the maintainer enable provenance via CI/CD.

v2.1.1

1 finding

LOW No provenance attestation provenance

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

v2.1.0

1 finding

LOW No provenance attestation provenance

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

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.