@bgord/ui MIT 43 versions

@bgord/ui

npm

Clone the repository

43

Versions

MIT

License

Yes

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 — the axios compromise (March 2026) relied on exactly this gap.

Maintainers

bgord

Accepted risks

Findings the reviewer chose to accept rather than block on.

Source	Rule	Reason	Accepted by	When
provenance	no-provenance	AI (provenance): Small personal UI library; no provenance is consistent across all 72 versions; not a meaningful risk signal here.	ai	2026/05/23
publish-pattern	new-deps-added	AI (publish-pattern): polish-plurals is a well-scoped pluralization utility; no malicious indicators.	ai	2026/05/12
bogus-package	bogus-package	AI (bogus-package): Personal scoped UI library (@bgord/ui); no repo/keywords expected for internal tooling with 70 published versions.	ai	2026/05/06
dependencies	unvetted-dep:polish-plurals	AI (dependencies): Small i18n utility; no known malicious history, consistent with a UI library targeting Polish locale.	ai	2026/05/06
dependencies	unvetted-dep:tinykeys	AI (dependencies): tinykeys is a well-known keyboard shortcut library; stable false positive for this UI package.	ai	2026/05/06
phantom-deps	phantom-dep:js-cookie	AI (phantom-deps): UI library likely re-exports or conditionally uses js-cookie; phantom-dep heuristic is unreliable for this package.	ai	2026/05/06
phantom-deps	phantom-dep:tinykeys	AI (phantom-deps): UI library likely re-exports or conditionally uses tinykeys; phantom-dep heuristic is unreliable for this package.	ai	2026/05/06
phantom-deps	phantom-dep:polish-plurals	AI (phantom-deps): UI library likely re-exports or conditionally uses polish-plurals; phantom-dep heuristic is unreliable for this package.	ai	2026/05/06
typosquat	typosquat.levenshtein:uuid	AI (typosquat): Scoped package @bgord/ui is not a typosquat of uuid; Levenshtein false positive.	ai	2026/04/30
typosquat	typosquat.levenshtein:yup	AI (typosquat): Scoped package @bgord/ui is not a typosquat of yup; Levenshtein false positive.	ai	2026/04/30
typosquat	typosquat.levenshtein:joi	AI (typosquat): Scoped package @bgord/ui is not a typosquat of joi; Levenshtein false positive.	ai	2026/04/30
typosquat	typosquat.levenshtein:qs	AI (typosquat): Scoped package @bgord/ui is not a typosquat of qs; Levenshtein false positive.	ai	2026/04/30
typosquat	typosquat.levenshtein:pg	AI (typosquat): Scoped package @bgord/ui is not a typosquat of pg; Levenshtein false positive.	ai	2026/04/30
install-scripts	install-script:preinstall	AI (install-scripts): bunx only-allow bun is a standard package-manager enforcement tool; stable pattern for this package.	ai	2026/04/30

Versions (showing 43 of 43)

Version	Deps	Published
0.8.37	3 / 22	2026-05-13
0.8.34	3 / 22	2026-04-28
0.8.33	3 / 22	2026-04-28
0.8.30	3 / 21	2026-04-11
0.8.29	3 / 20	2026-03-24
0.8.25	3 / 20	2026-03-13
0.8.24	3 / 20	2026-03-01
0.8.23	3 / 20	2026-02-11
0.8.22	3 / 20	2026-02-08
0.8.21	3 / 20	2026-02-06
0.8.20	3 / 20	2026-01-14
0.8.19	3 / 20	2026-01-14
0.8.18	3 / 20	2026-01-12
0.8.17	3 / 20	2026-01-09
0.8.16	3 / 19	2025-12-29
0.8.14	3 / 18	2025-12-14
0.8.13	3 / 18	2025-12-12
0.8.12	3 / 18	2025-12-11
0.8.11	3 / 18	2025-12-09
0.8.10	3 / 18	2025-12-03
0.8.9	3 / 17	2025-12-01
0.8.8	3 / 17	2025-11-14
0.8.3	3 / 17	2025-11-03
0.8.1	3 / 17	2025-11-01
0.8.0	3 / 17	2025-11-01
0.7.9	3 / 17	2025-11-01
0.7.8	3 / 17	2025-11-01
0.6.1	4 / 17	2025-10-23
0.5.13	4 / 17	2025-09-22
0.5.12	4 / 17	2025-09-22
0.5.11	4 / 17	2025-09-16
0.5.10	4 / 17	2025-09-09
0.5.9	4 / 17	2025-09-08
0.5.8	4 / 17	2025-08-30
0.5.7	4 / 17	2025-08-19
0.5.4	4 / 17	2025-08-02
0.4.1	1 / 16	2025-07-13
0.4.0	1 / 16	2025-07-12
0.3.0	0 / 16	2025-07-10
0.2.0	0 / 16	2025-07-07
0.1.2	0 / 2	2025-07-03
0.1.1	0 / 2	2025-07-03
0.1.0	0 / 2	2025-07-03

v0.8.37

1 finding

LOW No provenance attestation provenance

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

v0.8.33

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

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

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

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

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

1 finding

LOW No provenance attestation provenance

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

v0.8.22

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

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

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

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

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

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

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

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

v0.8.12

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

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

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

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

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

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

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

v0.7.9

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

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

1 finding

LOW No provenance attestation provenance

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

v0.5.13

1 finding

LOW No provenance attestation provenance

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

v0.5.12

1 finding

LOW No provenance attestation provenance

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

v0.5.11

1 finding

LOW No provenance attestation provenance

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

v0.5.10

1 finding

LOW No provenance attestation provenance

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

v0.5.9

1 finding

LOW No provenance attestation provenance

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

v0.5.8

1 finding

LOW No provenance attestation provenance

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

v0.5.7

1 finding

LOW No provenance attestation provenance

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

v0.5.4

1 finding

LOW No provenance attestation provenance

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

v0.4.1

1 finding

LOW No provenance attestation provenance

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

v0.4.0

1 finding

LOW No provenance attestation provenance

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

v0.3.0

1 finding

LOW No provenance attestation provenance

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

v0.2.0

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.

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