@cleartrip/ct-platform-rtbs
RTB 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 |
|---|---|---|---|---|
| provenance | no-provenance | AI (provenance): Established internal Cleartrip package; lack of provenance is consistent across all 338 versions. | ai | |
| phantom-deps | phantom-dep:classnames | AI (phantom-deps): classnames is explicitly declared in package.json dependencies; phantom-dep is a false positive for this package. | ai |
Versions (showing 28 of 28)
| Version | Deps | Published |
|---|---|---|
| 2.3.32 | 6 / 0 | |
| 2.3.31 | 6 / 0 | |
| 2.3.30 | 6 / 0 | |
| 2.3.29 | 6 / 0 | |
| 2.3.28 | 6 / 0 | |
| 2.3.27 | 6 / 0 | |
| 2.3.26 | 6 / 0 | |
| 2.3.25 | 6 / 0 | |
| 2.3.24 | 6 / 0 | |
| 2.3.23 | 6 / 0 | |
| 2.3.22 | 6 / 0 | |
| 2.3.21 | 6 / 0 | |
| 2.3.20 | 6 / 0 | |
| 2.3.19 | 6 / 0 | |
| 2.3.10 | 6 / 0 | |
| 2.3.9 | 6 / 0 | |
| 2.3.8 | 6 / 0 | |
| 2.3.7 | 6 / 0 | |
| 2.3.6 | 6 / 0 | |
| 2.3.5 | 6 / 0 | |
| 2.3.4 | 6 / 0 | |
| 2.3.3 | 6 / 0 | |
| 2.3.2 | 6 / 0 | |
| 2.3.0 | 6 / 0 | |
| 2.1.2 | 6 / 0 | |
| 2.1.1 | 6 / 0 | |
| 2.1.0 | 6 / 0 | |
| 2.0.0 | 6 / 0 |
v2.3.32
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.3.31
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.3.30
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.3.9
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.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.
v2.3.7
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.3.6
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.3.5
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.3.4
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.3.3
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.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.
v2.3.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.1.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.1.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.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.
v2.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.