@ditojs/ui
Dito.js UI is a simple UI library, built with Vue.js for use in Dito.js Admin and elsewhere
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 |
|---|---|---|---|---|
| typosquat | typosquat.levenshtein:uuid | AI (typosquat): Scoped @ditojs package; Levenshtein match to uuid is coincidental. | ai | |
| typosquat | typosquat.levenshtein:pg | AI (typosquat): Scoped @ditojs package; Levenshtein match to pg is coincidental. | ai | |
| typosquat | typosquat.levenshtein:qs | AI (typosquat): Scoped @ditojs package; Levenshtein match to qs is coincidental. | ai | |
| typosquat | typosquat.levenshtein:joi | AI (typosquat): Scoped @ditojs package; Levenshtein match to joi is coincidental. | ai | |
| typosquat | typosquat.levenshtein:yup | AI (typosquat): Scoped @ditojs package; Levenshtein match to yup is coincidental. | ai | |
| phantom-deps | phantom-dep:@soda/get-current-script | AI (phantom-deps): Declared dep used in config/build context; phantom-dep heuristic fires on indirect usage patterns. | ai |
Versions (showing 55 of 55)
| Version | Deps | Published |
|---|---|---|
| 2.99.0 | 2 / 2 | |
| 2.98.0 | 2 / 2 | |
| 2.97.0 | 2 / 2 | |
| 2.94.0 | 2 / 2 | |
| 2.93.0 | 2 / 2 | |
| 2.92.0 | 2 / 2 | |
| 2.91.0 | 2 / 2 | |
| 2.90.0 | 2 / 2 | |
| 2.89.0 | 2 / 2 | |
| 2.88.0 | 2 / 2 | |
| 2.87.0 | 2 / 2 | |
| 2.86.0 | 2 / 2 | |
| 2.85.0 | 2 / 2 | |
| 2.84.0 | 2 / 2 | |
| 2.83.0 | 2 / 2 | |
| 2.82.0 | 2 / 2 | |
| 2.81.0 | 2 / 2 | |
| 2.80.0 | 2 / 2 | |
| 2.79.0 | 2 / 2 | |
| 2.78.0 | 2 / 2 | |
| 2.77.0 | 2 / 2 | |
| 2.75.0 | 2 / 2 | |
| 2.74.0 | 2 / 2 | |
| 2.73.2 | 2 / 2 | |
| 2.73.1 | 2 / 2 | |
| 2.73.0 | 2 / 2 | |
| 2.72.0 | 2 / 2 | |
| 2.71.0 | 2 / 2 | |
| 2.70.0 | 2 / 2 | |
| 2.69.0 | 2 / 2 | |
| 2.68.0 | 2 / 2 | |
| 2.67.0 | 2 / 2 | |
| 2.66.0 | 2 / 2 | |
| 2.65.0 | 2 / 2 | |
| 2.64.0 | 2 / 2 | |
| 2.63.0 | 2 / 2 | |
| 2.62.0 | 2 / 2 | |
| 2.61.0 | 2 / 2 | |
| 2.60.0 | 2 / 2 | |
| 2.59.0 | 2 / 2 | |
| 2.58.0 | 2 / 2 | |
| 2.57.0 | 2 / 2 | |
| 2.56.0 | 2 / 2 | |
| 2.55.0 | 2 / 2 | |
| 2.54.0 | 2 / 2 | |
| 2.53.0 | 2 / 2 | |
| 2.52.0 | 2 / 2 | |
| 2.51.2 | 2 / 2 | |
| 2.51.0 | 2 / 2 | |
| 2.50.0 | 2 / 2 | |
| 2.49.1 | 2 / 2 | |
| 2.49.0 | 2 / 2 | |
| 2.48.0 | 2 / 2 | |
| 2.47.0 | 2 / 2 | |
| 2.46.1 | 2 / 2 |
v2.99.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.98.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.94.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.93.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.92.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.91.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.90.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.89.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.88.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.87.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.86.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.85.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.84.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.83.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.82.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.81.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.80.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.79.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.78.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.77.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.75.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.74.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.73.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.73.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.73.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.72.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.71.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.70.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.69.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.68.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.67.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.66.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.65.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.64.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.63.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.62.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.61.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.60.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.59.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.58.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.57.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.56.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.55.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.54.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.53.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.52.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.51.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.51.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.50.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.49.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.49.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.48.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.47.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.46.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.