@cleartrip/ct-design-bottomsheet
Bottomsheet 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 |
|---|---|---|---|---|
| phantom-deps | phantom-dep:@cleartrip/ct-design-hooks | AI (phantom-deps): Same-org scoped package; phantom-dep heuristic unreliable for monorepo peer/transitive usage. | ai | |
| phantom-deps | phantom-dep:@cleartrip/ct-design-conditional-wrap | AI (phantom-deps): Same-org scoped package; phantom-dep heuristic unreliable for monorepo peer/transitive usage. | ai | |
| phantom-deps | phantom-dep:@emotion/react | AI (phantom-deps): Referenced in config files (e.g. babel/rollup emotion plugin config); not a real phantom dep. | ai | |
| phantom-deps | phantom-dep:@emotion/styled | AI (phantom-deps): Referenced in config files; stable false positive for this emotion-based component package. | ai |
Versions (showing 28 of 28)
| Version | Deps | Published |
|---|---|---|
| 5.15.0 | 15 / 4 | |
| 5.14.0 | 15 / 4 | |
| 5.13.0 | 15 / 4 | |
| 5.12.0 | 15 / 4 | |
| 5.11.0 | 15 / 4 | |
| 5.10.0 | 15 / 4 | |
| 5.9.0 | 15 / 4 | |
| 5.7.0 | 15 / 4 | |
| 5.6.0 | 15 / 4 | |
| 5.1.0 | 15 / 4 | |
| 5.0.0 | 15 / 4 | |
| 1.19.0 | 8 / 4 | |
| 1.17.0 | 8 / 4 | |
| 1.16.0 | 8 / 4 | |
| 1.15.0 | 8 / 4 | |
| 1.14.0 | 8 / 4 | |
| 1.13.0 | 8 / 4 | |
| 1.12.0 | 8 / 4 | |
| 1.11.0 | 7 / 4 | |
| 1.10.0 | 7 / 4 | |
| 1.9.0 | 7 / 4 | |
| 1.8.0 | 7 / 4 | |
| 1.7.0 | 7 / 4 | |
| 1.6.0 | 7 / 4 | |
| 1.5.0 | 7 / 4 | |
| 1.4.0 | 7 / 4 | |
| 1.2.0 | 7 / 4 | |
| 1.1.0 | 7 / 4 |
v5.15.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.14.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.13.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.16.0
2 findingsPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
This version was published by a different npm account (saranshdawra) than the most recent previously approved version (gkanishk1) on 2024-12-27, but saranshdawra 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.
v1.15.0
2 findingsPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
This version was published by a different npm account (saranshdawra) than the most recent previously approved version (gkanishk1) on 2024-12-23, but saranshdawra 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.
v1.14.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.13.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.12.0
2 findingsPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
This version was published by a different npm account (gkanishk1) than the most recent previously approved version (ashutoshclearip) on 2024-10-03, but gkanishk1 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.
v1.11.0
2 findingsPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
This version was published by a different npm account (gkanishk1) than the most recent previously approved version (ashutoshclearip) on 2024-09-09, but gkanishk1 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.
v1.10.0
2 findingsPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
This version was published by a different npm account (ashutoshclearip) than the most recent previously approved version (bansalraghav19) on 2024-08-08, but ashutoshclearip 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.
v1.9.0
2 findingsPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
This version was published by a different npm account (gkanishk1) than the most recent previously approved version (bansalraghav19) on 2024-08-06, but gkanishk1 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.
v1.8.0
2 findingsPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
This version was published by a different npm account (bansalraghav19) than the most recent previously approved version (ashutoshclearip) on 2024-08-05, but bansalraghav19 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.
v1.7.0
2 findingsPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
This version was published by a different npm account (gkanishk1) than the most recent previously approved version (ashutoshclearip) on 2024-07-30, but gkanishk1 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.
v1.6.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.5.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.4.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.2.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.1.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.