@frak-labs/nexus-sdk — Greenflagged

Legacy SDK, only used here to provide nice wrapper and redirection for older implementation, to not break anything and keep them updated with latest security updates.

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

Maintainers

konfeaturesrod

Keywords

frak-labsnexus-walleterc-4337eip-4337smart-wallet

Accepted risks

Findings the reviewer chose to accept rather than block on.

Source	Rule	Reason	Accepted by	When
provenance	publisher-changed	AI (provenance): Transition between two listed org maintainers, no behavioral change in diff.	ai	2026/07/12
maintainer-change	maintainer-added	AI (maintainer-change): New maintainer is an existing listed org member.	ai	2026/07/12
maintainer-change	maintainer-removed	AI (maintainer-change): Removed maintainer still listed in package.json; benign handoff.	ai	2026/07/12
phantom-deps	phantom-dep:@frak-labs/ui	AI (phantom-deps): Same-org internal dep; phantom-dep heuristic fires on bundled/re-exported packages in monorepos.	ai	2026/05/04
phantom-deps	phantom-dep:@frak-labs/core-sdk	AI (phantom-deps): Same-org internal dep; phantom-dep heuristic fires on bundled/re-exported packages in monorepos.	ai	2026/05/04

Versions (showing 52 of 52)

Version	Deps	Published
0.0.56	1 / 4	2026-07-20
0.0.55	1 / 4	2026-07-08
0.0.54	1 / 4	2026-06-30
0.0.53	1 / 4	2026-06-23
0.0.52	1 / 4	2026-06-04
0.0.51	1 / 4	2026-05-27
0.0.50	1 / 4	2026-05-26
0.0.49	1 / 4	2026-05-20
0.0.48	1 / 4	2026-05-11
0.0.47	1 / 4	2026-04-28
0.0.46	1 / 4	2026-04-23
0.0.45	1 / 4	2026-04-15
0.0.44	2 / 4	2026-03-10
0.0.43	2 / 4	2026-03-02
0.0.42	2 / 4	2026-01-06
0.0.41	0 / 3	2025-10-08
0.0.40	0 / 3	2025-06-30
0.0.39	0 / 3	2025-06-30
0.0.38	0 / 2	2025-04-24
0.0.37	0 / 2	2025-04-17
0.0.36	0 / 2	2025-04-17
0.0.35	0 / 2	2025-04-03
0.0.34	0 / 2	2025-03-26
0.0.33	0 / 2	2025-03-26
0.0.32	0 / 2	2025-03-26
0.0.31	0 / 2	2025-03-18
0.0.30	0 / 2	2025-03-10
0.0.29	0 / 2	2025-02-13
0.0.28	0 / 0	2025-01-30
0.0.27	0 / 0	2025-01-15
0.0.26	0 / 0	2025-01-06
0.0.25	2 / 6	2024-12-10
0.0.24	2 / 6	2024-12-10
0.0.23	2 / 4	2024-10-31
0.0.22	2 / 4	2024-10-25
0.0.21	2 / 4	2024-10-22
0.0.20	2 / 4	2024-10-19
0.0.19	2 / 4	2024-10-19
0.0.18	2 / 4	2024-10-19
0.0.17	2 / 4	2024-10-18
0.0.16	2 / 4	2024-10-16
0.0.15	2 / 4	2024-10-08
0.0.14	2 / 4	2024-09-04
0.0.13	2 / 4	2024-08-28
0.0.12	2 / 4	2024-08-27
0.0.11	2 / 4	2024-08-21
0.0.10	2 / 4	2024-07-09
0.0.9	2 / 4	2024-05-16
0.0.8	2 / 4	2024-04-30
0.0.7	2 / 4	2024-04-19
0.0.6	2 / 4	2024-03-22
0.0.4	2 / 4	2024-03-08

v0.0.56

1 finding

LOW No provenance attestation provenance

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

v0.0.55

1 finding

LOW No provenance attestation provenance

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

v0.0.54

1 finding

LOW No provenance attestation provenance

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

v0.0.38

1 finding

LOW No provenance attestation provenance

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

v0.0.37

1 finding

LOW No provenance attestation provenance

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

v0.0.36

1 finding

LOW No provenance attestation provenance

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

v0.0.35

1 finding

LOW No provenance attestation provenance

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

v0.0.34

1 finding

LOW No provenance attestation provenance

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

v0.0.33

1 finding

LOW No provenance attestation provenance

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

v0.0.32

1 finding

LOW No provenance attestation provenance

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

v0.0.31

1 finding

LOW No provenance attestation provenance

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

v0.0.30

2 findings

LOW No provenance attestation provenance

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

INFO Publisher changed: srod → konfeature (on 2025-03-10, known maintainer) provenance

This version was published by a different npm account (konfeature) than the most recent previously approved version (srod) on 2025-03-10, but konfeature is listed as a maintainer on prior approved versions (matched on name). This looks like a manual publish by a known maintainer rather than a publisher change. Recorded as INFO for audit trail.

v0.0.29

2 findings

LOW No provenance attestation provenance

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

INFO Publisher changed: konfeature → srod (on 2025-02-13, known maintainer) provenance

This version was published by a different npm account (srod) than the most recent previously approved version (konfeature) on 2025-02-13, but srod is listed as a maintainer on prior approved versions (matched on name). This looks like a manual publish by a known maintainer rather than a publisher change. Recorded as INFO for audit trail.

v0.0.28

1 finding

LOW No provenance attestation provenance

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

v0.0.27

2 findings

LOW No provenance attestation provenance

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

INFO Publisher changed: srod → konfeature (on 2025-01-15, known maintainer) provenance

This version was published by a different npm account (konfeature) than the most recent previously approved version (srod) on 2025-01-15, but konfeature is listed as a maintainer on prior approved versions (matched on name). This looks like a manual publish by a known maintainer rather than a publisher change. Recorded as INFO for audit trail.

v0.0.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.0.25

1 finding

LOW No provenance attestation provenance

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

v0.0.24

2 findings

LOW No provenance attestation provenance

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

INFO Publisher changed: quentin_nivelais → srod (on 2024-12-10, known maintainer) provenance

This version was published by a different npm account (srod) than the most recent previously approved version (quentin_nivelais) on 2024-12-10, but srod is listed as a maintainer on prior approved versions (matched on name). This looks like a manual publish by a known maintainer rather than a publisher change. Recorded as INFO for audit trail.

v0.0.23

2 findings

HIGH Publisher changed: quentin_nivelais → konfeature (on 2024-10-31) provenance

This version was published by a different npm account than previous versions on 2024-10-31. This could indicate a legitimate maintainer transition or an account compromise.

LOW No provenance attestation provenance

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

v0.0.22

2 findings

HIGH Publisher changed: quentin_nivelais → konfeature (on 2024-10-25) provenance

This version was published by a different npm account than previous versions on 2024-10-25. This could indicate a legitimate maintainer transition or an account compromise.

LOW No provenance attestation provenance

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

v0.0.21

2 findings

HIGH Publisher changed: quentin_nivelais → konfeature (on 2024-10-22) provenance

This version was published by a different npm account than previous versions on 2024-10-22. This could indicate a legitimate maintainer transition or an account compromise.

LOW No provenance attestation provenance

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

v0.0.20

2 findings

HIGH Publisher changed: quentin_nivelais → konfeature (on 2024-10-19) provenance

This version was published by a different npm account than previous versions on 2024-10-19. This could indicate a legitimate maintainer transition or an account compromise.

LOW No provenance attestation provenance

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

v0.0.19

2 findings

HIGH Publisher changed: quentin_nivelais → konfeature (on 2024-10-19) provenance

This version was published by a different npm account than previous versions on 2024-10-19. This could indicate a legitimate maintainer transition or an account compromise.

LOW No provenance attestation provenance

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

v0.0.18

2 findings

HIGH Publisher changed: quentin_nivelais → konfeature (on 2024-10-19) provenance

This version was published by a different npm account than previous versions on 2024-10-19. This could indicate a legitimate maintainer transition or an account compromise.

LOW No provenance attestation provenance

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

v0.0.17

2 findings

HIGH Publisher changed: quentin_nivelais → konfeature (on 2024-10-18) provenance

This version was published by a different npm account than previous versions on 2024-10-18. This could indicate a legitimate maintainer transition or an account compromise.

LOW No provenance attestation provenance

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

v0.0.16

2 findings

HIGH Publisher changed: quentin_nivelais → konfeature (on 2024-10-16) provenance

This version was published by a different npm account than previous versions on 2024-10-16. This could indicate a legitimate maintainer transition or an account compromise.

LOW No provenance attestation provenance

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

v0.0.15

2 findings

HIGH Publisher changed: quentin_nivelais → konfeature (on 2024-10-08) provenance

This version was published by a different npm account than previous versions on 2024-10-08. This could indicate a legitimate maintainer transition or an account compromise.

LOW No provenance attestation provenance

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

v0.0.14

2 findings

HIGH Publisher changed: quentin_nivelais → konfeature (on 2024-09-04) provenance

This version was published by a different npm account than previous versions on 2024-09-04. This could indicate a legitimate maintainer transition or an account compromise.

LOW No provenance attestation provenance

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

v0.0.13

2 findings

HIGH Publisher changed: quentin_nivelais → konfeature (on 2024-08-28) provenance

This version was published by a different npm account than previous versions on 2024-08-28. This could indicate a legitimate maintainer transition or an account compromise.

LOW No provenance attestation provenance

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

v0.0.12

2 findings

HIGH Publisher changed: quentin_nivelais → konfeature (on 2024-08-27) provenance

This version was published by a different npm account than previous versions on 2024-08-27. This could indicate a legitimate maintainer transition or an account compromise.

LOW No provenance attestation provenance

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

v0.0.11

2 findings

HIGH Publisher changed: quentin_nivelais → konfeature (on 2024-08-21) provenance

This version was published by a different npm account than previous versions on 2024-08-21. This could indicate a legitimate maintainer transition or an account compromise.

LOW No provenance attestation provenance

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

v0.0.10

1 finding

LOW No provenance attestation provenance

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

v0.0.9

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. Only ~12% of npm packages have provenance, so this is common but not ideal.

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