@cleartrip/ct-platform-login-form
Login Form
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-field | AI (dependencies): Same org scope (@cleartrip); consistent with all other deps in this package. | ai | |
| provenance | no-provenance | AI (provenance): Internal org package; lack of Sigstore provenance is consistent across all Cleartrip-scoped packages. | ai | |
| phantom-deps | phantom-dep:@cleartrip/ct-design-theme | AI (phantom-deps): Same-org design system dep; likely re-exported transitively, stable false positive. | ai | |
| phantom-deps | phantom-dep:@cleartrip/ct-design-styles | AI (phantom-deps): Same-org design system dep; likely re-exported transitively, stable false positive. | ai | |
| phantom-deps | phantom-dep:@cleartrip/ct-platform-types | AI (phantom-deps): Same-org types package; used for type declarations only, stable false positive. | ai |
Versions (showing 21 of 21)
| Version | Deps | Published |
|---|---|---|
| 2.3.30 | 15 / 0 | |
| 2.3.29 | 15 / 0 | |
| 2.3.28 | 15 / 0 | |
| 2.3.27 | 15 / 0 | |
| 2.3.26 | 15 / 0 | |
| 2.3.25 | 15 / 0 | |
| 2.3.24 | 15 / 0 | |
| 2.3.23 | 15 / 0 | |
| 2.3.22 | 15 / 0 | |
| 2.3.21 | 15 / 0 | |
| 2.3.20 | 15 / 0 | |
| 2.3.19 | 15 / 0 | |
| 2.3.18 | 15 / 0 | |
| 2.3.17 | 15 / 0 | |
| 2.3.16 | 15 / 0 | |
| 2.3.15 | 15 / 0 | |
| 2.3.14 | 15 / 0 | |
| 2.3.13 | 15 / 0 | |
| 2.3.12 | 15 / 0 | |
| 2.3.11 | 15 / 0 | |
| 2.3.10 | 15 / 0 |
v2.3.30
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.3.29
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.3.28
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.3.27
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.3.26
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.3.25
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.3.24
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.3.23
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.3.22
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.3.21
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.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.
v2.3.19
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.3.18
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.3.17
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.3.16
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.3.15
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.3.14
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.3.13
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.3.12
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.3.11
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.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.