@bitgo/sdk-coin-zketh MIT 53 versions

@bitgo/sdk-coin-zketh

npm Repository Homepage

BitGo SDK coin library for zkSync

53

Versions

MIT

License

No

Install Scripts

Verified

Provenance

Supply chain provenance

Status for the latest visible version.

SLSA provenance attestation npm registry signatures gitHead linked

Maintainers

louib-bitgobitgobot

Accepted risks

Findings the reviewer chose to accept rather than block on.

Source	Rule	Reason	Accepted by	When
provenance	publisher-changed	AI (provenance): Publisher changed to GitHub Actions with SLSA provenance attestation; consistent with BitGo CI/CD migration.	ai	2026/05/17
source-diff	obfuscated-file:dist/test/resources.js	AI (source-diff): Long lines are hex-encoded Ethereum transaction test data, not obfuscated malware; stable pattern for BitGo SDK test fixtures.	ai	2026/05/17
source-diff	obfuscated-file:dist/test/unit/transactionBuilder/send.js	AI (source-diff): Standard TypeScript-compiled test file with long hex test vectors; not obfuscated.	ai	2026/05/17
source-diff	obfuscated-file:dist/test/unit/transaction.js	AI (source-diff): Standard TypeScript-compiled test file; long lines are test data, not obfuscation.	ai	2026/05/17
source-diff	obfuscated-file:dist/test/unit/transferBuilder.js	AI (source-diff): Standard TypeScript-compiled test file; long lines are test data, not obfuscation.	ai	2026/05/17
source-diff	obfuscated-file:dist/test/unit/zketh.js	AI (source-diff): Standard TypeScript-compiled test file; long lines are test data, not obfuscation.	ai	2026/05/17
source-diff	obfuscated-file:dist/test/unit/zkethToken.js	AI (source-diff): Standard TypeScript-compiled test file with base64 sourcemap; not obfuscated malware.	ai	2026/05/17
source-diff	obfuscated-file:dist/test/resources.d.ts	AI (source-diff): TypeScript declaration file with long hex-encoded transaction constant; test data, not obfuscation.	ai	2026/05/17
maintainer-change	maintainer-takeover	AI (maintainer-change): BitGo org-wide shift to bot-based publishing (bitgobot) with SLSA provenance; not a hijack.	ai	2026/05/17
source-diff	obfuscated-file:dist/test/fixtures/zketh.js	AI (source-diff): Test fixture file with long hex response data; not obfuscated malware.	ai	2026/05/17
phantom-deps	phantom-dep:@bitgo/secp256k1	AI (phantom-deps): Same-org dependency within BitGo monorepo; stable false positive for this package.	ai	2026/05/17

Versions (showing 53 of 153)

Version	Deps	Published
2.0.56	5 / 3	2025-02-05
2.0.55	5 / 3	2025-01-28
2.0.54	5 / 3	2025-01-23
2.0.52	5 / 3	2025-01-20
2.0.51	5 / 3	2025-01-15
2.0.50	5 / 3	2025-01-09
2.0.49	5 / 3	2025-01-03
2.0.48	5 / 3	2024-12-24
2.0.47	5 / 3	2024-12-19
2.0.46	5 / 3	2024-12-17
2.0.44	5 / 3	2024-12-12
2.0.43	5 / 3	2024-12-11
2.0.42	5 / 3	2024-12-03
2.0.41	5 / 3	2024-11-26
2.0.40	5 / 3	2024-11-21
2.0.39	5 / 3	2024-11-19
2.0.38	5 / 3	2024-11-14
2.0.37	5 / 3	2024-11-08
2.0.36	5 / 3	2024-11-07
2.0.35	5 / 3	2024-11-01
2.0.34	5 / 3	2024-10-22
2.0.33	5 / 3	2024-10-15
2.0.32	5 / 3	2024-10-08
2.0.31	5 / 3	2024-10-04
2.0.30	5 / 3	2024-09-24
2.0.29	5 / 3	2024-09-19
2.0.28	5 / 3	2024-09-16
2.0.27	5 / 3	2024-09-10
2.0.26	5 / 3	2024-09-03
2.0.25	5 / 3	2024-08-29
2.0.24	5 / 3	2024-08-27
2.0.23	5 / 3	2024-08-20
2.0.22	5 / 3	2024-08-13
2.0.21	5 / 3	2024-08-07
2.0.20	5 / 3	2024-07-30
2.0.19	5 / 3	2024-07-24
2.0.18	5 / 3	2024-07-16
2.0.17	5 / 3	2024-07-04
2.0.16	5 / 3	2024-07-02
2.0.15	5 / 3	2024-06-27
2.0.14	5 / 3	2024-06-26
2.0.13	5 / 3	2024-06-21
2.0.12	5 / 3	2024-06-20
2.0.11	5 / 3	2024-06-14
2.0.10	5 / 3	2024-06-11
2.0.9	5 / 3	2024-06-05
2.0.8	5 / 3	2024-05-31
2.0.7	5 / 3	2024-05-28
2.0.6	5 / 3	2024-05-22
2.0.5	5 / 3	2024-05-17
2.0.4	5 / 3	2024-05-13
2.0.3	5 / 3	2024-05-08
2.0.2	5 / 3	2024-05-01

v2.0.56

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.

v2.0.55

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.

v2.0.54

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.

v2.0.52

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.

v2.0.51

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.

v2.0.50

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.

v2.0.49

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.

v2.0.48

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.

v2.0.47

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.

v2.0.46

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.

v2.0.44

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.

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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