@servicetitan/anvil2-ext-charts
<h1 align="center"> Anvil2 Extended Charts </h1>
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 |
|---|---|---|---|---|
| phantom-deps | phantom-dep:uuid | AI (phantom-deps): UUID is a standard utility imported indirectly through component code; stable false positive. | ai | |
| phantom-deps | phantom-dep:tabbable | AI (phantom-deps): Tabbable is a standard accessibility utility for React components; stable false positive. | ai | |
| phantom-deps | phantom-dep:classnames | AI (phantom-deps): Classnames is a standard React utility imported indirectly; stable false positive. | ai | |
| phantom-deps | phantom-dep:tinycolor2 | AI (phantom-deps): Tinycolor2 is a color utility imported indirectly in component code; stable false positive. | ai | |
| phantom-deps | phantom-dep:@react-hook/merged-ref | AI (phantom-deps): React hook utility imported indirectly in component code; stable false positive. | ai | |
| phantom-deps | phantom-dep:@react-hook/resize-observer | AI (phantom-deps): React hook utility imported indirectly in component code; stable false positive. | ai |
Versions (showing 9 of 9)
| Version | Deps | Published |
|---|---|---|
| 0.2.1 | 7 / 41 | |
| 0.2.0 | 7 / 41 | |
| 0.1.7 | 7 / 41 | |
| 0.1.6 | 7 / 41 | |
| 0.1.5 | 7 / 41 | |
| 0.1.4 | 7 / 41 | |
| 0.1.3 | 7 / 41 | |
| 0.1.2 | 7 / 41 | |
| 0.1.1 | 7 / 41 |
v0.2.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.2.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.1.7
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.1.6
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.1.5
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.1.4
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.1.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.1.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.1.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.