← Home

@flarenetwork/flare-periphery-contracts

npm

Smart contracts for all Flare chains

14
Versions
MIT
License
No
Install Scripts
Missing
Provenance

Supply chain provenance

Status for the latest visible version.

No SLSA provenance npm registry signatures gitHead linked

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

kuco23fkoprivecavbrehtlukawxlf1333flare-botkristaps.flarenik_flare

Keywords

flareflarenetworksongbirdsmart contractsdefistate connectorftso

Accepted risks

Findings the reviewer chose to accept rather than block on.

SourceRuleReasonAccepted byWhen
phantom-deps phantom-dep:@openzeppelin/contracts AI (phantom-deps): Solidity smart contract library; OpenZeppelin contracts referenced in config/imports, not direct JS imports. ai
phantom-deps phantom-dep:@layerzerolabs/lz-evm-protocol-v2 AI (phantom-deps): Solidity smart contract library; LayerZero protocol referenced in config/imports, not direct JS imports. ai
phantom-deps phantom-dep:@openzeppelin/contracts-upgradeable AI (phantom-deps): Solidity smart contract library; OpenZeppelin upgradeable contracts referenced in config/imports, not direct JS imports. ai

Versions (showing 14 of 14)

Version Deps Published
0.1.50 3 / 3
0.1.49 3 / 3
0.1.48 3 / 3
0.1.47 3 / 3
0.1.46 2 / 3
0.1.45 1 / 3
0.1.43 1 / 3
0.1.42 1 / 3
0.1.41 1 / 3
0.1.40 1 / 3
0.1.39 1 / 3
0.1.27 2 / 2
0.1.26 2 / 0
0.1.24 2 / 0

v0.1.50

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v0.1.49

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v0.1.48

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v0.1.47

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v0.1.46

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v0.1.45

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v0.1.43

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v0.1.42

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v0.1.41

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v0.1.40

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v0.1.39

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v0.1.27

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v0.1.26

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v0.1.24

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.