← Home

@bitgo/sdk-coin-zeta

npm Repository Homepage

BitGo SDK coin library for Zeta

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

SourceRuleReasonAccepted byWhen
source-diff obfuscated-file:dist/test/unit/zeta.js AI (source-diff): Compiled test file; long lines from inlined test fixture data, not obfuscation. ai
maintainer-change maintainer-takeover AI (maintainer-change): BitGo org-wide CI migration to GitHub Actions/bitgobot; SLSA provenance confirms legitimate CI publish. ai
source-diff obfuscated-file:dist/test/unit/keyPair.js AI (source-diff): TypeScript-compiled test file; long lines from inlined fixture data, not obfuscation. ai
source-diff obfuscated-file:dist/test/unit/transactionBuilder/StakingActivateBuilder.js AI (source-diff): TypeScript-compiled test file; standard tsc boilerplate with long fixture lines. ai
source-diff obfuscated-file:dist/test/unit/transactionBuilder/StakingDeactivateBuilder.js AI (source-diff): TypeScript-compiled test file; standard tsc boilerplate with long fixture lines. ai
source-diff obfuscated-file:dist/test/unit/transactionBuilder/StakingRedelegateBuilder.js AI (source-diff): TypeScript-compiled test file; standard tsc boilerplate with long fixture lines. ai
source-diff obfuscated-file:dist/test/unit/transactionBuilder/StakingWithdrawRewardsBuilder.js AI (source-diff): TypeScript-compiled test file; standard tsc boilerplate with long fixture lines. ai
source-diff obfuscated-file:dist/test/unit/transaction.js AI (source-diff): TypeScript-compiled test file; standard tsc boilerplate with long fixture lines. ai
source-diff obfuscated-file:dist/test/unit/transactionBuilder/transactionBuilder.js AI (source-diff): TypeScript-compiled test file; standard tsc boilerplate with long fixture lines. ai
source-diff obfuscated-file:dist/test/unit/transactionBuilder/transferBuilder.js AI (source-diff): TypeScript-compiled test file; standard tsc boilerplate with long fixture lines. ai
source-diff obfuscated-file:dist/test/unit/utils.js AI (source-diff): TypeScript-compiled test file; standard tsc boilerplate with long fixture lines. ai
source-diff obfuscated-file:dist/test/resources/zeta.js AI (source-diff): Compiled test resource file; long lines from inlined test fixture data, not obfuscation. ai
provenance publisher-changed AI (provenance): zahin-mohammad is an established BitGo publisher (54 approved, 0 rejected); transition appears legitimate within the org. ai
phantom-deps phantom-dep:@cosmjs/encoding AI (phantom-deps): Cosmos SDK utility used via config/re-export; stable false positive for this Cosmos-based coin package. ai
phantom-deps phantom-dep:@bitgo/sdk-lib-mpc AI (phantom-deps): Same-org sibling dep; phantom-dep heuristic fires on transitive/re-exported usage, stable false positive for this package. ai

Versions (showing 98 of 98)

Version Deps Published
3.7.26 8 / 3
3.7.25 8 / 3
3.7.23 8 / 3
3.7.22 8 / 3
3.7.21 8 / 3
3.7.20 8 / 3
3.7.19 8 / 3
3.7.18 8 / 3
3.7.17 8 / 3
3.7.16 8 / 3
3.7.15 8 / 3
3.7.14 8 / 3
3.7.13 8 / 3
3.7.12 8 / 3
3.7.11 8 / 3
3.7.10 8 / 3
3.7.9 8 / 3
3.7.8 8 / 3
3.7.7 8 / 3
3.7.6 8 / 3
3.7.3 8 / 3
3.5.8 8 / 3
3.5.2 8 / 3
3.5.1 8 / 3
3.5.0 8 / 3
3.4.2 8 / 3
3.4.1 8 / 3
3.4.0 8 / 3
3.3.1 8 / 3
3.3.0 8 / 3
3.2.3 8 / 3
3.2.2 8 / 3
3.2.1 8 / 3
3.2.0 8 / 3
3.1.11 8 / 3
3.1.10 8 / 3
3.1.9 8 / 3
3.1.8 8 / 3
3.1.7 8 / 3
3.1.6 8 / 3
3.1.5 8 / 3
3.1.4 8 / 3
3.1.3 8 / 3
3.1.2 8 / 3
3.1.1 8 / 3
3.1.0 8 / 3
3.0.52 8 / 3
3.0.51 8 / 3
3.0.50 8 / 3
3.0.49 8 / 3
3.0.48 8 / 3
3.0.47 8 / 3
3.0.46 8 / 3
3.0.45 8 / 3
3.0.44 8 / 3
3.0.43 8 / 3
3.0.42 8 / 3
3.0.41 8 / 3
3.0.40 8 / 3
3.0.39 8 / 3
3.0.38 8 / 3
3.0.37 8 / 3
3.0.36 8 / 3
3.0.35 8 / 3
3.0.34 8 / 3
3.0.33 8 / 3
3.0.32 8 / 3
3.0.31 8 / 3
3.0.30 8 / 3
3.0.29 8 / 3
3.0.28 8 / 3
3.0.27 8 / 3
3.0.26 8 / 3
3.0.25 8 / 3
3.0.24 8 / 3
3.0.23 8 / 3
3.0.21 8 / 3
3.0.20 8 / 3
3.0.19 8 / 3
3.0.18 8 / 3
3.0.17 8 / 3
3.0.16 8 / 3
3.0.15 8 / 3
3.0.14 8 / 3
3.0.13 8 / 3
3.0.12 8 / 4
3.0.11 8 / 4
3.0.10 8 / 4
3.0.9 8 / 4
3.0.8 8 / 4
3.0.7 8 / 4
3.0.6 8 / 4
3.0.5 8 / 4
3.0.4 8 / 4
3.0.3 8 / 4
3.0.2 8 / 4
3.0.1 8 / 4
3.0.0 8 / 4

v3.7.26

1 finding
INFO Has SLSA provenance attestation provenance

Published via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.

v3.7.25

1 finding
INFO Has SLSA provenance attestation provenance

Published via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.

v3.7.23

1 finding
INFO Has SLSA provenance attestation provenance

Published via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.

v3.7.22

1 finding
INFO Has SLSA provenance attestation provenance

Published via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.

v3.7.21

1 finding
INFO Has SLSA provenance attestation provenance

Published via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.

v3.7.20

1 finding
INFO Has SLSA provenance attestation provenance

Published via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.

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

v3.0.45

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.

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

v3.0.0

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.