@reach/tooltip
Accessible tooltips
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 |
|---|---|---|---|---|
| npm-metadata | suspicious-initial-version | AI (npm-metadata): @reach/* monorepo uses 0.0.0 as a placeholder version for initial package scaffolding; this is a stable false positive for this package family. | ai | |
| bogus-package | bogus-package | AI (bogus-package): chancestrickland is the legitimate Reach UI maintainer with 1777 approved packages; spam flag is a false positive for this scope. | ai | |
| provenance | no-provenance | AI (provenance): Reach UI predates Sigstore provenance; absence is expected for this package's publish era. | ai | |
| source-diff | obfuscated-file:dist/index.d.ts | AI (source-diff): dist/index.d.ts is a TypeScript declaration file generated by tsdx; long lines are normal for inlined complex types, not obfuscation. Stable false positive for this package. | ai | |
| provenance | publisher-changed | AI (provenance): ryanflorence and mjackson are co-maintainers of the @reach/* monorepo; this transition is a known legitimate handoff within the same team. | ai | |
| email-domain | unclaimed-email:ryanflorence | AI (email-domain): The 'email' field contains a Twitter handle (@ryanflorence), not a real email address. No actual email domain risk exists. | ai | |
| maintainer-change | maintainer-added | AI (maintainer-change): mjackson is a long-standing co-maintainer of the @reach/* suite alongside ryanflorence; addition is legitimate. | ai |
Versions (showing 51 of 55)
| Version | Deps | Published |
|---|---|---|
| 0.18.0 | 6 / 6 | |
| 0.17.0 | 8 / 2 | |
| 0.16.2 | 8 / 2 | |
| 0.16.0 | 8 / 2 | |
| 0.15.3 | 8 / 2 | |
| 0.15.2 | 8 / 2 | |
| 0.15.0 | 8 / 2 | |
| 0.14.0 | 7 / 2 | |
| 0.13.2 | 7 / 2 | |
| 0.13.1 | 7 / 2 | |
| 0.13.0 | 7 / 0 | |
| 0.12.1 | 7 / 0 | |
| 0.12.0 | 7 / 0 | |
| 0.11.2 | 7 / 0 | |
| 0.11.1 | 7 / 0 | |
| 0.11.0 | 7 / 0 | |
| 0.10.5 | 7 / 0 | |
| 0.10.4 | 7 / 0 | |
| 0.10.3 | 7 / 0 | |
| 0.10.2 | 7 / 0 | |
| 0.10.1 | 7 / 0 | |
| 0.10.0 | 7 / 0 | |
| 0.9.1 | 7 / 0 | |
| 0.9.0 | 7 / 0 | |
| 0.8.6 | 7 / 0 | |
| 0.8.5 | 7 / 0 | |
| 0.8.4 | 7 / 0 | |
| 0.8.3 | 7 / 0 | |
| 0.8.2 | 7 / 0 | |
| 0.8.0 | 6 / 0 | |
| 0.7.4 | 6 / 0 | |
| 0.7.3 | 6 / 0 | |
| 0.7.2 | 6 / 0 | |
| 0.7.0 | 6 / 0 | |
| 0.6.4 | 6 / 0 | |
| 0.6.3 | 6 / 0 | |
| 0.6.2 | 6 / 0 | |
| 0.6.1 | 6 / 1 | |
| 0.5.4 | 6 / 1 | |
| 0.5.3 | 6 / 1 | |
| 0.5.0 | 6 / 1 | |
| 0.4.0 | 6 / 1 | |
| 0.3.0 | 6 / 1 | |
| 0.2.2 | 6 / 1 | |
| 0.2.1 | 6 / 1 | |
| 0.2.0 | 6 / 1 | |
| 0.1.7 | 6 / 1 | |
| 0.1.6 | 6 / 1 | |
| 0.1.5 | 6 / 1 | |
| 0.1.4 | 6 / 1 | |
| 0.1.3 | 6 / 1 |
v0.18.0
2 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.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.17.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.16.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.16.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.15.3
2 findings[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
[Accepted risk] This version was published by a different npm account than previous versions on 2021-07-10. This could indicate a legitimate maintainer transition or an account compromise.
v0.15.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.15.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.14.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.13.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.13.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.13.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.12.1
2 findings[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
[Accepted risk] This version was published by a different npm account than previous versions on 2020-11-27. This could indicate a legitimate maintainer transition or an account compromise.
v0.12.0
2 findings[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
[Accepted risk] This version was published by a different npm account than previous versions on 2020-11-26. This could indicate a legitimate maintainer transition or an account compromise.
v0.11.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.11.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.11.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.10.5
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.10.4
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.10.3
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.10.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.10.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.10.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.9.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.9.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.8.6
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.8.5
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.8.4
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.8.3
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.8.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.8.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.7.4
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.7.3
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.7.2
2 findingsNewly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.7.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.6.4
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.6.3
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.6.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.6.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.5.4
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.5.3
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.5.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.4.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.3.0
3 findingsThis version was published by a different npm account than previous versions on 2019-10-11. This could indicate a legitimate maintainer transition or an account compromise.
Maintainer 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.
v0.2.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.2.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.2.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.7
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.6
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.5
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.4
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.3
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.