@kong-ui-public/sandbox-layout
A layout component for Vue component sandboxes. Simply slot in your component (`default` slot) and component controls (`controls` slot).
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 publishing to GitHub Actions CI with SLSA attestation; stable pattern for this package. | ai | |
| dependencies | unvetted-dep:@kong/icons | AI (dependencies): @kong/icons is a first-party Kong org package; stable false positive for this package family. | ai |
Versions (showing 100 of 152)
| Version | Deps | Published |
|---|---|---|
| 2.6.4 | 1 / 4 | |
| 2.6.3 | 1 / 4 | |
| 2.6.2 | 1 / 4 | |
| 2.6.1 | 1 / 4 | |
| 2.6.0 | 1 / 4 | |
| 2.5.0 | 1 / 4 | |
| 2.4.26 | 1 / 4 | |
| 2.4.25 | 1 / 4 | |
| 2.4.24 | 1 / 4 | |
| 2.4.23 | 1 / 4 | |
| 2.4.22 | 1 / 4 | |
| 2.4.21 | 1 / 4 | |
| 2.4.20 | 1 / 4 | |
| 2.4.19 | 1 / 4 | |
| 2.4.18 | 1 / 4 | |
| 2.4.17 | 1 / 4 | |
| 2.4.16 | 1 / 4 | |
| 2.4.15 | 1 / 4 | |
| 2.4.14 | 1 / 4 | |
| 2.4.13 | 1 / 4 | |
| 2.4.12 | 1 / 4 | |
| 2.4.11 | 1 / 4 | |
| 2.4.10 | 1 / 4 | |
| 2.4.9 | 1 / 4 | |
| 2.4.8 | 1 / 4 | |
| 2.4.7 | 1 / 4 | |
| 2.4.6 | 1 / 4 | |
| 2.4.5 | 1 / 4 | |
| 2.4.4 | 1 / 4 | |
| 2.4.3 | 1 / 4 | |
| 2.4.2 | 1 / 4 | |
| 2.4.1 | 1 / 4 | |
| 2.4.0 | 1 / 4 | |
| 2.3.26 | 1 / 4 | |
| 2.3.25 | 1 / 4 | |
| 2.3.24 | 1 / 4 | |
| 2.3.23 | 1 / 4 | |
| 2.3.22 | 1 / 4 | |
| 2.3.21 | 1 / 4 | |
| 2.3.20 | 1 / 4 | |
| 2.3.19 | 1 / 4 | |
| 2.3.18 | 1 / 4 | |
| 2.3.17 | 1 / 4 | |
| 2.3.16 | 1 / 4 | |
| 2.3.15 | 1 / 4 | |
| 2.3.14 | 1 / 4 | |
| 2.3.13 | 1 / 4 | |
| 2.3.12 | 1 / 4 | |
| 2.3.11 | 1 / 4 | |
| 2.3.10 | 1 / 4 | |
| 2.3.9 | 1 / 4 | |
| 2.3.8 | 1 / 4 | |
| 2.3.7 | 1 / 4 | |
| 2.3.6 | 1 / 4 | |
| 2.3.5 | 1 / 4 | |
| 2.3.4 | 1 / 4 | |
| 2.3.3 | 1 / 4 | |
| 2.3.2 | 1 / 4 | |
| 2.3.1 | 1 / 4 | |
| 2.3.0 | 1 / 4 | |
| 2.2.6 | 1 / 4 | |
| 2.2.5 | 1 / 4 | |
| 2.2.4 | 1 / 4 | |
| 2.2.3 | 1 / 4 | |
| 2.2.2 | 1 / 4 | |
| 2.2.1 | 1 / 4 | |
| 2.1.75 | 1 / 4 | |
| 2.1.74 | 1 / 4 | |
| 2.1.73 | 1 / 4 | |
| 2.1.72 | 1 / 4 | |
| 2.1.71 | 1 / 4 | |
| 2.1.70 | 1 / 4 | |
| 2.1.69 | 1 / 4 | |
| 2.1.68 | 1 / 4 | |
| 2.1.67 | 1 / 4 | |
| 2.1.66 | 1 / 4 | |
| 2.1.65 | 1 / 4 | |
| 2.1.64 | 1 / 4 | |
| 2.1.63 | 1 / 4 | |
| 2.1.62 | 1 / 4 | |
| 2.1.61 | 1 / 4 | |
| 2.1.60 | 1 / 4 | |
| 2.1.59 | 1 / 4 | |
| 2.1.58 | 1 / 4 | |
| 2.1.57 | 1 / 4 | |
| 2.1.56 | 1 / 4 | |
| 2.1.55 | 1 / 4 | |
| 2.1.54 | 1 / 4 | |
| 2.1.53 | 1 / 4 | |
| 2.1.52 | 1 / 4 | |
| 2.1.51 | 1 / 4 | |
| 2.1.50 | 1 / 4 | |
| 2.1.49 | 1 / 4 | |
| 2.1.48 | 1 / 4 | |
| 2.1.47 | 1 / 4 | |
| 2.1.46 | 1 / 4 | |
| 2.1.45 | 1 / 4 | |
| 2.1.44 | 1 / 4 | |
| 2.1.43 | 1 / 4 | |
| 2.1.42 | 1 / 4 |
v2.6.4
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v2.6.3
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v2.6.2
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v2.6.1
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v2.6.0
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.26
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v2.4.25
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v2.4.24
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v2.1.68
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.1.67
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.1.66
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.1.65
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.1.64
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.1.63
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.1.62
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
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.