@elastic/search-ui
Supply chain provenance
Status for the latest visible version.
Without SLSA provenance there is no cryptographic link between this tarball and the public source, so a manually published version cannot be tied back to a reviewed commit.
Maintainers
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| source-diff | obfuscated-file:lib/index.js | AI (source-diff): tsup-bundled output; minified but not obfuscated. Standard build artifact for this package. | ai | |
| source-diff | obfuscated-file:lib/index.mjs | AI (source-diff): tsup-bundled ESM output; same rationale as lib/index.js. | ai | |
| source-diff | source-size-dropped | AI (source-diff): Size drop reflects consolidation to single tsup bundle, not code removal. | ai | |
| phantom-deps | phantom-dep:date-fns | AI (phantom-deps): date-fns is a declared runtime dep; bundled by tsup so not directly imported in source. | ai |
Versions (showing 10 of 10)
| Version | Deps | Published |
|---|---|---|
| 1.24.2 | 4 / 3 | |
| 1.24.0 | 4 / 3 | |
| 1.23.0 | 4 / 3 | |
| 1.22.2 | 4 / 4 | |
| 1.22.1 | 4 / 4 | |
| 1.22.0 | 4 / 4 | |
| 1.21.5 | 4 / 4 | |
| 1.21.4 | 4 / 4 | |
| 1.21.3 | 4 / 4 | |
| 1.21.2 | 4 / 4 |
v1.23.0
2 findingsPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
This version was published by a different npm account (yan.savitski) than the most recent previously approved version (phoey1) on 2025-04-01, but yan.savitski is listed as a maintainer on prior approved versions (matched on name). This looks like a manual publish by a known maintainer rather than a publisher change. Recorded as INFO for audit trail.
v1.22.2
2 findingsPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
This version was published by a different npm account (phoey1) than the most recent previously approved version (yan.savitski) on 2025-01-06, but phoey1 is listed as a maintainer on prior approved versions (matched on name). This looks like a manual publish by a known maintainer rather than a publisher change. Recorded as INFO for audit trail.
v1.22.1
2 findingsPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
This version was published by a different npm account (phoey1) than the most recent previously approved version (yan.savitski) on 2025-01-06, but phoey1 is listed as a maintainer on prior approved versions (matched on name). This looks like a manual publish by a known maintainer rather than a publisher change. Recorded as INFO for audit trail.
v1.22.0
2 findingsPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
This version was published by a different npm account (yan.savitski) than the most recent previously approved version (phoey1) on 2024-11-28, but yan.savitski is listed as a maintainer on prior approved versions (matched on name). This looks like a manual publish by a known maintainer rather than a publisher change. Recorded as INFO for audit trail.
v1.21.5
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.21.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.21.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.