@ktjs/mui
Material-UI inspired components for kt.js - pre-styled UI components
Supply chain provenance
Status for the latest visible version.
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
Keywords
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| typosquat | typosquat.levenshtein:uuid | AI (typosquat): Scoped MUI component library; Levenshtein match to uuid is coincidental. | ai | |
| typosquat | typosquat.levenshtein:joi | AI (typosquat): Scoped MUI component library; Levenshtein match to joi is coincidental. | ai | |
| typosquat | typosquat.levenshtein:yup | AI (typosquat): Scoped MUI component library; Levenshtein match to yup is coincidental. | ai |
Versions (showing 51 of 93)
| Version | Deps | Published |
|---|---|---|
| 0.40.26 | 0 / 0 | |
| 0.40.24 | 0 / 0 | |
| 0.40.23 | 0 / 0 | |
| 0.40.22 | 0 / 0 | |
| 0.40.21 | 0 / 0 | |
| 0.40.20 | 0 / 0 | |
| 0.40.19 | 0 / 0 | |
| 0.40.18 | 0 / 0 | |
| 0.40.17 | 0 / 0 | |
| 0.40.16 | 0 / 0 | |
| 0.40.15 | 0 / 0 | |
| 0.40.14 | 0 / 0 | |
| 0.40.11 | 0 / 0 | |
| 0.40.10 | 0 / 0 | |
| 0.40.9 | 0 / 0 | |
| 0.40.7 | 0 / 0 | |
| 0.40.6 | 0 / 0 | |
| 0.40.5 | 0 / 0 | |
| 0.40.4 | 0 / 0 | |
| 0.40.3 | 0 / 0 | |
| 0.40.2 | 0 / 0 | |
| 0.40.1 | 3 / 0 | |
| 0.40.0 | 3 / 0 | |
| 0.39.1 | 3 / 0 | |
| 0.39.0 | 3 / 0 | |
| 0.38.13 | 3 / 0 | |
| 0.38.12 | 3 / 0 | |
| 0.38.11 | 3 / 0 | |
| 0.38.8 | 3 / 0 | |
| 0.38.7 | 3 / 0 | |
| 0.38.6 | 3 / 0 | |
| 0.38.5 | 3 / 0 | |
| 0.38.3 | 3 / 0 | |
| 0.38.2 | 3 / 0 | |
| 0.38.1 | 3 / 0 | |
| 0.38.0 | 3 / 0 | |
| 0.37.9 | 3 / 0 | |
| 0.37.8 | 3 / 0 | |
| 0.37.7 | 3 / 0 | |
| 0.37.6 | 3 / 0 | |
| 0.37.5 | 3 / 0 | |
| 0.37.4 | 3 / 0 | |
| 0.37.3 | 3 / 0 | |
| 0.37.2 | 3 / 0 | |
| 0.37.1 | 3 / 0 | |
| 0.37.0 | 3 / 0 | |
| 0.36.2 | 3 / 0 | |
| 0.36.1 | 3 / 0 | |
| 0.36.0 | 3 / 0 | |
| 0.35.0 | 3 / 0 | |
| 0.34.3 | 3 / 0 |
v0.40.26
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.40.24
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.40.23
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.40.22
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.40.21
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.40.20
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.40.19
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.40.18
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.40.17
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.40.16
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.40.15
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.40.14
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.40.11
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.40.10
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.40.9
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.40.7
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.40.6
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.40.5
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.40.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.40.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.40.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.40.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.40.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.39.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.39.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.38.13
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.38.12
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.38.11
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.38.8
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.38.7
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.38.6
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.38.5
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.38.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.38.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.38.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.38.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.37.9
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.37.8
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.37.7
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.37.6
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.37.5
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.37.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.37.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.37.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.37.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.37.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.36.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.36.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.36.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.35.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.34.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.