@kong-ui-public/entities-shared
Shared components for Kong entities.
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 |
|---|---|---|---|---|
| source-diff | obfuscated-file:dist/_plugin-vue_export-helper-DcXbY5JL.cjs | AI (source-diff): Standard Vite/Vue minified CJS build artifact; content is readable Kong entity code, not obfuscated malware. | ai | |
| publish-pattern | rapid-publish | AI (publish-pattern): 2040 versions published via automated CI; rapid successive publishes are normal for this package. | ai | |
| source-diff | obfuscated-file:dist/_plugin-vue_export-helper-CPHEKtsJ.cjs | AI (source-diff): Standard Vite/Vue minified build artifact; content is recognizable Kong UI component code, not obfuscation. | ai | |
| source-diff | obfuscated-file:dist/_plugin-vue_export-helper-CwM56vX0.cjs | AI (source-diff): Standard Vite/Vue minified build artifact; content is clearly Kong UI component logic, not malicious code. | ai | |
| source-diff | obfuscated-file:dist/_plugin-vue_export-helper-BxQ7nON4.cjs | AI (source-diff): Standard Vite/Vue minified CJS build output; content is readable Kong entity code, not malicious obfuscation. | ai | |
| source-diff | obfuscated-file:dist/_plugin-vue_export-helper-B5cQfgfE.cjs | AI (source-diff): Standard Vite/Vue minified CJS build artifact; content is clearly legitimate Kong UI component code. | ai | |
| source-diff | obfuscated-file:dist/_plugin-vue_export-helper-B2WhlBkH.cjs | AI (source-diff): Standard Vite/Rollup minified build artifact; not obfuscated malware. | ai | |
| source-diff | obfuscated-file:dist/_plugin-vue_export-helper-B3S5Tx0x.cjs | AI (source-diff): Standard Vite/Rollup minified build output for a Vue UI component library; not obfuscation. | ai | |
| source-diff | obfuscated-file:dist/_plugin-vue_export-helper-BVLVXTg1.cjs | AI (source-diff): Standard Vite/Rollup minified CJS bundle output; content is normal Vue component code, not obfuscation. | ai | |
| phantom-deps | phantom-dep:@kong-ui-public/core | AI (phantom-deps): Same-org monorepo package; bundled into dist rather than directly imported at source level. | ai | |
| phantom-deps | phantom-dep:compare-versions | AI (phantom-deps): Monorepo build artifact; dependency is used transitively in bundled output. | ai |
Versions (showing 100 of 304)
| Version | Deps | Published |
|---|---|---|
| 3.10.10 | 2 / 7 | |
| 3.10.9 | 2 / 7 | |
| 3.10.8 | 2 / 7 | |
| 3.10.7 | 2 / 7 | |
| 3.10.6 | 2 / 7 | |
| 3.10.5 | 2 / 7 | |
| 3.10.4 | 2 / 7 | |
| 3.10.3 | 2 / 7 | |
| 3.10.2 | 2 / 7 | |
| 3.10.1 | 2 / 7 | |
| 3.10.0 | 2 / 7 | |
| 3.9.26 | 2 / 7 | |
| 3.9.25 | 2 / 7 | |
| 3.9.24 | 2 / 7 | |
| 3.9.23 | 2 / 7 | |
| 3.9.22 | 2 / 7 | |
| 3.9.21 | 2 / 7 | |
| 3.9.20 | 2 / 7 | |
| 3.9.19 | 2 / 7 | |
| 3.9.18 | 2 / 7 | |
| 3.9.17 | 2 / 7 | |
| 3.9.16 | 2 / 7 | |
| 3.9.15 | 2 / 7 | |
| 3.9.14 | 2 / 7 | |
| 3.9.13 | 2 / 7 | |
| 3.9.12 | 2 / 7 | |
| 3.9.11 | 2 / 7 | |
| 3.9.10 | 2 / 7 | |
| 3.9.9 | 2 / 7 | |
| 3.9.8 | 2 / 7 | |
| 3.9.7 | 2 / 7 | |
| 3.9.6 | 2 / 7 | |
| 3.9.5 | 2 / 7 | |
| 3.9.4 | 2 / 7 | |
| 3.9.3 | 2 / 7 | |
| 3.9.2 | 2 / 7 | |
| 3.9.1 | 2 / 7 | |
| 3.9.0 | 2 / 7 | |
| 3.8.11 | 2 / 7 | |
| 3.8.10 | 2 / 7 | |
| 3.8.9 | 2 / 7 | |
| 3.8.8 | 2 / 7 | |
| 3.8.7 | 2 / 7 | |
| 3.8.6 | 2 / 7 | |
| 3.8.5 | 2 / 7 | |
| 3.8.4 | 2 / 7 | |
| 3.8.3 | 2 / 7 | |
| 3.8.2 | 2 / 7 | |
| 3.8.1 | 2 / 7 | |
| 3.8.0 | 2 / 7 | |
| 3.7.8 | 3 / 6 | |
| 3.7.7 | 3 / 6 | |
| 3.7.6 | 3 / 6 | |
| 3.7.5 | 3 / 6 | |
| 3.7.4 | 3 / 6 | |
| 3.7.3 | 3 / 6 | |
| 3.7.2 | 3 / 6 | |
| 3.7.1 | 3 / 6 | |
| 3.7.0 | 3 / 6 | |
| 3.6.4 | 3 / 6 | |
| 3.6.3 | 3 / 6 | |
| 3.6.2 | 3 / 6 | |
| 3.6.1 | 3 / 6 | |
| 3.6.0 | 3 / 6 | |
| 3.5.4 | 3 / 6 | |
| 3.5.3 | 3 / 6 | |
| 3.5.2 | 3 / 6 | |
| 3.5.1 | 3 / 6 | |
| 3.5.0 | 3 / 6 | |
| 3.4.7 | 3 / 6 | |
| 3.4.6 | 3 / 6 | |
| 3.4.5 | 3 / 6 | |
| 3.4.4 | 3 / 6 | |
| 3.4.3 | 3 / 6 | |
| 3.4.2 | 3 / 6 | |
| 3.4.1 | 3 / 6 | |
| 3.4.0 | 3 / 6 | |
| 3.3.11 | 3 / 6 | |
| 3.3.10 | 3 / 6 | |
| 3.3.9 | 3 / 6 | |
| 3.3.8 | 3 / 6 | |
| 3.3.7 | 3 / 6 | |
| 3.3.6 | 3 / 6 | |
| 3.3.5 | 3 / 6 | |
| 3.3.4 | 3 / 6 | |
| 3.3.3 | 3 / 6 | |
| 3.3.2 | 3 / 6 | |
| 3.3.1 | 3 / 6 | |
| 3.3.0 | 3 / 6 | |
| 3.2.11 | 3 / 6 | |
| 3.2.10 | 3 / 6 | |
| 3.2.9 | 3 / 6 | |
| 3.2.8 | 3 / 6 | |
| 3.2.7 | 3 / 6 | |
| 3.2.6 | 3 / 6 | |
| 3.2.5 | 3 / 6 | |
| 3.2.4 | 3 / 6 | |
| 3.2.3 | 3 / 6 | |
| 3.2.2 | 3 / 6 | |
| 3.2.1 | 3 / 6 |
v3.10.10
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.10.9
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.10.8
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.10.7
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.10.6
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.10.5
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.10.4
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.10.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.10.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.10.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.10.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.9.26
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.9.25
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.9.24
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.9.23
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.9.22
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.9.21
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.9.20
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.9.19
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.9.18
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.9.17
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.9.16
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.9.15
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.9.14
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.9.13
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.9.12
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.9.11
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.9.10
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.9.9
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.9.8
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.9.7
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.9.6
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.9.5
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.9.4
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.9.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.9.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.9.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.9.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.8.11
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.8.10
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.8.9
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.8.8
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.8.7
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.8.6
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.8.5
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.8.4
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.8.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.8.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.8.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.8.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.7.8
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.7.7
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.7.6
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.7.5
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.7.4
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.7.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.7.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.7.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.7.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.6.4
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.6.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.6.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.6.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.6.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.5.4
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.5.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.5.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.5.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.5.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.4.7
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.4.6
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.4.5
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.4.4
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.4.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.4.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.4.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.4.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.3.11
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.3.10
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.3.9
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.3.8
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.3.7
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.3.6
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.3.5
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.3.4
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.3.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.3.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.3.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.3.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.2.11
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.2.10
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.2.9
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.2.8
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.2.7
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.2.6
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.2.5
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.2.4
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.2.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.2.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.2.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.