@kong-ui-public/misc-widgets
A collection of miscellaneous components and widgets.
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 |
|---|---|---|---|---|
| provenance | publisher-changed | AI (provenance): Kong org migrated to GitHub Actions CI publishing; SLSA attestation confirms legitimate CI/CD origin. | ai |
Versions (showing 100 of 168)
| Version | Deps | Published |
|---|---|---|
| 2.5.3 | 0 / 3 | |
| 2.5.2 | 0 / 3 | |
| 2.5.1 | 0 / 3 | |
| 2.5.0 | 0 / 3 | |
| 2.4.0 | 0 / 3 | |
| 2.3.38 | 0 / 3 | |
| 2.3.37 | 0 / 3 | |
| 2.3.36 | 0 / 3 | |
| 2.3.35 | 0 / 3 | |
| 2.3.34 | 0 / 3 | |
| 2.3.33 | 0 / 3 | |
| 2.3.32 | 0 / 3 | |
| 2.3.31 | 0 / 3 | |
| 2.3.30 | 0 / 3 | |
| 2.3.29 | 0 / 3 | |
| 2.3.28 | 0 / 3 | |
| 2.3.27 | 0 / 3 | |
| 2.3.26 | 0 / 3 | |
| 2.3.25 | 0 / 3 | |
| 2.3.24 | 0 / 3 | |
| 2.3.23 | 0 / 3 | |
| 2.3.22 | 0 / 3 | |
| 2.3.21 | 0 / 3 | |
| 2.3.20 | 0 / 3 | |
| 2.3.19 | 0 / 3 | |
| 2.3.18 | 0 / 3 | |
| 2.3.17 | 0 / 3 | |
| 2.3.16 | 0 / 3 | |
| 2.3.15 | 0 / 3 | |
| 2.3.14 | 0 / 3 | |
| 2.3.13 | 0 / 3 | |
| 2.3.12 | 0 / 3 | |
| 2.3.11 | 0 / 3 | |
| 2.3.10 | 0 / 3 | |
| 2.3.9 | 0 / 3 | |
| 2.3.8 | 0 / 3 | |
| 2.3.7 | 0 / 3 | |
| 2.3.6 | 0 / 3 | |
| 2.3.5 | 0 / 3 | |
| 2.3.4 | 0 / 3 | |
| 2.3.3 | 0 / 3 | |
| 2.3.2 | 0 / 3 | |
| 2.3.1 | 0 / 3 | |
| 2.3.0 | 0 / 3 | |
| 2.2.7 | 0 / 3 | |
| 2.2.6 | 0 / 3 | |
| 2.2.5 | 0 / 3 | |
| 2.2.4 | 0 / 3 | |
| 2.2.3 | 0 / 3 | |
| 2.2.2 | 0 / 3 | |
| 2.2.1 | 0 / 3 | |
| 2.1.69 | 0 / 3 | |
| 2.1.68 | 0 / 3 | |
| 2.1.67 | 0 / 3 | |
| 2.1.66 | 0 / 3 | |
| 2.1.65 | 0 / 3 | |
| 2.1.64 | 0 / 3 | |
| 2.1.63 | 0 / 3 | |
| 2.1.62 | 0 / 3 | |
| 2.1.61 | 0 / 3 | |
| 2.1.60 | 0 / 3 | |
| 2.1.59 | 0 / 3 | |
| 2.1.58 | 0 / 3 | |
| 2.1.57 | 0 / 3 | |
| 2.1.56 | 0 / 3 | |
| 2.1.55 | 0 / 3 | |
| 2.1.54 | 0 / 3 | |
| 2.1.53 | 0 / 3 | |
| 2.1.52 | 0 / 3 | |
| 2.1.51 | 0 / 3 | |
| 2.1.50 | 0 / 3 | |
| 2.1.49 | 0 / 3 | |
| 2.1.48 | 0 / 3 | |
| 2.1.47 | 0 / 3 | |
| 2.1.46 | 0 / 3 | |
| 2.1.45 | 0 / 3 | |
| 2.1.44 | 0 / 3 | |
| 2.1.43 | 0 / 3 | |
| 2.1.42 | 0 / 3 | |
| 2.1.41 | 0 / 3 | |
| 2.1.40 | 0 / 3 | |
| 2.1.39 | 0 / 3 | |
| 2.1.38 | 0 / 3 | |
| 2.1.37 | 0 / 3 | |
| 2.1.36 | 0 / 3 | |
| 2.1.35 | 0 / 3 | |
| 2.1.34 | 0 / 3 | |
| 2.1.33 | 0 / 3 | |
| 2.1.32 | 0 / 3 | |
| 2.1.31 | 0 / 3 | |
| 2.1.30 | 0 / 3 | |
| 2.1.29 | 0 / 3 | |
| 2.1.28 | 0 / 3 | |
| 2.1.27 | 0 / 3 | |
| 2.1.26 | 0 / 3 | |
| 2.1.25 | 0 / 3 | |
| 2.1.24 | 0 / 3 | |
| 2.1.23 | 0 / 3 | |
| 2.1.22 | 0 / 3 | |
| 2.1.21 | 0 / 3 |
v2.5.3
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v2.5.2
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v2.5.1
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v2.5.0
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v2.4.0
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v2.3.38
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v2.3.37
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v2.1.61
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.1.60
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.1.59
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.1.58
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.1.57
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.1.56
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.1.55
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.1.54
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.1.53
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.1.52
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.1.51
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.1.50
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.1.49
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.1.48
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.1.47
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.1.46
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.1.45
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.1.44
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.1.43
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.1.42
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.1.41
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.1.40
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.1.39
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.1.38
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.1.37
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.1.36
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.1.35
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.1.34
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.1.33
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.1.32
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.1.31
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.1.30
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.1.29
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.1.28
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.1.27
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.1.26
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.1.25
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.1.24
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.1.23
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.1.22
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.1.21
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.