@cleartrip/ct-design-nav-tabs
NavTabs 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 — the axios compromise (March 2026) relied on exactly this gap.
Maintainers
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| phantom-deps | phantom-dep:@emotion/react | AI (phantom-deps): Emotion is a peer/build dep referenced in config; not directly imported in source is expected for this package type. | ai | |
| phantom-deps | phantom-dep:@emotion/styled | AI (phantom-deps): Same as @emotion/react — config-level reference in a CSS-in-JS design system component is expected. | ai | |
| phantom-deps | phantom-dep:@cleartrip/ct-design-tokens | AI (phantom-deps): Same-org design token dep; phantom detection is a false positive for this monorepo-style package. | ai | |
| phantom-deps | phantom-dep:@cleartrip/ct-design-use-merge-refs | AI (phantom-deps): Same-org utility dep; phantom detection is a false positive for this monorepo-style package. | ai | |
| dependencies | unvetted-dep:@cleartrip/ct-design-typography | AI (dependencies): Internal Cleartrip design-system sibling dep; stable pattern across all versions of this package. | ai | |
| dependencies | unvetted-dep:@cleartrip/ct-design-chip | AI (dependencies): Internal Cleartrip design-system sibling dep; stable pattern across all versions of this package. | ai | |
| provenance | no-provenance | AI (provenance): No provenance is consistent across all versions of this package; not a risk signal here. | ai | |
| dependencies | unvetted-dep:@cleartrip/ct-design-horizontal-scroll | AI (dependencies): Internal Cleartrip design-system sibling dep; stable pattern across all versions of this package. | ai | |
| dependencies | unvetted-dep:@cleartrip/ct-design-theme | AI (dependencies): Internal Cleartrip design-system sibling dep; stable pattern across all versions of this package. | ai | |
| dependencies | unvetted-dep:@cleartrip/ct-design-types | AI (dependencies): Internal Cleartrip design-system sibling dep; stable pattern across all versions of this package. | ai | |
| dependencies | unvetted-dep:@cleartrip/ct-design-tokens | AI (dependencies): Internal Cleartrip design-system sibling dep; stable pattern across all versions of this package. | ai |
Versions (showing 5 of 5)
| Version | Deps | Published |
|---|---|---|
| 5.6.0 | 13 / 2 | |
| 5.2.0 | 13 / 2 | |
| 5.1.0 | 13 / 2 | |
| 5.0.0 | 13 / 2 | |
| 3.21.0 | 7 / 1 |
v5.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 (sidhantrajan) than the most recent previously approved version (saranshdawra) on 2026-06-02, 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.
v5.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 (sidhantrajan) than the most recent previously approved version (saranshdawra) on 2026-06-02, 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.
v5.1.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 (sidhantrajan) than the most recent previously approved version (saranshdawra) on 2026-06-02, 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.
v5.0.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 (sidhantrajan) than the most recent previously approved version (saranshdawra) on 2026-06-02, 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.21.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.