@cleartrip/ct-platform-app-push-sticky-banner
App push sticky banner 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:react-lottie | AI (dependencies): react-lottie is a well-known animation wrapper; pinned to 1.2.4 with no known advisories. | ai | |
| dependencies | unvetted-dep:@cleartrip/ct-design-button | AI (dependencies): Internal Cleartrip design system package; consistent with the publisher org. | ai | |
| dependencies | unvetted-dep:@cleartrip/ct-design-typography | AI (dependencies): Internal Cleartrip design system package; consistent with the publisher org. | ai | |
| provenance | no-provenance | AI (provenance): Internal Cleartrip component library; lack of Sigstore provenance is consistent across all versions and not a risk indicator here. | ai |
Versions (showing 12 of 12)
| Version | Deps | Published |
|---|---|---|
| 4.3.29 | 6 / 1 | |
| 4.3.28 | 6 / 1 | |
| 4.3.27 | 6 / 1 | |
| 4.3.26 | 6 / 1 | |
| 4.3.25 | 6 / 1 | |
| 4.3.24 | 6 / 1 | |
| 4.3.23 | 6 / 1 | |
| 4.3.22 | 6 / 1 | |
| 4.3.21 | 6 / 1 | |
| 4.3.20 | 6 / 1 | |
| 4.3.19 | 6 / 1 | |
| 4.3.10 | 6 / 1 |
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 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.3.26
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.25
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.24
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.23
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.3.22
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.3.21
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.3.20
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.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.