← Home

@donotdev/ui

npm Repository Homepage

UI components for DoNotDev.

29
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

donotdev

Keywords

donotdevdndevreactuicompositionroutingformsreact-hook-formtypescriptvitenextjs

Accepted risks

Findings the reviewer chose to accept rather than block on.

SourceRuleReasonAccepted byWhen
typosquat typosquat.levenshtein:uuid AI (typosquat): Scoped UI library; Levenshtein match to 'uuid' is a false positive. ai
typosquat typosquat.levenshtein:pg AI (typosquat): Scoped UI library; Levenshtein match to 'pg' is a false positive. ai
typosquat typosquat.levenshtein:qs AI (typosquat): Scoped UI library; Levenshtein match to 'qs' is a false positive. ai
typosquat typosquat.levenshtein:joi AI (typosquat): Scoped UI library; Levenshtein match to 'joi' is a false positive. ai
typosquat typosquat.levenshtein:yup AI (typosquat): Scoped UI library; Levenshtein match to 'yup' is a false positive. ai
dependencies unvetted-dep:@fontsource/press-start-2p AI (dependencies): @fontsource/* packages are well-known font distribution packages; stable false positive for this UI library. ai
dependencies unvetted-dep:@fontsource/playfair-display AI (dependencies): @fontsource/* packages are well-known font distribution packages; stable false positive for this UI library. ai
phantom-deps phantom-dep:@fontsource/inter AI (phantom-deps): Font packages referenced in CSS/config rather than JS imports; expected pattern for a UI library. ai
phantom-deps phantom-dep:@fontsource/roboto AI (phantom-deps): Font packages referenced in CSS/config rather than JS imports; expected pattern for a UI library. ai
phantom-deps phantom-dep:@fontsource/space-grotesk AI (phantom-deps): Font packages referenced in CSS/config rather than JS imports; expected pattern for a UI library. ai
phantom-deps phantom-dep:@fontsource/press-start-2p AI (phantom-deps): Font packages referenced in CSS/config rather than JS imports; expected pattern for a UI library. ai
phantom-deps phantom-dep:@fontsource/playfair-display AI (phantom-deps): Font packages referenced in CSS/config rather than JS imports; expected pattern for a UI library. ai

Versions (showing 29 of 29)

Version Deps Published
0.1.43 5 / 0
0.1.42 5 / 0
0.1.1 8 / 0
0.1.0 8 / 0
0.0.31 8 / 0
0.0.30 8 / 0
0.0.29 8 / 0
0.0.28 8 / 0
0.0.22 8 / 0
0.0.21 8 / 0
0.0.20 8 / 0
0.0.19 8 / 0
0.0.18 8 / 0
0.0.17 7 / 0
0.0.16 7 / 0
0.0.15 7 / 0
0.0.14 7 / 0
0.0.13 3 / 0
0.0.12 3 / 0
0.0.11 3 / 0
0.0.10 3 / 0
0.0.9 3 / 0
0.0.8 3 / 0
0.0.7 3 / 0
0.0.6 4 / 0
0.0.5 4 / 0
0.0.4 4 / 0
0.0.3 4 / 0
0.0.2 4 / 0

v0.1.43

1 finding
LOW No provenance attestation provenance

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

v0.1.42

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

v0.1.0

1 finding
LOW No provenance attestation provenance

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

v0.0.31

1 finding
LOW No provenance attestation provenance

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

v0.0.30

1 finding
LOW No provenance attestation provenance

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

v0.0.29

1 finding
LOW No provenance attestation provenance

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

v0.0.28

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

1 finding
LOW No provenance attestation provenance

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

v0.0.21

1 finding
LOW No provenance attestation provenance

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

v0.0.20

1 finding
LOW No provenance attestation provenance

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

v0.0.19

1 finding
LOW No provenance attestation provenance

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

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.