@altron-test/ui MIT 17 versions

@altron-test/ui

npm Repository Homepage

A starter for creating a React component library with React Compiler.

17

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

Maintainers

keshavsense

Accepted risks

Findings the reviewer chose to accept rather than block on.

Source	Rule	Reason	Accepted by	When
phantom-deps	phantom-dep:tailwindcss	AI (phantom-deps): Tailwind is a CSS framework referenced in config files; not directly imported in JS/TS source is expected.	ai	2026/05/15
phantom-deps	phantom-dep:tailwind-merge	AI (phantom-deps): Config-only reference; stable false positive for this UI library.	ai	2026/05/15
phantom-deps	phantom-dep:@tailwindcss/vite	AI (phantom-deps): Vite plugin referenced in build config, not imported in source; expected pattern.	ai	2026/05/15
phantom-deps	phantom-dep:@storybook/react-vite	AI (phantom-deps): Storybook framework referenced in config, not directly imported in source; expected pattern.	ai	2026/05/15
typosquat	typosquat.levenshtein:uuid	AI (typosquat): Scoped UI library; no plausible impersonation of uuid.	ai	2026/05/15
typosquat	typosquat.levenshtein:yup	AI (typosquat): Scoped UI library; no plausible impersonation of yup.	ai	2026/05/15
typosquat	typosquat.levenshtein:pg	AI (typosquat): Scoped UI library; no plausible impersonation of pg.	ai	2026/05/15
typosquat	typosquat.levenshtein:qs	AI (typosquat): Scoped UI library; no plausible impersonation of qs.	ai	2026/05/15
typosquat	typosquat.levenshtein:joi	AI (typosquat): Scoped UI library; no plausible impersonation of joi.	ai	2026/05/15

Versions (showing 17 of 17)

Version	Deps	Published
0.0.18	0 / 22	2026-05-21
0.0.17	0 / 22	2026-05-20
0.0.16	0 / 22	2026-05-20
0.0.15	0 / 22	2026-05-15
0.0.14	0 / 22	2026-05-15
0.0.13	0 / 22	2026-05-13
0.0.12	0 / 22	2026-04-29
0.0.11	0 / 22	2026-04-15
0.0.10	0 / 22	2026-04-14
0.0.9	0 / 22	2026-04-10
0.0.8	0 / 22	2026-04-09
0.0.7	8 / 18	2026-04-09
0.0.6	8 / 18	2026-04-09
0.0.5	8 / 18	2026-04-09
0.0.4	8 / 18	2026-04-09
0.0.3	8 / 18	2026-04-08
0.0.2	8 / 18	2026-04-08

v0.0.18

1 finding

LOW No provenance attestation provenance

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

v0.0.17

1 finding

LOW No provenance attestation provenance

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

v0.0.16

1 finding

LOW No provenance attestation provenance

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

v0.0.15

1 finding

LOW No provenance attestation provenance

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

v0.0.14

1 finding

LOW No provenance attestation provenance

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

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

v0.0.6

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

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

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