rc-align
align ui component for react
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
Keywords
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| dependencies | unvetted-dep:rc-util | AI (dependencies): rc-util is a well-known shared utility library from the same react-component org; not a security concern for this package. | ai | |
| dependencies | unvetted-dep:dom-align | AI (dependencies): dom-align is the core alignment engine this package wraps; a long-standing, legitimate dependency. | ai | |
| dependencies | unvetted-dep:resize-observer-polyfill | AI (dependencies): resize-observer-polyfill is a widely-used browser polyfill with no security concerns relevant to this package. | ai |
Versions (showing 30 of 30)
| Version | Deps | Published |
|---|---|---|
| 4.0.14 | 6 / 14 | |
| 4.0.13 | 6 / 14 | |
| 4.0.12 | 6 / 12 | |
| 4.0.9 | 5 / 12 | |
| 4.0.8 | 5 / 12 | |
| 4.0.7 | 5 / 12 | |
| 4.0.6 | 5 / 12 | |
| 4.0.5 | 5 / 12 | |
| 4.0.3 | 5 / 12 | |
| 4.0.2 | 5 / 12 | |
| 3.0.0 | 4 / 11 | |
| 2.4.5 | 4 / 8 | |
| 2.4.4 | 4 / 8 | |
| 2.4.3 | 4 / 8 | |
| 2.4.2 | 4 / 8 | |
| 2.4.1 | 5 / 8 | |
| 2.4.0 | 5 / 8 | |
| 2.3.6 | 5 / 7 | |
| 2.3.3 | 2 / 6 | |
| 2.3.2 | 2 / 6 | |
| 2.3.1 | 2 / 6 | |
| 2.3.0 | 2 / 6 | |
| 2.2.0 | 2 / 7 | |
| 2.1.0 | 2 / 7 | |
| 2.0.0 | 2 / 7 | |
| 1.2.1 | 2 / 7 | |
| 1.2.0 | 2 / 7 | |
| 1.1.1 | 2 / 7 | |
| 1.1.0 | 2 / 7 | |
| 1.0.0 | 2 / 7 |
v4.0.14
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.0.13
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.0.12
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.0.9
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.0.8
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.0.7
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.0.6
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.0.5
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.0.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.0.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.0.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.4.5
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.4.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.4.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.4.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.4.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.4.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.3.6
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.3.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.3.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.3.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.3.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.2.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.1.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.0.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.2.1
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. Consider requesting the maintainer enable provenance via CI/CD.
v1.1.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.1.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.