← Home

@radix-ui/rect

npm Repository Homepage
6
Versions
MIT
License
No
Install Scripts
Verified
Provenance

Supply chain provenance

Status for the latest visible version.

SLSA provenance attestation npm registry signatures No source commit

Maintainers

hadihallakchancestricklandmark-workosnpm-workos

Accepted risks

Findings the reviewer chose to accept rather than block on.

SourceRuleReasonAccepted byWhen
maintainer-change maintainer-removed AI (maintainer-change): Old individual maintainers replaced by org account post-acquisition. ai
provenance publisher-changed AI (provenance): Radix UI moved to GitHub Actions CI/CD publishing under WorkOS; legitimate org transition. ai
provenance missing-githead AI (provenance): GitHub Actions publish flow omits gitHead; SLSA provenance compensates. ai
maintainer-change maintainer-added AI (maintainer-change): npm-workos reflects WorkOS acquisition of Radix UI; legitimate org change. ai
typosquat typosquat.levenshtein:react AI (typosquat): @radix-ui/rect is 'rectangle' utility, not a typosquat of react. Scoped under @radix-ui with 50M+ weekly downloads. ai
typosquat typosquat.levenshtein:next AI (typosquat): rect (rectangle) is a legitimate name; not related to 'next'. Established package in @radix-ui scope. ai
typosquat typosquat.levenshtein:jest AI (typosquat): rect (rectangle) is a legitimate name; not related to 'jest'. Established package in @radix-ui scope. ai
bogus-package bogus-package AI (bogus-package): Small internal monorepo utility; no-deps/no-keywords/no-description is normal for this kind of package. ai

Versions (showing 6 of 6)

Version Deps Published
1.1.3 0 / 3
1.1.2 0 / 3
1.1.1 0 / 4
1.1.0 0 / 0
1.0.1 1 / 0
1.0.0 1 / 0

v1.1.3

2 findings
INFO Has SLSA provenance attestation provenance

Published via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.

INFO Missing gitHead — previous versions had it provenance

[Accepted risk] This version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: GitHub Actions.

v1.0.1

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v1.0.0

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.