@0xsequence/design-system Apache-2.0 20 versions

@0xsequence/design-system

npm Homepage

[![npm version](https://badge.fury.io/js/@0xsequence%2Fdesign-system.svg)](https://badge.fury.io/js/@0xsequence%2Fdesign-system)

20

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

naivesheeppkieltykaagusx1211taylanpincemilkytastecorban

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 core dependency for CSS generation in design systems; config-file usage is expected.	ai	2026/05/18
phantom-deps	phantom-dep:tw-animate-css	AI (phantom-deps): Animation utility library; used via Tailwind config, not direct imports.	ai	2026/05/18
phantom-deps	phantom-dep:@radix-ui/react-aspect-ratio	AI (phantom-deps): Radix component re-exported from main entry; phantom-dep heuristic misses re-export patterns.	ai	2026/05/18

Versions (showing 20 of 20)

Version	Deps	Published
3.2.9	22 / 40	2026-03-05
3.2.8	22 / 40	2026-02-26
3.2.7	22 / 40	2026-02-20
3.2.6	22 / 40	2026-02-19
3.2.5	22 / 40	2026-02-17
3.2.4	22 / 40	2026-02-10
3.2.3	22 / 40	2026-02-09
3.2.2	22 / 40	2026-01-28
3.2.1	22 / 40	2026-01-19
3.2.0	22 / 40	2026-01-16
3.1.7	22 / 40	2025-12-03
3.1.6	22 / 40	2025-12-03
3.1.5	22 / 41	2025-11-26
3.1.4	22 / 41	2025-11-25
3.1.3	22 / 41	2025-11-21
3.1.2	22 / 41	2025-11-20
3.1.1	22 / 41	2025-11-19
3.1.0	22 / 42	2025-11-07
3.0.1	23 / 41	2025-10-23
3.0.0	23 / 41	2025-10-22

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

v3.2.8

1 finding

LOW No provenance attestation provenance

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

v3.2.7

1 finding

LOW No provenance attestation provenance

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

v3.2.6

1 finding

LOW No provenance attestation provenance

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

v3.2.5

1 finding

LOW No provenance attestation provenance

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

v3.2.4

1 finding

LOW No provenance attestation provenance

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

v3.2.3

1 finding

LOW No provenance attestation provenance

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

v3.2.2

1 finding

LOW No provenance attestation provenance

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

v3.2.1

1 finding

LOW No provenance attestation provenance

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

v3.2.0

1 finding

LOW No provenance attestation provenance

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

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

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

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

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

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

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

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

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

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

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