@rc-component/tooltip
React Tooltip
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 |
|---|---|---|---|---|
| phantom-deps | phantom-dep:@rc-component/father-plugin | AI (phantom-deps): Build tool from same org scope; not imported at runtime, stable false positive for this package. | ai | |
| provenance | no-provenance | AI (provenance): Established react-component org package; lack of Sigstore provenance is common and not a risk signal for this publisher. | ai |
Versions (showing 11 of 11)
| Version | Deps | Published |
|---|---|---|
| 1.4.0 | 3 / 19 | |
| 1.3.4 | 3 / 18 | |
| 1.3.3 | 3 / 20 | |
| 1.3.2 | 3 / 19 | |
| 1.3.1 | 3 / 19 | |
| 1.3.0 | 3 / 19 | |
| 1.2.2 | 3 / 19 | |
| 1.2.1 | 3 / 19 | |
| 1.2.0 | 4 / 18 | |
| 1.1.0 | 4 / 17 | |
| 1.0.0 | 5 / 17 |
v1.3.4
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.3.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.
v1.3.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.3.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.3.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.2.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.2.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.2.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.1.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.