@cleartrip/ct-design-typography
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 |
|---|---|---|---|---|
| maintainer-change | maintainer-added | AI (maintainer-change): Active internal team rotation on a large Cleartrip monorepo; consistent with org-level maintainer management. | ai | |
| maintainer-change | maintainer-removed | AI (maintainer-change): Same org-level rotation; no external actors involved. | ai | |
| phantom-deps | phantom-dep:@emotion/react | AI (phantom-deps): @emotion/react is used via babel plugin / JSX transform config, not direct import; stable pattern for emotion-based component libs. | ai | |
| phantom-deps | phantom-dep:@emotion/styled | AI (phantom-deps): Same as @emotion/react — emotion styled usage may be indirect via JSX transform; stable false positive for this package. | ai | |
| npm-metadata | no-description | AI (npm-metadata): Monorepo component package; missing description is a stable pattern across all @cleartrip/ct-design-* packages. | ai | |
| provenance | no-provenance | AI (provenance): No provenance across the entire @cleartrip design-system; consistent pattern, not a per-version anomaly. | ai | |
| bogus-package | bogus-package | AI (bogus-package): Part of Cleartrip's internal design-system monorepo; sparse metadata is expected for scoped component packages. | ai |
Versions (showing 36 of 36)
| Version | Deps | Published |
|---|---|---|
| 5.14.0 | 9 / 1 | |
| 5.13.0 | 9 / 1 | |
| 5.12.0 | 9 / 1 | |
| 5.11.0 | 9 / 1 | |
| 5.10.0 | 9 / 1 | |
| 5.9.0 | 9 / 1 | |
| 5.8.0 | 9 / 1 | |
| 5.7.0 | 9 / 1 | |
| 5.6.0 | 9 / 1 | |
| 5.5.0 | 9 / 1 | |
| 5.2.0 | 9 / 1 | |
| 5.1.0 | 9 / 1 | |
| 5.0.0 | 9 / 1 | |
| 3.21.0 | 4 / 0 | |
| 3.20.0 | 4 / 0 | |
| 3.19.0 | 4 / 0 | |
| 3.18.0 | 4 / 0 | |
| 3.17.0 | 4 / 0 | |
| 3.16.0 | 4 / 0 | |
| 3.15.0 | 4 / 0 | |
| 3.14.0 | 4 / 0 | |
| 3.13.0 | 4 / 0 | |
| 3.12.0 | 4 / 0 | |
| 3.11.0 | 4 / 0 | |
| 3.10.0 | 4 / 0 | |
| 3.9.0 | 4 / 0 | |
| 3.8.0 | 4 / 0 | |
| 3.7.0 | 4 / 0 | |
| 3.6.0 | 4 / 0 | |
| 3.5.0 | 4 / 0 | |
| 3.4.0 | 4 / 0 | |
| 3.3.0 | 4 / 0 | |
| 3.2.0 | 4 / 0 | |
| 3.1.1 | 4 / 0 | |
| 3.1.0 | 4 / 0 | |
| 3.0.0 | 4 / 0 |
v5.14.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.13.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.12.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.20.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.19.0
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 (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.
v3.18.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.17.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.16.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.15.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.14.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.13.0
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 (ashutoshclearip) than the most recent previously approved version (gkanishk1) 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.
v3.12.0
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 (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.
v3.11.0
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 (bansalraghav19) than the most recent previously approved version (gkanishk1) 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.
v3.10.0
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 (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.
v3.9.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.8.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.7.0
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 (ashutoshclearip) than the most recent previously approved version (gkanishk1) on 2024-06-27, 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.
v3.6.0
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 (gkanishk1) than the most recent previously approved version (ashutoshclearip) on 2024-06-25, 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.
v3.5.0
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 (ashutoshclearip) than the most recent previously approved version (gkanishk1) on 2024-06-25, 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.
v3.4.0
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 (gkanishk1) than the most recent previously approved version (bansalraghav19) on 2024-06-20, 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.
v3.3.0
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 (bansalraghav19) than the most recent previously approved version (gkanishk1) on 2024-06-20, 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.
v3.2.0
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 (gkanishk1) than the most recent previously approved version (sidhantrajan) on 2024-06-10, 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.
v3.1.1
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 (sidhantrajan) than the most recent previously approved version (gkanishk1) on 2024-06-04, but sidhantrajan 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.
v3.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.
v3.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.