@commercetools-uikit/search-text-input
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 |
|---|---|---|---|---|
| provenance | publisher-changed | AI (provenance): Transition from commercetools-admin to GitHub Actions is a legitimate CI/CD migration, confirmed by SLSA provenance attestation. | ai | |
| publish-pattern | dormant-publish | AI (publish-pattern): Dormancy followed by GitHub Actions publishing is consistent with CI pipeline migration, not account takeover; SLSA attestation confirms integrity. | ai | |
| phantom-deps | phantom-dep:@babel/runtime | AI (phantom-deps): Standard Babel runtime dep in bundled UI kit packages; loaded by convention, not direct import. | ai | |
| phantom-deps | phantom-dep:@emotion/styled | AI (phantom-deps): Emotion styled is referenced in config/theme files; stable false positive for this UI kit package. | ai |
Versions (showing 11 of 11)
| Version | Deps | Published |
|---|---|---|
| 20.6.0 | 10 / 1 | |
| 20.5.0 | 10 / 1 | |
| 20.4.0 | 10 / 1 | |
| 20.3.1 | 10 / 1 | |
| 20.3.0 | 10 / 1 | |
| 20.2.3 | 10 / 1 | |
| 20.2.2 | 10 / 1 | |
| 20.2.1 | 10 / 1 | |
| 20.2.0 | 10 / 1 | |
| 20.1.0 | 10 / 1 | |
| 20.0.0 | 10 / 1 |
v20.6.0
2 findingsThis version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: GitHub Actions.
Published via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v20.5.0
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v20.4.0
2 findingsThis version was published by a different npm account than previous versions on 2026-02-24. 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.
v20.3.1
2 findingsThis version was published by a different npm account than previous versions on 2026-02-10. 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.
v20.3.0
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v20.2.3
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v20.2.2
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v20.2.1
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v20.2.0
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v20.1.0
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v20.0.0
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.