@astral/ui
```@astral/ui``` - это UI-KIT, на основе которого строятся интерфейсы в Астрал-Софт.
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
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| publish-pattern | new-deps-added | AI (publish-pattern): focus-trap is a well-established accessibility library; addition is consistent with UI component development. | ai | |
| publish-pattern | rapid-publish | AI (publish-pattern): High-velocity component library with 1279 versions; rapid publishes are normal for this package. | ai | |
| phantom-deps | phantom-dep:dayjs | AI (phantom-deps): dayjs is a declared runtime dep; phantom-dep heuristic fires on indirect/config usage, stable false positive. | ai | |
| source-diff | large-new-source-files | AI (source-diff): Major version consolidation of multiple @astral/* packages into one; large file count increase is expected. | ai | |
| source-diff | source-size-tripled | AI (source-diff): v3→v4 consolidation of @astral/components, @astral/form, @astral/icons explains the 684x size increase. | ai | |
| dependencies | unvetted-dep:react-toastify-next | AI (dependencies): npm alias pattern pointing to real [email protected]; stable dual-version dependency pattern for this package. | ai | |
| dependencies | unvetted-dep:react-imask-next | AI (dependencies): npm alias pattern pointing to real [email protected]; stable dual-version dependency pattern for this package. | ai | |
| typosquat | typosquat.levenshtein:uuid | AI (typosquat): Scoped @astral/ui package; Levenshtein match to uuid is a false positive for this legitimate UI library. | ai | |
| typosquat | typosquat.levenshtein:yup | AI (typosquat): Scoped @astral/ui package; Levenshtein match to yup is a false positive. | ai | |
| typosquat | typosquat.levenshtein:joi | AI (typosquat): Scoped @astral/ui package; Levenshtein match to joi is a false positive. | ai | |
| typosquat | typosquat.levenshtein:qs | AI (typosquat): Scoped @astral/ui package; Levenshtein match to qs is a false positive. | ai | |
| typosquat | typosquat.levenshtein:pg | AI (typosquat): Scoped @astral/ui package; Levenshtein match to pg is a false positive. | ai |
Versions (showing 23 of 23)
| Version | Deps | Published |
|---|---|---|
| 4.68.0 | 21 / 0 | |
| 4.63.0 | 20 / 0 | |
| 4.61.3 | 20 / 0 | |
| 4.61.2 | 20 / 0 | |
| 4.60.0 | 20 / 0 | |
| 4.55.4 | 20 / 0 | |
| 4.55.1 | 20 / 0 | |
| 4.42.0 | 19 / 0 | |
| 3.364.0 | 3 / 0 | |
| 3.363.5 | 3 / 0 | |
| 3.363.4 | 3 / 0 | |
| 3.363.3 | 3 / 0 | |
| 3.363.2 | 3 / 0 | |
| 3.363.1 | 3 / 0 | |
| 3.363.0 | 3 / 0 | |
| 3.362.3 | 3 / 0 | |
| 3.362.2 | 3 / 0 | |
| 3.362.1 | 3 / 0 | |
| 3.362.0 | 3 / 0 | |
| 3.361.0 | 3 / 0 | |
| 3.360.1 | 3 / 0 | |
| 3.360.0 | 3 / 0 | |
| 3.359.2 | 3 / 0 |
v4.68.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.63.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.61.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.61.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.60.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.55.4
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.55.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.42.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.364.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.363.5
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.363.4
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.363.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.363.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.363.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.363.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.362.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.362.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.362.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.362.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.361.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.360.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.360.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.359.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.