@flarenetwork/flare-wagmi-periphery-package
Flare Network periphery artifacts wagmi types
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 |
|---|---|---|---|---|
| provenance | no-provenance | AI (provenance): Flare Network org package; no provenance is a process gap, not a security signal for this package. | ai | |
| phantom-deps | phantom-dep:viem | AI (phantom-deps): viem is a peer/runtime dep for wagmi bindings; not directly imported in generated output but legitimately declared. | ai | |
| phantom-deps | phantom-dep:@wagmi/cli | AI (phantom-deps): Build-time codegen tool; referenced in wagmi.config.ts, not imported in source — expected pattern. | ai | |
| phantom-deps | phantom-dep:typescript | AI (phantom-deps): Build-time compiler; not imported in source — standard for TS packages. | ai | |
| phantom-deps | phantom-dep:@types/node | AI (phantom-deps): Type-only package; never directly imported — expected. | ai | |
| phantom-deps | phantom-dep:@layerzerolabs/lz-evm-protocol-v2 | AI (phantom-deps): ABI/config reference for wagmi codegen; not directly imported in output — expected pattern. | ai |
Versions (showing 5 of 5)
| Version | Deps | Published |
|---|---|---|
| 3.4.0 | 6 / 6 | |
| 3.3.0 | 6 / 6 | |
| 3.2.0 | 6 / 6 | |
| 3.1.0 | 6 / 6 | |
| 3.0.0 | 6 / 6 |
v3.4.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.3.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.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.
v3.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.
v3.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.