@kong-ui-public/core
> **Note**: This package must **not** contain Vue 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 |
|---|---|---|---|---|
| provenance | publisher-changed | AI (provenance): Transition to GitHub Actions CI publisher is confirmed by SLSA provenance attestation; stable pattern for this package going forward. | ai | |
| bogus-package | bogus-package | AI (bogus-package): Established Kong UI library with 422 versions; sparse README/keywords are a cosmetic issue, not a spam signal. | ai | |
| typosquat | typosquat.levenshtein:cors | AI (typosquat): Scoped Kong org package; name similarity to 'cors' is coincidental, not a typosquat. | ai | |
| phantom-deps | phantom-dep:date-fns | AI (phantom-deps): date-fns is a declared runtime dependency; bundled into dist rather than directly imported at source level. | ai |
Versions (showing 30 of 30)
| Version | Deps | Published |
|---|---|---|
| 1.11.24 | 1 / 2 | |
| 1.11.23 | 1 / 2 | |
| 1.11.22 | 1 / 2 | |
| 1.11.21 | 1 / 2 | |
| 1.11.20 | 1 / 2 | |
| 1.11.19 | 1 / 2 | |
| 1.11.18 | 1 / 2 | |
| 1.11.17 | 1 / 2 | |
| 1.11.16 | 1 / 2 | |
| 1.11.15 | 1 / 2 | |
| 1.11.14 | 1 / 2 | |
| 1.11.13 | 1 / 2 | |
| 1.11.12 | 1 / 2 | |
| 1.11.11 | 1 / 2 | |
| 1.11.10 | 1 / 2 | |
| 1.11.9 | 1 / 2 | |
| 1.11.8 | 1 / 2 | |
| 1.11.7 | 1 / 2 | |
| 1.11.6 | 1 / 2 | |
| 1.11.5 | 1 / 2 | |
| 1.11.4 | 1 / 3 | |
| 1.11.3 | 1 / 2 | |
| 1.11.2 | 1 / 2 | |
| 1.11.1 | 1 / 2 | |
| 1.11.0 | 1 / 2 | |
| 1.10.11 | 1 / 2 | |
| 1.10.10 | 1 / 2 | |
| 1.10.9 | 1 / 2 | |
| 1.10.8 | 1 / 2 | |
| 1.10.7 | 1 / 2 |
v1.11.24
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v1.11.23
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v1.11.22
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v1.11.21
2 findingsPackage name '@kong-ui-public/core' is 1 edit(s) away from popular package 'cors'.
Published via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v1.11.13
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v1.11.12
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v1.11.11
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v1.11.10
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v1.11.9
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v1.11.8
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v1.11.7
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v1.11.6
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v1.11.5
2 findingsThis version was published by a different npm account than previous versions on 2025-10-29. This could indicate a legitimate maintainer transition or an account compromise.
Published via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v1.11.4
2 findingsThis version was published by a different npm account than previous versions on 2025-10-29. This could indicate a legitimate maintainer transition or an account compromise.
Published via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v1.11.3
2 findingsThis version was published by a different npm account than previous versions on 2025-09-12. This could indicate a legitimate maintainer transition or an account compromise.
Published via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v1.11.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.11.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.11.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.10.11
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.10.10
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.10.9
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.10.8
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.10.7
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.