@fiscozen/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, so a manually published version cannot be tied back to a reviewed commit.
Maintainers
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| provenance | no-provenance | AI (provenance): Internal @fiscozen design system package; provenance not configured for this org's packages. | ai |
Versions (showing 9 of 9)
| Version | Deps | Published |
|---|---|---|
| 3.0.4 | 1 / 20 | |
| 3.0.3 | 1 / 20 | |
| 3.0.2 | 1 / 20 | |
| 3.0.1 | 3 / 18 | |
| 3.0.0 | 3 / 18 | |
| 2.0.0 | 3 / 18 | |
| 1.0.3 | 3 / 18 | |
| 1.0.2 | 4 / 18 | |
| 1.0.1 | 0 / 22 |
v3.0.4
2 findings[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
This version was published by a different npm account (trebh) than the most recent previously approved version (panicofr) on 2026-07-17, but trebh is listed as a maintainer on prior approved versions (matched on name). This looks like a manual publish by a known maintainer rather than a publisher change. Recorded as INFO for audit trail.