@nori-zk/mina-token-bridge Apache-2.0 29 versions

@nori-zk/mina-token-bridge

npm

Nori ethereum state settelment and nETH token bridge zkApp

29

Versions

Apache-2.0

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

jk89kirol

Keywords

mina-zkappmina-zk-appmina-dappzkapp

Accepted risks

Findings the reviewer chose to accept rather than block on.

Source	Rule	Reason	Accepted by	When
phantom-deps	phantom-dep:xstate	AI (phantom-deps): xstate is listed in dependencies and used in config; phantom-dep heuristic false positive.	ai	2026/05/30
npm-metadata	url-dep:o1js	AI (npm-metadata): pkg.pr.new URL for o1js is a documented Mina ecosystem pattern for pre-release builds; stable for this package.	ai	2026/05/30
phantom-deps	phantom-dep:mina-attestations	AI (phantom-deps): Config-referenced dependency; stable pattern for this package.	ai	2026/05/30
phantom-deps	phantom-dep:@nori-zk/o1js-zk-utils	AI (phantom-deps): Same-org scoped dep; monorepo pattern.	ai	2026/05/30
phantom-deps	phantom-dep:@nori-zk/ethprocessor	AI (phantom-deps): Same-org scoped dep; monorepo pattern.	ai	2026/05/30
phantom-deps	phantom-dep:autrace	AI (phantom-deps): Config-referenced dependency; stable pattern for this package.	ai	2026/05/30
provenance	no-provenance	AI (provenance): Established package with clean history; lack of provenance is common and not a risk signal here.	ai	2026/05/29

Versions (showing 29 of 29)

Version	Deps	Published
0.3.34	7 / 18	2026-05-20
0.3.33	7 / 18	2026-04-29
0.3.32	9 / 18	2026-04-20
0.2.26	9 / 18	2026-04-17
0.2.25	9 / 18	2026-04-15
0.2.24	9 / 18	2026-02-16
0.2.23	8 / 19	2025-11-26
0.2.22	8 / 19	2025-10-14
0.2.21	8 / 19	2025-10-10
0.2.20	8 / 19	2025-09-27
0.2.19	8 / 19	2025-09-23
0.2.18	8 / 19	2025-09-23
0.2.17	8 / 19	2025-09-23
0.2.16	8 / 19	2025-09-15
0.2.15	8 / 19	2025-08-20
0.2.14	8 / 19	2025-08-19
0.2.12	7 / 19	2025-08-15
0.2.11	7 / 19	2025-08-15
0.2.10	7 / 19	2025-08-14
0.2.9	7 / 19	2025-08-14
0.2.8	7 / 19	2025-08-14
0.2.7	7 / 19	2025-08-14
0.2.6	7 / 19	2025-08-14
0.2.5	7 / 19	2025-08-14
0.2.4	7 / 19	2025-08-12
0.2.3	7 / 19	2025-08-07
0.2.2	7 / 18	2025-08-05
0.1.2	5 / 18	2025-07-24
0.0.1	4 / 14	2025-07-08

v0.3.34

1 finding

LOW No provenance attestation provenance

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

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

v0.3.32

1 finding

LOW No provenance attestation provenance

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

v0.2.26

1 finding

LOW No provenance attestation provenance

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

v0.2.25

1 finding

LOW No provenance attestation provenance

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

v0.2.24

1 finding

LOW No provenance attestation provenance

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

v0.2.23

1 finding

LOW No provenance attestation provenance

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

v0.2.22

1 finding

LOW No provenance attestation provenance

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

v0.2.21

1 finding

LOW No provenance attestation provenance

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

v0.2.20

1 finding

LOW No provenance attestation provenance

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

v0.2.19

1 finding

LOW No provenance attestation provenance

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

v0.2.18

1 finding

LOW No provenance attestation provenance

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

v0.2.17

1 finding

LOW No provenance attestation provenance

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

v0.2.16

1 finding

LOW No provenance attestation provenance

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

v0.2.15

1 finding

LOW No provenance attestation provenance

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

v0.2.14

1 finding

LOW No provenance attestation provenance

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

v0.2.12

1 finding

LOW No provenance attestation provenance

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

v0.2.11

1 finding

LOW No provenance attestation provenance

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

v0.2.10

1 finding

LOW No provenance attestation provenance

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

v0.2.9

1 finding

LOW No provenance attestation provenance

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

v0.2.8

1 finding

LOW No provenance attestation provenance

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

v0.2.7

1 finding

LOW No provenance attestation provenance

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

v0.2.6

1 finding

LOW No provenance attestation provenance

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

v0.2.5

1 finding

LOW No provenance attestation provenance

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

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

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

v0.2.2

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

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