@cleartrip/ct-platform-hotel-cross-sell-lpg-content
Hotel cross sell LPG content 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, so a manually published version cannot be tied back to a reviewed commit.
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): Internal same-org scoped dependency, consistent across versions. | ai | |
| maintainer-change | maintainer-added | AI (maintainer-change): Publisher has strong track record; no behavior change in this release. | ai | |
| provenance | no-provenance | AI (provenance): Org-internal package; lack of Sigstore provenance is consistent across all versions and poses no elevated risk here. | ai | |
| phantom-deps | phantom-dep:@cleartrip/ct-design-theme | AI (phantom-deps): Same-org dep; phantom-dep heuristic unreliable for monorepo packages that may use peer/transitive imports. | ai | |
| phantom-deps | phantom-dep:@cleartrip/ct-design-typography | AI (phantom-deps): Same-org dep; phantom-dep heuristic unreliable for monorepo packages that may use peer/transitive imports. | ai |
Versions (showing 32 of 32)
| Version | Deps | Published |
|---|---|---|
| 4.3.32 | 8 / 0 | |
| 4.3.31 | 8 / 0 | |
| 4.3.30 | 8 / 0 | |
| 4.3.29 | 8 / 0 | |
| 4.3.27 | 8 / 0 | |
| 4.3.24 | 8 / 0 | |
| 4.3.23 | 8 / 0 | |
| 4.3.22 | 8 / 0 | |
| 4.3.21 | 8 / 0 | |
| 4.3.20 | 8 / 0 | |
| 4.3.19 | 8 / 0 | |
| 4.3.18 | 8 / 0 | |
| 4.3.17 | 8 / 0 | |
| 4.3.16 | 8 / 0 | |
| 4.3.15 | 8 / 0 | |
| 4.3.14 | 8 / 0 | |
| 4.3.13 | 8 / 0 | |
| 4.3.12 | 8 / 0 | |
| 4.3.11 | 8 / 0 | |
| 4.3.10 | 8 / 0 | |
| 4.3.9 | 8 / 0 | |
| 4.3.8 | 8 / 0 | |
| 4.3.7 | 8 / 0 | |
| 4.3.6 | 8 / 0 | |
| 4.3.5 | 8 / 0 | |
| 4.3.4 | 8 / 0 | |
| 4.3.3 | 8 / 0 | |
| 4.3.2 | 8 / 0 | |
| 4.3.0 | 8 / 0 | |
| 4.1.1 | 8 / 0 | |
| 4.1.0 | 8 / 0 | |
| 4.0.0 | 8 / 0 |
v4.3.32
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.3.31
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.3.30
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.18
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.3.17
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.3.16
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.3.15
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.3.14
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.3.13
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.3.12
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.3.11
2 findings[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
This version was published by a different npm account (ashokmpatel) than the most recent previously approved version (ritesh.kumarjena) on 2025-07-03, but ashokmpatel is listed as a maintainer on prior approved versions (matched on name). This looks like a manual publish by a known maintainer rather than a publisher change. Recorded as INFO for audit trail.
v4.3.10
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.3.9
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.3.8
2 findings[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
This version was published by a different npm account (ritesh.kumarjena) than the most recent previously approved version (ashokmpatel) on 2025-04-16, but ritesh.kumarjena is listed as a maintainer on prior approved versions (matched on name). This looks like a manual publish by a known maintainer rather than a publisher change. Recorded as INFO for audit trail.
v4.3.7
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.3.6
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.3.5
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.3.4
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.3.3
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.3.2
2 findings[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
This version was published by a different npm account (ashokmpatel) than the most recent previously approved version (ritesh.kumarjena) on 2025-04-11, but ashokmpatel is listed as a maintainer on prior approved versions (matched on name). This looks like a manual publish by a known maintainer rather than a publisher change. Recorded as INFO for audit trail.
v4.3.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.1.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.1.0
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.0.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.