@injectivelabs/wallet-magic Apache-2.0 40 versions

@injectivelabs/wallet-magic

npm Repository Homepage

Magic wallet strategy for use with @injectivelabs/wallet-core.

40

Versions

Apache-2.0

License

No

Install Scripts

Verified

Provenance

Supply chain provenance

Status for the latest visible version.

SLSA provenance attestation npm registry signatures No source commit

Maintainers

albertchonbangjelkoskihmoragregathomasraleemmeloniivan-angelkoskimaxim-injdanidomiproofofzedbrajovicdavidjossefrederick-injectivea1337

Accepted risks

Findings the reviewer chose to accept rather than block on.

Source	Rule	Reason	Accepted by	When
provenance	publisher-changed	AI (provenance): Transition to GitHub Actions CI publisher is confirmed by SLSA attestation; stable for this org's packages.	ai	2026/05/04
provenance	missing-githead	AI (provenance): Missing gitHead is a side-effect of the CI/CD migration; SLSA attestation provides stronger provenance.	ai	2026/05/04
maintainer-change	maintainer-removed	AI (maintainer-change): Maintainer removal consistent with org-level CI pipeline takeover of publishing; no malicious indicators.	ai	2026/05/04
dependencies	unvetted-dep:magic-sdk	AI (dependencies): magic-sdk is the official Magic.link SDK; expected dependency for a Magic wallet integration.	ai	2026/04/30
dependencies	unvetted-dep:@magic-ext/cosmos	AI (dependencies): Official Magic.link Cosmos extension; expected for Injective/Cosmos wallet support.	ai	2026/04/30
dependencies	unvetted-dep:@magic-ext/oauth2	AI (dependencies): Official Magic.link OAuth2 extension; expected for wallet OAuth flows.	ai	2026/04/30

Versions (showing 40 of 153)

Version	Deps	Published
1.15.43	8 / 0	2025-07-14
1.15.42	8 / 0	2025-07-04
1.15.41	8 / 0	2025-07-03
1.15.40	8 / 0	2025-07-03
1.15.39	8 / 0	2025-07-01
1.15.38	8 / 0	2025-07-01
1.15.37	8 / 0	2025-06-30
1.15.36	8 / 0	2025-06-27
1.15.35	8 / 0	2025-06-24
1.15.34	8 / 0	2025-06-23
1.15.33	8 / 0	2025-06-20
1.15.32	8 / 0	2025-06-18
1.15.31	8 / 0	2025-06-17
1.15.30	8 / 0	2025-06-13
1.15.29	8 / 0	2025-06-12
1.15.28	8 / 0	2025-06-09
1.15.27	8 / 0	2025-06-09
1.15.26	8 / 0	2025-06-05
1.15.25	8 / 0	2025-06-03
1.15.24	8 / 0	2025-06-03
1.15.23	8 / 0	2025-06-02
1.15.22	8 / 0	2025-06-02
1.15.21	8 / 0	2025-05-30
1.15.20	8 / 0	2025-05-29
1.15.19	8 / 0	2025-05-27
1.15.18	8 / 0	2025-05-21
1.15.17	8 / 0	2025-05-20
1.15.16	8 / 0	2025-05-20
1.15.15	8 / 0	2025-05-19
1.15.14	8 / 0	2025-05-19
1.15.12	8 / 0	2025-05-19
1.15.11	8 / 0	2025-05-19
1.15.10	8 / 0	2025-05-19
1.15.9	8 / 0	2025-05-19
1.15.8	8 / 0	2025-05-19
1.15.7	8 / 0	2025-05-19
1.15.6	8 / 0	2025-05-14
1.15.5	8 / 0	2025-05-06
1.15.4	8 / 0	2025-04-30
1.15.3	8 / 0	2025-04-28

v1.15.43

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.

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

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

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

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

v1.15.38

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.

v1.15.37

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.

v1.15.36

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.

v1.15.35

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.

v1.15.34

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.

v1.15.33

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.

v1.15.32

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.

v1.15.31

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.

v1.15.30

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.

v1.15.29

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.

v1.15.28

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.

v1.15.27

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.

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

v1.15.6

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.

v1.15.5

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.

v1.15.4

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.

v1.15.3

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.