@flarenetwork/flare-periphery-contracts MIT 46 versions

@flarenetwork/flare-periphery-contracts

npm

Smart contracts for all Flare chains

46

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, so a manually published version cannot be tied back to a reviewed commit.

Maintainers

kuco23fkoprivecavbrehtlukawxlf1333flare-botkristaps.flarenik_flare

Keywords

flareflarenetworksongbirdsmart contractsdefistate connectorftso

Accepted risks

Findings the reviewer chose to accept rather than block on.

Source	Rule	Reason	Accepted by	When
phantom-deps	phantom-dep:@openzeppelin/contracts	AI (phantom-deps): Solidity smart contract library; OpenZeppelin contracts referenced in config/imports, not direct JS imports.	ai	2026/04/30
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	2026/04/30
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	2026/04/30

Versions (showing 46 of 46)

Version	Deps	Published
0.1.52	3 / 3	2026-06-30
0.1.51	3 / 3	2026-06-11
0.1.50	3 / 3	2026-05-01
0.1.49	3 / 3	2026-04-28
0.1.48	3 / 3	2026-04-27
0.1.47	3 / 3	2026-04-23
0.1.46	2 / 3	2026-04-22
0.1.45	1 / 3	2026-03-17
0.1.43	1 / 3	2026-02-26
0.1.42	1 / 3	2026-02-24
0.1.41	1 / 3	2026-02-09
0.1.40	1 / 3	2026-01-22
0.1.39	1 / 3	2026-01-13
0.1.27	2 / 2	2025-06-24
0.1.26	2 / 0	2025-05-28
0.1.24	2 / 0	2025-05-05
0.1.23	2 / 0	2025-04-25
0.1.21	2 / 0	2025-02-08
0.1.20	2 / 0	2025-02-07
0.1.19	2 / 0	2025-02-07
0.1.18	2 / 0	2025-02-05
0.1.17	2 / 0	2025-01-04
0.1.16	2 / 0	2024-09-16
0.1.15	2 / 0	2024-09-11
0.1.14	2 / 0	2024-09-10
0.1.13	2 / 0	2024-09-09
0.1.12	2 / 0	2024-07-12
0.1.11	2 / 0	2024-07-12
0.1.10	2 / 0	2024-07-12
0.1.9	2 / 0	2024-06-28
0.1.8	1 / 0	2024-06-27
0.1.7	1 / 0	2024-05-28
0.1.6	1 / 0	2024-03-25
0.1.5	1 / 0	2024-02-07
0.1.4	1 / 0	2024-02-05
0.1.3	1 / 0	2024-02-05
0.1.2	1 / 0	2023-11-22
0.1.1	1 / 0	2023-10-17
0.1.0	1 / 0	2023-09-15
0.0.8	1 / 0	2023-03-07
0.0.7	1 / 0	2023-02-26
0.0.6	1 / 0	2023-01-16
0.0.5	1 / 0	2023-01-13
0.0.4	1 / 0	2022-12-28
0.0.2	1 / 0	2022-11-18
0.0.1	1 / 0	2022-11-06

v0.1.52

1 finding

LOW No provenance attestation provenance

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

v0.1.23

1 finding

LOW No provenance attestation provenance

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

v0.1.21

1 finding

LOW No provenance attestation provenance

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

v0.1.20

1 finding

LOW No provenance attestation provenance

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

v0.1.19

1 finding

LOW No provenance attestation provenance

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

v0.1.18

1 finding

LOW No provenance attestation provenance

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

v0.1.17

1 finding

LOW No provenance attestation provenance

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

v0.1.16

1 finding

LOW No provenance attestation provenance

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

v0.1.15

1 finding

LOW No provenance attestation provenance

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

v0.1.14

1 finding

LOW No provenance attestation provenance

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

v0.1.13

1 finding

LOW No provenance attestation provenance

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

v0.1.12

1 finding

LOW No provenance attestation provenance

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

v0.1.11

1 finding

LOW No provenance attestation provenance

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

v0.1.10

1 finding

LOW No provenance attestation provenance

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

v0.1.9

1 finding

LOW No provenance attestation provenance

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

v0.1.8

1 finding

LOW No provenance attestation provenance

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

v0.1.7

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.6

1 finding

LOW No provenance attestation provenance

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

v0.1.5

1 finding

LOW No provenance attestation provenance

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

v0.1.4

1 finding

LOW No provenance attestation provenance

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

v0.1.3

1 finding

LOW No provenance attestation provenance

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

v0.1.2

1 finding

LOW No provenance attestation provenance

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

v0.1.1

1 finding

LOW No provenance attestation provenance

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

v0.1.0

1 finding

LOW No provenance attestation provenance

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

v0.0.8

1 finding

LOW No provenance attestation provenance

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

v0.0.7

1 finding

LOW No provenance attestation provenance

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

v0.0.6

1 finding

LOW No provenance attestation provenance

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

v0.0.5

1 finding

LOW No provenance attestation provenance

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

v0.0.4

1 finding

LOW No provenance attestation provenance

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

v0.0.2

1 finding

LOW No provenance attestation provenance

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

v0.0.1

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.