@kong-ui-public/entities-plugins
Plugin entity components.
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/filler/field-walker-CituFcZB.js | AI (source-diff): Vite build artifact with readable content; filler utilities for Cypress/Playwright test helpers, not malicious obfuscation. | ai | |
| source-diff | obfuscated-file:dist/filler/field-walker-DMJsTz2L.js | AI (source-diff): File is standard Vite-bundled output with readable code; minification is expected for this build pipeline. | ai | |
| publish-pattern | rapid-publish | AI (publish-pattern): High-frequency automated CI releases from Kong monorepo; rapid publishes are normal for this package. | ai | |
| source-diff | obfuscated-file:dist/filler/field-walker-GKhLVBvo.js | AI (source-diff): Vite-minified filler/test-helper bundle; content is readable selector utilities, not obfuscated malware. | ai | |
| source-diff | net-exec-file:dist/Reflect-DRBLqlES.js | AI (source-diff): File is the reflect-metadata polyfill (Apache-2.0, Microsoft); no actual network calls or malicious code execution. | ai | |
| phantom-deps | phantom-dep:focus-trap | AI (phantom-deps): Declared in dependencies; used in build/config; stable false positive. | ai | |
| phantom-deps | phantom-dep:nanoid | AI (phantom-deps): Declared in dependencies; used in build/config; stable false positive. | ai | |
| phantom-deps | phantom-dep:lodash-es | AI (phantom-deps): Declared in dependencies; used in build/config; stable false positive. | ai | |
| source-diff | obfuscated-file:dist/filler/field-walker-CwfGUJrB.js | AI (source-diff): Vite-bundled output with content-hash filename; readable source, no malicious patterns. Normal for this package's build pipeline. | ai | |
| dependencies | unvetted-peer-dep:@kong-ui-public/i18n | AI (dependencies): Internal Kong UI peer dependency; stable pattern across versions. | ai | |
| dependencies | unvetted-dep:@kong-ui-public/entities-plugins-metadata | AI (dependencies): Same Kong org namespace; consistent pattern across all versions of this package. | ai |
Versions (showing 100 of 600)
| Version | Deps | Published |
|---|---|---|
| 9.50.0 | 11 / 15 | |
| 9.49.0 | 11 / 15 | |
| 9.48.0 | 11 / 15 | |
| 9.47.1 | 11 / 15 | |
| 9.47.0 | 11 / 15 | |
| 9.46.0 | 11 / 15 | |
| 9.45.1 | 11 / 15 | |
| 9.45.0 | 11 / 15 | |
| 9.44.2 | 11 / 15 | |
| 9.44.1 | 11 / 15 | |
| 9.44.0 | 11 / 15 | |
| 9.43.1 | 11 / 15 | |
| 9.43.0 | 11 / 15 | |
| 9.42.1 | 11 / 15 | |
| 9.42.0 | 11 / 15 | |
| 9.41.0 | 11 / 15 | |
| 9.40.0 | 11 / 15 | |
| 9.39.1 | 11 / 15 | |
| 9.39.0 | 11 / 15 | |
| 9.38.1 | 11 / 15 | |
| 9.38.0 | 11 / 15 | |
| 9.37.0 | 11 / 15 | |
| 9.36.0 | 11 / 12 | |
| 9.35.2 | 11 / 12 | |
| 9.35.1 | 11 / 12 | |
| 9.35.0 | 11 / 12 | |
| 9.34.0 | 11 / 12 | |
| 9.33.0 | 11 / 12 | |
| 9.32.1 | 10 / 12 | |
| 9.32.0 | 10 / 12 | |
| 9.31.0 | 10 / 12 | |
| 9.30.1 | 10 / 12 | |
| 9.30.0 | 10 / 12 | |
| 9.29.4 | 10 / 12 | |
| 9.29.3 | 10 / 12 | |
| 9.29.2 | 10 / 12 | |
| 9.29.1 | 10 / 12 | |
| 9.29.0 | 10 / 12 | |
| 9.28.6 | 9 / 10 | |
| 9.28.5 | 9 / 10 | |
| 9.28.4 | 9 / 10 | |
| 9.28.3 | 9 / 10 | |
| 9.28.2 | 9 / 10 | |
| 9.28.1 | 9 / 10 | |
| 9.28.0 | 9 / 10 | |
| 9.27.1 | 9 / 8 | |
| 9.27.0 | 9 / 8 | |
| 9.26.0 | 9 / 8 | |
| 9.25.15 | 9 / 8 | |
| 9.25.14 | 9 / 8 | |
| 9.25.13 | 9 / 8 | |
| 9.25.12 | 9 / 8 | |
| 9.25.11 | 9 / 8 | |
| 9.25.10 | 9 / 8 | |
| 9.25.9 | 8 / 9 | |
| 9.25.8 | 8 / 9 | |
| 9.25.7 | 8 / 9 | |
| 9.25.6 | 8 / 9 | |
| 9.25.5 | 8 / 9 | |
| 9.25.4 | 8 / 9 | |
| 9.25.3 | 8 / 9 | |
| 9.25.2 | 8 / 9 | |
| 9.25.1 | 8 / 9 | |
| 9.25.0 | 8 / 9 | |
| 9.24.2 | 8 / 9 | |
| 9.24.1 | 8 / 9 | |
| 9.24.0 | 8 / 9 | |
| 9.23.1 | 8 / 9 | |
| 9.23.0 | 8 / 9 | |
| 9.22.2 | 7 / 9 | |
| 9.22.1 | 7 / 9 | |
| 9.22.0 | 7 / 9 | |
| 9.21.7 | 7 / 9 | |
| 9.21.6 | 7 / 9 | |
| 9.21.5 | 7 / 9 | |
| 9.21.4 | 7 / 9 | |
| 9.21.3 | 7 / 9 | |
| 9.21.2 | 7 / 9 | |
| 9.21.1 | 7 / 9 | |
| 9.21.0 | 7 / 9 | |
| 9.20.9 | 7 / 9 | |
| 9.20.8 | 7 / 9 | |
| 9.20.7 | 7 / 9 | |
| 9.20.6 | 7 / 9 | |
| 9.20.5 | 7 / 9 | |
| 9.20.4 | 7 / 9 | |
| 9.20.3 | 7 / 9 | |
| 9.20.2 | 7 / 9 | |
| 9.20.1 | 7 / 9 | |
| 9.20.0 | 7 / 9 | |
| 9.19.3 | 7 / 9 | |
| 9.19.2 | 7 / 9 | |
| 9.19.1 | 7 / 9 | |
| 9.19.0 | 7 / 9 | |
| 9.18.16 | 7 / 9 | |
| 9.18.15 | 7 / 9 | |
| 9.18.14 | 7 / 9 | |
| 9.18.13 | 7 / 9 | |
| 9.18.12 | 7 / 9 | |
| 9.18.11 | 7 / 9 |
v9.50.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v9.49.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v9.48.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v9.47.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v9.47.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v9.46.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v9.45.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v9.45.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v9.44.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v9.44.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v9.44.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v9.43.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v9.43.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v9.42.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v9.42.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v9.41.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v9.40.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v9.39.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v9.39.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v9.38.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v9.38.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v9.37.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v9.36.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v9.35.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v9.35.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v9.35.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v9.34.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v9.33.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v9.32.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v9.32.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v9.31.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v9.30.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v9.30.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v9.29.4
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v9.29.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v9.29.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v9.29.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v9.29.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v9.28.6
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v9.28.5
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v9.28.4
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v9.28.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v9.28.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v9.28.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v9.28.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v9.27.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v9.27.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v9.26.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v9.25.15
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v9.25.14
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v9.25.13
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v9.25.12
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v9.25.11
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v9.25.10
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v9.25.9
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v9.25.8
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v9.25.7
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v9.25.6
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v9.25.5
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v9.25.4
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v9.25.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v9.25.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v9.25.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v9.25.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v9.24.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v9.24.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v9.24.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v9.23.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v9.23.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v9.22.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v9.22.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v9.22.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v9.21.7
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v9.21.6
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v9.21.5
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v9.21.4
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v9.21.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v9.21.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v9.21.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v9.21.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v9.20.9
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v9.20.8
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v9.20.7
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v9.20.6
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v9.20.5
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v9.20.4
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v9.20.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v9.20.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v9.20.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v9.20.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v9.19.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v9.19.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v9.19.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v9.19.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v9.18.16
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v9.18.15
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v9.18.14
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v9.18.13
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v9.18.12
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v9.18.11
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.