@qqt-product/ui
This template should help get you started developing with Vue 3 and TypeScript in Vite. The template uses Vue 3 `<script setup>` SFCs, check out the [script setup docs](https://v3.vuejs.org/api/sfc-script-setup.html#sfc-script-setup) to learn more.
Supply chain provenance
Status for the latest visible version.
Without SLSA provenance there is no cryptographic link between this tarball and the public source, so a manually published version cannot be tied back to a reviewed commit.
Maintainers
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| source-diff | encoded-string-file:dist/index.es.js | AI (source-diff): Long strings are Unicode BiDi lookup tables from CodeMirror/text-rendering code; stable false positive for this UI bundle. | ai | |
| source-diff | encoded-string-file:dist/index.umd.js | AI (source-diff): Long strings are Sortable.js 1.15.0 minified bundle; legitimate third-party library code, not obfuscation. | ai | |
| typosquat | typosquat.levenshtein:qs | AI (typosquat): Scoped UI library; string distance match to 'qs' is a false positive. | ai | |
| typosquat | typosquat.levenshtein:uuid | AI (typosquat): Scoped UI library; string distance match to 'uuid' is a false positive. | ai | |
| typosquat | typosquat.levenshtein:yup | AI (typosquat): Scoped UI library; string distance match to 'yup' is a false positive. | ai | |
| typosquat | typosquat.levenshtein:joi | AI (typosquat): Scoped UI library; string distance match to 'joi' is a false positive. | ai | |
| typosquat | typosquat.levenshtein:pg | AI (typosquat): Scoped UI library; string distance match to 'pg' is a false positive. | ai |
Versions (showing 34 of 34)
| Version | Deps | Published |
|---|---|---|
| 20.0.1 | 0 / 51 | |
| 20.0.0 | 0 / 51 | |
| 17.0.0 | 0 / 51 | |
| 16.0.9 | 0 / 51 | |
| 16.0.8 | 0 / 51 | |
| 16.0.7 | 0 / 51 | |
| 16.0.6 | 0 / 51 | |
| 16.0.5 | 0 / 51 | |
| 16.0.4 | 0 / 51 | |
| 16.0.3 | 0 / 51 | |
| 16.0.2 | 0 / 51 | |
| 16.0.1 | 0 / 51 | |
| 16.0.0 | 0 / 51 | |
| 14.1.5 | 0 / 51 | |
| 14.1.4 | 0 / 51 | |
| 14.1.3 | 0 / 51 | |
| 14.1.2 | 0 / 51 | |
| 14.1.1 | 0 / 51 | |
| 14.0.9 | 0 / 51 | |
| 14.0.8 | 0 / 51 | |
| 14.0.7 | 0 / 51 | |
| 14.0.6 | 0 / 51 | |
| 12.0.10 | 0 / 51 | |
| 12.0.9 | 0 / 51 | |
| 12.0.8 | 0 / 51 | |
| 12.0.7 | 0 / 51 | |
| 12.0.6 | 0 / 51 | |
| 11.1.0 | 0 / 51 | |
| 11.0.15 | 0 / 51 | |
| 11.0.14 | 0 / 51 | |
| 11.0.13 | 0 / 51 | |
| 11.0.12 | 0 / 51 | |
| 11.0.11 | 0 / 51 | |
| 11.0.10 | 0 / 51 |
v16.0.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v16.0.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v16.0.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v16.0.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v16.0.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v14.1.5
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v14.1.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v14.1.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v14.1.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v14.1.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v14.0.9
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v14.0.8
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v14.0.7
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v14.0.6
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v12.0.7
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v12.0.6
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v11.1.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v11.0.15
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v11.0.12
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v11.0.11
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v11.0.10
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.