@cleartrip/ct-platform-timer-widget
Timer Widget 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:react-countdown | AI (dependencies): react-countdown is a well-known, benign React countdown library; stable false positive for this package. | ai | |
| provenance | no-provenance | AI (provenance): Established org package with 353 versions; lack of provenance is consistent across all prior releases. | ai |
Versions (showing 33 of 33)
| Version | Deps | Published |
|---|---|---|
| 4.3.32 | 7 / 0 | |
| 4.3.31 | 7 / 0 | |
| 4.3.30 | 7 / 0 | |
| 4.3.29 | 7 / 0 | |
| 4.3.28 | 7 / 0 | |
| 4.3.27 | 7 / 0 | |
| 4.3.24 | 7 / 0 | |
| 4.3.23 | 7 / 0 | |
| 4.3.22 | 7 / 0 | |
| 4.3.21 | 7 / 0 | |
| 4.3.20 | 7 / 0 | |
| 4.3.19 | 7 / 0 | |
| 4.3.18 | 7 / 0 | |
| 4.3.17 | 7 / 0 | |
| 4.3.16 | 7 / 0 | |
| 4.3.15 | 7 / 0 | |
| 4.3.14 | 7 / 0 | |
| 4.3.13 | 7 / 0 | |
| 4.3.12 | 7 / 0 | |
| 4.3.11 | 7 / 0 | |
| 4.3.10 | 7 / 0 | |
| 4.3.9 | 7 / 0 | |
| 4.3.8 | 7 / 0 | |
| 4.3.7 | 7 / 0 | |
| 4.3.6 | 7 / 0 | |
| 4.3.5 | 7 / 0 | |
| 4.3.4 | 7 / 0 | |
| 4.3.3 | 7 / 0 | |
| 4.3.2 | 7 / 0 | |
| 4.3.0 | 7 / 0 | |
| 4.1.1 | 7 / 0 | |
| 4.1.0 | 7 / 0 | |
| 4.0.0 | 7 / 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.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. Consider requesting the maintainer enable provenance via CI/CD.
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.