@cleartrip/ct-platform-recent-search-widget
Recent Search Widget Component
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 |
|---|---|---|---|---|
| provenance | no-provenance | AI (provenance): Established org package with 53 versions; lack of provenance is common and not a risk signal here. | ai | |
| phantom-deps | phantom-dep:@cleartrip/ct-design-theme | AI (phantom-deps): Same-org design system dep; phantom-dep heuristic fires on transitive/re-export patterns common in component libraries. | ai | |
| phantom-deps | phantom-dep:@cleartrip/ct-design-container | AI (phantom-deps): Same-org design system dep; same rationale as ct-design-theme. | ai | |
| phantom-deps | phantom-dep:uuid | AI (phantom-deps): uuid is declared in package.json dependencies; config-file-only reference is a known false-positive pattern for this heuristic. | ai |
Versions (showing 10 of 10)
| Version | Deps | Published |
|---|---|---|
| 1.0.10 | 10 / 0 | |
| 1.0.9 | 10 / 0 | |
| 1.0.8 | 10 / 0 | |
| 1.0.7 | 10 / 0 | |
| 1.0.6 | 10 / 0 | |
| 1.0.5 | 10 / 0 | |
| 1.0.4 | 10 / 0 | |
| 1.0.3 | 10 / 0 | |
| 1.0.2 | 10 / 0 | |
| 1.0.1 | 10 / 0 |
v1.0.10
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.9
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.8
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.7
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.6
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.5
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.4
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.3
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.