@kong-ui-public/forms
- `vue` **must** be initialized in the host application - `@kong/kongponents` **must** be available as a `dependency` in the host application and registered globally, along with the Kongponents style import. [See here for instructions on installing Kongpo
Supply chain provenance
Status for the latest visible version.
Maintainers
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| typosquat | typosquat.levenshtein:cors | AI (typosquat): Scoped Kong UI package; Levenshtein match to 'cors' is a false positive with no impersonation intent. | ai | |
| phantom-deps | phantom-dep:fecha | AI (phantom-deps): fecha is a declared runtime dependency used in build/config; phantom-dep heuristic misfires here. | ai | |
| phantom-deps | phantom-dep:dompurify | AI (phantom-deps): dompurify is a declared runtime dependency; phantom-dep heuristic misfires here. | ai | |
| phantom-deps | phantom-dep:lodash-es | AI (phantom-deps): lodash-es is a declared runtime dependency; phantom-dep heuristic misfires here. | ai |
Versions (showing 100 of 320)
| Version | Deps | Published |
|---|---|---|
| 4.12.7 | 3 / 6 | |
| 4.12.6 | 3 / 6 | |
| 4.12.5 | 3 / 6 | |
| 4.12.4 | 3 / 6 | |
| 4.12.3 | 3 / 6 | |
| 4.12.2 | 3 / 6 | |
| 4.12.1 | 3 / 6 | |
| 4.12.0 | 3 / 6 | |
| 4.11.17 | 3 / 6 | |
| 4.11.16 | 3 / 6 | |
| 4.11.15 | 3 / 6 | |
| 4.11.14 | 3 / 6 | |
| 4.11.13 | 3 / 6 | |
| 4.11.12 | 3 / 6 | |
| 4.11.11 | 3 / 6 | |
| 4.11.10 | 3 / 6 | |
| 4.11.9 | 3 / 6 | |
| 4.11.8 | 3 / 6 | |
| 4.11.7 | 3 / 6 | |
| 4.11.6 | 3 / 6 | |
| 4.11.5 | 3 / 6 | |
| 4.11.4 | 3 / 6 | |
| 4.11.3 | 3 / 6 | |
| 4.11.2 | 3 / 6 | |
| 4.11.1 | 3 / 6 | |
| 4.11.0 | 3 / 6 | |
| 4.10.11 | 3 / 5 | |
| 4.10.10 | 3 / 5 | |
| 4.10.9 | 3 / 5 | |
| 4.10.8 | 3 / 5 | |
| 4.10.7 | 3 / 5 | |
| 4.10.6 | 3 / 5 | |
| 4.10.5 | 3 / 5 | |
| 4.10.4 | 3 / 5 | |
| 4.10.3 | 3 / 5 | |
| 4.10.2 | 3 / 5 | |
| 4.10.1 | 3 / 5 | |
| 4.10.0 | 3 / 5 | |
| 4.9.0 | 3 / 5 | |
| 4.8.3 | 4 / 5 | |
| 4.8.2 | 3 / 5 | |
| 4.8.1 | 3 / 5 | |
| 4.8.0 | 3 / 5 | |
| 4.7.36 | 3 / 5 | |
| 4.7.35 | 3 / 5 | |
| 4.7.34 | 3 / 5 | |
| 4.7.33 | 3 / 5 | |
| 4.7.32 | 3 / 5 | |
| 4.7.31 | 3 / 5 | |
| 4.7.30 | 3 / 5 | |
| 4.7.29 | 3 / 5 | |
| 4.7.28 | 3 / 5 | |
| 4.7.27 | 3 / 5 | |
| 4.7.26 | 3 / 5 | |
| 4.7.25 | 3 / 5 | |
| 4.7.24 | 3 / 5 | |
| 4.7.23 | 3 / 5 | |
| 4.7.22 | 3 / 5 | |
| 4.7.21 | 3 / 5 | |
| 4.7.20 | 3 / 5 | |
| 4.7.19 | 3 / 5 | |
| 4.7.18 | 3 / 5 | |
| 4.7.17 | 3 / 5 | |
| 4.7.16 | 3 / 5 | |
| 4.7.15 | 3 / 5 | |
| 4.7.14 | 3 / 5 | |
| 4.7.13 | 3 / 5 | |
| 4.7.12 | 3 / 5 | |
| 4.7.11 | 3 / 5 | |
| 4.7.10 | 3 / 5 | |
| 4.7.9 | 3 / 5 | |
| 4.7.8 | 3 / 5 | |
| 4.7.7 | 3 / 5 | |
| 4.7.6 | 3 / 5 | |
| 4.7.5 | 3 / 5 | |
| 4.7.4 | 3 / 5 | |
| 4.7.3 | 3 / 5 | |
| 4.7.2 | 3 / 5 | |
| 4.7.1 | 3 / 5 | |
| 4.7.0 | 3 / 5 | |
| 4.6.1 | 3 / 5 | |
| 4.6.0 | 3 / 5 | |
| 4.5.11 | 3 / 5 | |
| 4.5.10 | 3 / 5 | |
| 4.5.9 | 3 / 5 | |
| 4.5.8 | 3 / 5 | |
| 4.5.7 | 3 / 5 | |
| 4.5.6 | 3 / 5 | |
| 4.5.5 | 3 / 5 | |
| 4.5.4 | 3 / 5 | |
| 4.5.3 | 3 / 5 | |
| 4.5.2 | 3 / 5 | |
| 4.5.1 | 3 / 5 | |
| 4.5.0 | 3 / 5 | |
| 4.4.0 | 3 / 5 | |
| 4.3.4 | 3 / 5 | |
| 4.3.3 | 3 / 5 | |
| 4.3.2 | 3 / 5 | |
| 4.3.1 | 3 / 5 | |
| 4.3.0 | 3 / 5 |
v4.12.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.12.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.12.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.11.17
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.11.16
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.11.15
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.11.14
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.11.13
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.11.12
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.11.11
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.11.10
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.11.9
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.11.8
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.11.7
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.11.6
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.11.5
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.11.4
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.11.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.11.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.11.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.11.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.10.11
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.10.10
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.10.9
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.10.8
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.10.7
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.10.6
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.10.5
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.10.4
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.10.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.10.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.10.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.10.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.9.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.8.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.8.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.8.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.7.36
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.7.35
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.7.34
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.7.33
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.7.32
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.7.31
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.7.30
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.7.29
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.7.28
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.7.27
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.7.26
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.7.25
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.7.24
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.7.23
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.7.22
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.7.21
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.7.20
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.7.19
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.7.18
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.7.17
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.7.16
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.7.15
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.7.14
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.7.13
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.7.12
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.7.11
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.7.10
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.7.9
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.7.8
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.7.7
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.7.6
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.7.5
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.7.4
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.7.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.7.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.7.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.7.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.6.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.6.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.5.11
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.5.10
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.5.9
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.5.8
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.5.7
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.5.6
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.5.5
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.5.4
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.5.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.5.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.5.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.5.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.4.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.3.4
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.3.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.3.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.3.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.3.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.