@liberfi.io/ui-perpetuals No license 20 versions

@liberfi.io/ui-perpetuals

npm

Perpetuals for Liberfi React SDK

20

Versions

—

License

No

Install Scripts

Missing

Provenance

Supply chain provenance

Status for the latest visible version.

No SLSA provenance npm registry signatures No source commit

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

bombdmod

Accepted risks

Findings the reviewer chose to accept rather than block on.

Source	Rule	Reason	Accepted by	When
phantom-deps	phantom-dep:@liberfi.io/ui	AI (phantom-deps): Same-org scope dependency; phantom-dep heuristic is a stable false positive for this monorepo-style package.	ai	2026/05/05
phantom-deps	phantom-dep:@liberfi.io/core	AI (phantom-deps): Same-org scope dependency; phantom-dep heuristic is a stable false positive for this monorepo-style package.	ai	2026/05/05
phantom-deps	phantom-dep:@liberfi.io/i18n	AI (phantom-deps): Same-org scope dependency; phantom-dep heuristic is a stable false positive for this monorepo-style package.	ai	2026/05/05
phantom-deps	phantom-dep:@liberfi.io/hooks	AI (phantom-deps): Same-org monorepo dep; phantom-dep heuristic fires on indirect/re-exported usage patterns.	ai	2026/04/29
phantom-deps	phantom-dep:tailwind-variants	AI (phantom-deps): Referenced in config files per finding; not a direct import but legitimately declared.	ai	2026/04/29
phantom-deps	phantom-dep:@liberfi.io/types	AI (phantom-deps): Same-org monorepo dep; type-only imports may not appear as direct imports.	ai	2026/04/29
phantom-deps	phantom-dep:@liberfi.io/utils	AI (phantom-deps): Same-org monorepo dep; stable false positive for this package.	ai	2026/04/29

Versions (showing 20 of 229)

Version	Deps	Published
0.1.26	6 / 8	2026-03-08
0.1.25	6 / 8	2026-03-06
0.1.24	6 / 13	2026-03-06
0.1.23	6 / 13	2026-03-06
0.1.22	6 / 13	2026-03-04
0.1.21	6 / 13	2026-03-04
0.1.20	6 / 13	2026-03-04
0.1.19	6 / 13	2026-03-04
0.1.18	6 / 13	2026-03-04
0.1.17	6 / 13	2026-03-02
0.1.16	6 / 13	2026-03-02
0.1.15	7 / 13	2026-03-02
0.1.14	7 / 13	2026-02-28
0.1.13	7 / 13	2026-02-28
0.1.12	7 / 13	2026-02-26
0.1.11	7 / 13	2026-02-25
0.1.10	7 / 13	2026-02-25
0.1.9	7 / 13	2026-02-24
0.1.8	7 / 13	2026-02-24
0.1.7	7 / 13	2026-02-24

v0.1.26

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

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

v0.1.23

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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