@reach/observe-rect
Observe the Rect of a DOM element.
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 |
|---|---|---|---|---|
| provenance | publisher-changed | AI (provenance): Publisher change from ryanflorence to chancestrickland is a documented, legitimate handoff within React Training / Reach UI org. chancestrickland is the known long-term Reach UI maintainer. | ai | |
| maintainer-change | maintainer-added | AI (maintainer-change): chancestrickland and mjackson (Michael Jackson) are both React Training co-founders/core maintainers. Addition is a legitimate organizational change, not a compromise. | ai | |
| source-diff | source-size-tripled | AI (source-diff): Size increase reflects migration to tsdx build tooling producing CJS, ESM, and UMD bundles. Multiple output formats naturally explain the 4.7x size increase. | ai | |
| provenance | missing-githead | AI (provenance): Missing gitHead is consistent with the tsdx tooling migration changing the publish environment. No malicious indicator. | ai | |
| email-domain | unclaimed-email:ryanflorence | AI (email-domain): The 'email' field contains '@ryanflorence', a social handle placeholder, not a real email address. No actual email domain to hijack; finding is a false positive for this package. | ai |
Versions (showing 8 of 8)
| Version | Deps | Published |
|---|---|---|
| 1.2.0 | 0 / 14 | |
| 1.1.0 | 0 / 14 | |
| 1.0.5 | 0 / 14 | |
| 1.0.4 | 0 / 14 | |
| 1.0.3 | 0 / 6 | |
| 1.0.2 | 0 / 6 | |
| 1.0.1 | 0 / 6 | |
| 1.0.0 | 0 / 6 |
v1.2.0
2 findingsPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
[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: chancestrickland.
v1.1.0
2 findingsPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
[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: chancestrickland.
v1.0.5
2 findingsPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
[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: chancestrickland.
v1.0.4
3 findingsThis version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: chancestrickland.
This version was published by a different npm account than previous versions on 2020-01-08. This could indicate a legitimate maintainer transition or an account compromise.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.3
2 findingsMaintainer email '@ryanflorence' uses domain 'ryanflorence' which has no DNS records. An attacker could register this domain to hijack the maintainer identity.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.1
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.