@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.85.1 | 12 / 16 | |
| 9.85.0 | 11 / 17 | |
| 9.84.0 | 11 / 17 | |
| 9.83.4 | 11 / 17 | |
| 9.83.3 | 11 / 17 | |
| 9.83.2 | 11 / 17 | |
| 9.83.1 | 11 / 17 | |
| 9.83.0 | 11 / 17 | |
| 9.82.2 | 11 / 17 | |
| 9.82.1 | 11 / 17 | |
| 9.82.0 | 11 / 17 | |
| 9.81.1 | 11 / 17 | |
| 9.81.0 | 11 / 17 | |
| 9.80.0 | 11 / 17 | |
| 9.79.0 | 11 / 17 | |
| 9.78.0 | 12 / 16 | |
| 9.77.5 | 12 / 16 | |
| 9.77.4 | 12 / 16 | |
| 9.77.3 | 12 / 16 | |
| 9.77.2 | 12 / 16 | |
| 9.77.1 | 12 / 16 | |
| 9.77.0 | 12 / 16 | |
| 9.76.0 | 12 / 16 | |
| 9.75.0 | 12 / 16 | |
| 9.74.0 | 12 / 16 | |
| 9.73.0 | 12 / 16 | |
| 9.72.1 | 12 / 16 | |
| 9.72.0 | 12 / 16 | |
| 9.71.0 | 13 / 16 | |
| 9.70.2 | 13 / 16 | |
| 9.70.1 | 13 / 16 | |
| 9.70.0 | 13 / 16 | |
| 9.69.1 | 13 / 16 | |
| 9.69.0 | 13 / 16 | |
| 9.68.1 | 13 / 16 | |
| 9.68.0 | 13 / 16 | |
| 9.67.6 | 13 / 16 | |
| 9.67.5 | 13 / 16 | |
| 9.67.4 | 13 / 16 | |
| 9.67.3 | 13 / 16 | |
| 9.67.2 | 13 / 16 | |
| 9.67.1 | 13 / 16 | |
| 9.67.0 | 13 / 16 | |
| 9.66.0 | 13 / 16 | |
| 9.65.0 | 13 / 16 | |
| 9.64.0 | 13 / 16 | |
| 9.63.5 | 13 / 16 | |
| 9.63.4 | 13 / 16 | |
| 9.63.3 | 13 / 16 | |
| 9.63.2 | 13 / 16 | |
| 9.63.1 | 13 / 16 | |
| 9.63.0 | 13 / 16 | |
| 9.62.0 | 13 / 16 | |
| 9.61.1 | 13 / 16 | |
| 9.61.0 | 13 / 16 | |
| 9.60.2 | 13 / 16 | |
| 9.60.1 | 13 / 16 | |
| 9.60.0 | 13 / 16 | |
| 9.59.6 | 13 / 16 | |
| 9.59.5 | 13 / 16 | |
| 9.59.4 | 11 / 16 | |
| 9.59.3 | 11 / 16 | |
| 9.59.2 | 11 / 16 | |
| 9.59.1 | 11 / 16 | |
| 9.59.0 | 11 / 16 | |
| 9.58.1 | 11 / 16 | |
| 9.58.0 | 11 / 16 | |
| 9.57.0 | 11 / 16 | |
| 9.56.1 | 11 / 16 | |
| 9.56.0 | 11 / 16 | |
| 9.55.0 | 11 / 16 | |
| 9.54.1 | 11 / 16 | |
| 9.54.0 | 11 / 16 | |
| 9.53.0 | 11 / 16 | |
| 9.52.0 | 11 / 15 | |
| 9.51.0 | 11 / 15 | |
| 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 |
v9.85.1
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v9.85.0
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v9.84.0
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v9.83.4
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v9.83.3
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v9.83.2
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v9.83.1
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v9.83.0
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v9.82.2
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v9.82.1
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v9.82.0
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v9.81.1
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v9.81.0
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v9.80.0
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v9.79.0
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v9.78.0
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v9.77.5
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v9.77.4
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v9.77.3
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v9.77.2
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v9.77.1
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v9.77.0
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v9.76.0
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v9.75.0
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v9.74.0
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v9.73.0
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v9.72.1
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v9.72.0
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v9.71.0
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v9.70.2
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v9.70.1
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v9.70.0
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v9.69.1
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v9.69.0
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v9.68.1
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v9.68.0
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v9.67.6
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v9.67.5
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v9.67.4
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v9.67.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v9.67.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v9.67.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v9.67.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v9.66.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v9.65.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v9.64.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v9.63.5
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v9.63.4
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v9.63.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v9.63.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v9.63.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v9.63.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v9.62.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v9.61.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v9.61.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v9.60.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v9.60.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v9.60.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v9.59.6
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v9.59.5
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v9.59.4
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v9.59.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v9.59.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v9.59.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v9.59.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v9.58.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v9.58.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v9.57.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v9.56.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v9.56.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v9.55.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v9.54.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v9.54.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v9.53.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v9.52.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v9.51.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
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.