@popmenu/common-ui MIT 51 versions

@popmenu/common-ui

npm

React components for all Popmenu apps on the web.

51

Versions

MIT

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

bantug_popmatthew.paravatibrandonbrown5lesley-rchrisohpopmenu

Versions (showing 51 of 73)

View all versions

Version	Deps	Published
0.168.0	0 / 0	2026-07-27
0.167.1	0 / 0	2026-07-27
0.166.0	0 / 0	2026-07-17
0.165.0	0 / 0	2026-07-14
0.164.0	0 / 0	2026-07-08
0.163.0	0 / 0	2026-07-08
0.162.0	0 / 0	2026-07-06
0.161.0	0 / 0	2026-06-29
0.160.0	0 / 0	2026-06-24
0.159.0	0 / 0	2026-06-11
0.156.0	0 / 0	2026-05-06
0.154.0	0 / 0	2026-04-24
0.153.0	0 / 0	2026-04-23
0.152.0	0 / 0	2026-04-09
0.151.0	0 / 0	2026-04-03
0.150.2	0 / 0	2026-03-27
0.147.0	0 / 0	2026-01-12
0.144.2	0 / 0	2025-12-17
0.142.0	0 / 0	2025-11-12
0.126.1	0 / 0	2025-06-09
0.122.0	0 / 1	2025-05-19
0.121.1	0 / 1	2025-05-07
0.121.0	0 / 1	2025-05-01
0.120.0	0 / 1	2025-05-01
0.119.0	0 / 1	2025-04-23
0.118.0	0 / 1	2025-04-17
0.117.0	0 / 1	2025-04-02
0.116.0	0 / 1	2025-03-27
0.115.0	0 / 1	2025-03-25
0.114.0	0 / 1	2025-03-24
0.113.4	0 / 1	2025-03-07
0.113.0	0 / 1	2025-03-03
0.112.0	0 / 1	2025-02-26
0.111.0	0 / 1	2025-02-24
0.110.0	0 / 1	2025-02-17
0.109.0	0 / 1	2025-02-03
0.108.0	0 / 1	2025-01-31
0.107.0	0 / 1	2025-01-28
0.106.0	0 / 1	2025-01-28
0.105.0	0 / 1	2025-01-17
0.104.0	0 / 1	2025-01-14
0.103.0	0 / 1	2025-01-06
0.102.0	0 / 1	2024-12-13
0.101.0	0 / 1	2024-12-06
0.100.0	0 / 1	2024-12-05
0.99.0	0 / 1	2024-11-27
0.98.0	0 / 1	2024-11-25
0.97.1	0 / 1	2024-11-20
0.97.0	0 / 1	2024-11-20
0.96.0	0 / 1	2024-11-19
0.95.1	0 / 1	2024-11-07

v0.168.0

1 finding

LOW No provenance attestation provenance

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

v0.167.1

1 finding

LOW No provenance attestation provenance

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

v0.166.0

1 finding

LOW No provenance attestation provenance

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

v0.165.0

1 finding

LOW No provenance attestation provenance

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

v0.164.0

1 finding

LOW No provenance attestation provenance

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

v0.163.0

1 finding

LOW No provenance attestation provenance

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

v0.162.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: lesley-r → bantug_pop (on 2026-07-06, known maintainer) provenance

This version was published by a different npm account (bantug_pop) than the most recent previously approved version (lesley-r) on 2026-07-06, but bantug_pop 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.

v0.161.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: bantug_pop → lesley-r (on 2026-06-29, known maintainer) provenance

This version was published by a different npm account (lesley-r) than the most recent previously approved version (bantug_pop) on 2026-06-29, but lesley-r 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.

v0.121.0

1 finding

LOW No provenance attestation provenance

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

v0.120.0

1 finding

LOW No provenance attestation provenance

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

v0.119.0

1 finding

LOW No provenance attestation provenance

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

v0.118.0

1 finding

LOW No provenance attestation provenance

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

v0.117.0

1 finding

LOW No provenance attestation provenance

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

v0.116.0

2 findings

MEDIUM Publisher changed: brandonbrown5 → nguyntyler (on 2025-03-27, unremoved on npm for 477d) provenance

This version was published by a different npm account (nguyntyler) than the most recent previously approved version (brandonbrown5) on 2025-03-27. It has since remained available on npm for 477 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.

v0.115.0

2 findings

MEDIUM Publisher changed: brandonbrown5 → nguyntyler (on 2025-03-25, unremoved on npm for 479d) provenance

This version was published by a different npm account (nguyntyler) than the most recent previously approved version (brandonbrown5) on 2025-03-25. It has since remained available on npm for 479 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.

v0.114.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: bantug_pop → brandonbrown5 (on 2025-03-24, known maintainer) provenance

This version was published by a different npm account (brandonbrown5) than the most recent previously approved version (bantug_pop) on 2025-03-24, but brandonbrown5 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.

v0.113.4

1 finding

LOW No provenance attestation provenance

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

v0.113.0

1 finding

LOW No provenance attestation provenance

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

v0.112.0

1 finding

LOW No provenance attestation provenance

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

v0.111.0

1 finding

LOW No provenance attestation provenance

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

v0.110.0

1 finding

LOW No provenance attestation provenance

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

v0.109.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: brandonbrown5 → bantug_pop (on 2025-02-03, known maintainer) provenance

This version was published by a different npm account (bantug_pop) than the most recent previously approved version (brandonbrown5) on 2025-02-03, but bantug_pop 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.

v0.108.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: brandonbrown5 → bantug_pop (on 2025-01-31, known maintainer) provenance

This version was published by a different npm account (bantug_pop) than the most recent previously approved version (brandonbrown5) on 2025-01-31, but bantug_pop 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.

v0.107.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: bantug_pop → brandonbrown5 (on 2025-01-28, known maintainer) provenance

This version was published by a different npm account (brandonbrown5) than the most recent previously approved version (bantug_pop) on 2025-01-28, but brandonbrown5 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.

v0.106.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: brandonbrown5 → bantug_pop (on 2025-01-28, known maintainer) provenance

This version was published by a different npm account (bantug_pop) than the most recent previously approved version (brandonbrown5) on 2025-01-28, but bantug_pop 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.

v0.105.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: brandonbrown5 → bantug_pop (on 2025-01-17, known maintainer) provenance

This version was published by a different npm account (bantug_pop) than the most recent previously approved version (brandonbrown5) on 2025-01-17, but bantug_pop 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.

v0.104.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: bantug_pop → brandonbrown5 (on 2025-01-14, known maintainer) provenance

This version was published by a different npm account (brandonbrown5) than the most recent previously approved version (bantug_pop) on 2025-01-14, but brandonbrown5 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.

v0.103.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: brandonbrown5 → bantug_pop (on 2025-01-06, known maintainer) provenance

This version was published by a different npm account (bantug_pop) than the most recent previously approved version (brandonbrown5) on 2025-01-06, but bantug_pop 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.

v0.102.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: bantug_pop → brandonbrown5 (on 2024-12-13, known maintainer) provenance

This version was published by a different npm account (brandonbrown5) than the most recent previously approved version (bantug_pop) on 2024-12-13, but brandonbrown5 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.

v0.101.0

1 finding

LOW No provenance attestation provenance

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

v0.100.0

1 finding

LOW No provenance attestation provenance

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

v0.99.0

1 finding

LOW No provenance attestation provenance

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

v0.98.0

1 finding

LOW No provenance attestation provenance

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

v0.97.1

1 finding

LOW No provenance attestation provenance

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

v0.97.0

1 finding

LOW No provenance attestation provenance

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

v0.96.0

1 finding

LOW No provenance attestation provenance

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

v0.95.1

1 finding

LOW No provenance attestation provenance

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