@elastic/react-search-ui-views
Supply chain provenance
Status for the latest visible version.
Without SLSA provenance there is no cryptographic link between this tarball and the public source — the axios compromise (March 2026) relied on exactly this gap.
Maintainers
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| source-diff | source-size-dropped | AI (source-diff): Size drop reflects consolidation of build artifacts via tsup, not code removal. | ai | |
| source-diff | obfuscated-file:lib/index.js | AI (source-diff): Standard tsup minified bundle output for this Elastic UI package; not obfuscation. | ai | |
| source-diff | obfuscated-file:lib/index.mjs | AI (source-diff): Standard tsup minified ESM bundle output; not obfuscation. | ai | |
| maintainer-change | maintainer-added | AI (maintainer-change): Elastic org team rotation; new maintainers include known elastic/kibana CI accounts. | ai | |
| maintainer-change | maintainer-removed | AI (maintainer-change): Elastic org team rotation; removals paired with additions consistent with org restructuring. | ai |
Versions (showing 4 of 4)
| Version | Deps | Published |
|---|---|---|
| 1.24.2 | 4 / 10 | |
| 1.24.1 | 4 / 10 | |
| 1.24.0 | 4 / 10 | |
| 1.21.2 | 4 / 16 |
v1.24.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.24.1
4 findingsNewly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Newly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Package 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-05-30, 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.24.0
4 findingsNewly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Newly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Package 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-05-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.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.