@corsair-dev/ui
Plain-HTML UI helpers for Corsair permissions and related flows
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:@corsair-dev/googlecalendar | AI (phantom-deps): Same-org dep declared for re-export/transitive use; stable pattern for UI meta-package. | ai | |
| phantom-deps | phantom-dep:@corsair-dev/cal | AI (phantom-deps): Same-org dep declared for re-export/transitive use; stable pattern for UI meta-package. | ai | |
| phantom-deps | phantom-dep:@corsair-dev/gmail | AI (phantom-deps): Same-org dep declared for re-export/transitive use; stable pattern for UI meta-package. | ai | |
| phantom-deps | phantom-dep:@corsair-dev/slack | AI (phantom-deps): Same-org dep declared for re-export/transitive use; stable pattern for UI meta-package. | ai | |
| phantom-deps | phantom-dep:@corsair-dev/linear | AI (phantom-deps): Same-org dep declared for re-export/transitive use; stable pattern for UI meta-package. | ai | |
| typosquat | typosquat.levenshtein:uuid | AI (typosquat): Scoped org package @corsair-dev/ui; short name 'ui' triggers false Levenshtein matches, not a typosquat. | ai | |
| typosquat | typosquat.levenshtein:pg | AI (typosquat): Same false-positive pattern; no resemblance to 'pg' in intent or content. | ai | |
| typosquat | typosquat.levenshtein:qs | AI (typosquat): Same false-positive pattern; no resemblance to 'qs' in intent or content. | ai | |
| typosquat | typosquat.levenshtein:joi | AI (typosquat): Same false-positive pattern; no resemblance to 'joi' in intent or content. | ai | |
| typosquat | typosquat.levenshtein:yup | AI (typosquat): Same false-positive pattern; no resemblance to 'yup' in intent or content. | ai |
v0.1.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.