@elastic/prismjs-esql
Supply chain provenance
Status for the latest visible version.
Maintainers
Keywords
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| dependencies | unvetted-dep:@elastic/esql-definitions | AI (dependencies): First-party Elastic sibling package, same org/team. | ai | |
| publish-pattern | new-deps-added | AI (publish-pattern): Expected addition of first-party Elastic dependency. | ai |
Versions (showing 9 of 9)
| Version | Deps | Published |
|---|---|---|
| 4.14.0 | 1 / 6 | |
| 4.13.0 | 1 / 6 | |
| 4.12.0 | 1 / 6 | |
| 4.11.0 | 0 / 6 | |
| 1.1.4 | 0 / 18 | |
| 1.1.3 | 0 / 5 | |
| 1.1.2 | 0 / 5 | |
| 1.1.0 | 0 / 5 | |
| 1.0.0 | 0 / 2 |
v4.14.0
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v4.13.0
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v4.12.0
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v4.11.0
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v1.1.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.