@cleartrip/ct-platform-hotel-cross-sell-lpg-bottomsheet
Hotel cross sell LPG bottomsheet 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 |
|---|---|---|---|---|
| dependencies | unvetted-dep:@cleartrip/ct-design-components | AI (dependencies): Same-org Cleartrip dependency; consistent across versions of this package. | ai | |
| dependencies | unvetted-dep:@cleartrip/ct-platform-hotel-cross-sell-lpg-content | AI (dependencies): Same-org Cleartrip sibling package; consistent pattern across versions. | ai | |
| provenance | no-provenance | AI (provenance): Cleartrip org package; no provenance is consistent across all 159 versions, not a new signal. | ai | |
| phantom-deps | phantom-dep:classnames | AI (phantom-deps): classnames is a common utility; phantom-dep heuristic fires on config-only references in bundled packages. | ai | |
| phantom-deps | phantom-dep:@cleartrip/ct-design-components | AI (phantom-deps): Same-org scoped package; phantom-dep false positive common in monorepo component bundles. | ai |
Versions (showing 8 of 8)
| Version | Deps | Published |
|---|---|---|
| 4.3.29 | 6 / 0 | |
| 4.3.28 | 6 / 0 | |
| 4.3.27 | 6 / 0 | |
| 4.3.26 | 6 / 0 | |
| 4.3.25 | 6 / 0 | |
| 4.3.24 | 6 / 0 | |
| 4.3.19 | 6 / 0 | |
| 4.3.10 | 6 / 0 |
v4.3.29
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.3.28
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.3.27
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.3.26
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.3.25
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.3.24
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.3.19
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.3.10
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.