← Home

@vultisig/core-mpc

npm Repository

MPC, keysign, and vault types shared across Vultisig clients

35
Versions
MIT
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

jpthorrcoderdevbornslippynuxx

Accepted risks

Findings the reviewer chose to accept rather than block on.

SourceRuleReasonAccepted byWhen
source-diff encoded-string-file:dist/types/vultisig/keygen/v1/keygen_message_pb.js AI (source-diff): Base64 protobuf file descriptor from protoc-gen-es codegen; stable false positive for this package. ai
source-diff encoded-string-file:dist/types/vultisig/keygen/v1/reshare_message_pb.js AI (source-diff): Base64 protobuf file descriptor from protoc-gen-es codegen; stable false positive for this package. ai
source-diff encoded-string-file:dist/types/vultisig/keygen/v1/single_keygen_message_pb.js AI (source-diff): Base64 is a protobuf file descriptor passed to fileDesc() by protoc-gen-es codegen; stable false positive for this package. ai
source-diff encoded-string-file:dist/types/vultisig/keysign/v1/wasm_execute_contract_payload_pb.js AI (source-diff): Base64 string is a protoc-gen-es generated protobuf file descriptor; stable pattern for this package's generated types. ai
phantom-deps phantom-dep:@mysten/sui AI (phantom-deps): Config-file reference in monorepo; stable pattern for this package. ai
phantom-deps phantom-dep:@vultisig/lib-schnorr AI (phantom-deps): Same-org monorepo dependency; stable pattern for this package. ai
phantom-deps phantom-dep:@vultisig/lib-dkls AI (phantom-deps): Same-org monorepo dependency; stable pattern for this package. ai

Versions (showing 35 of 35)

Version Deps Published
1.2.19 20 / 0
1.2.18 20 / 0
1.2.17 20 / 0
1.2.16 20 / 0
1.2.15 20 / 0
1.2.14 20 / 0
1.2.13 20 / 0
1.2.12 20 / 0
1.2.11 20 / 0
1.2.10 20 / 0
1.2.9 20 / 0
1.2.8 20 / 0
1.2.7 20 / 0
1.2.6 20 / 0
1.2.5 20 / 0
1.2.4 20 / 0
1.2.3 19 / 0
1.2.2 19 / 0
1.2.1 19 / 0
1.2.0 19 / 0
1.1.9 19 / 0
1.1.8 19 / 0
1.1.7 19 / 0
1.1.6 19 / 0
1.1.5 19 / 0
1.1.4 19 / 0
1.1.3 19 / 0
1.1.2 19 / 0
1.1.1 19 / 0
1.1.0 19 / 0
1.0.2 19 / 0
1.0.1 18 / 0
1.0.0 18 / 0
0.10.0 18 / 0
0.9.0 18 / 0

v1.2.19

1 finding
LOW No provenance attestation provenance

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

v1.2.18

1 finding
LOW No provenance attestation provenance

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

v1.2.17

1 finding
LOW No provenance attestation provenance

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

v1.2.16

1 finding
LOW No provenance attestation provenance

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

v1.2.15

1 finding
LOW No provenance attestation provenance

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

v1.2.14

1 finding
LOW No provenance attestation provenance

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

v1.2.13

1 finding
LOW No provenance attestation provenance

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

v1.2.12

1 finding
LOW No provenance attestation provenance

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

v1.2.11

1 finding
LOW No provenance attestation provenance

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

v1.2.10

3 findings
HIGH Long encoded string in modified file: dist/types/vultisig/keygen/v1/keygen_message_pb.js source-diff

Modified file contains 1 long encoded string(s) (200+ chars). These are commonly used to hide malicious payloads.

HIGH Long encoded string in modified file: dist/types/vultisig/keygen/v1/reshare_message_pb.js source-diff

Modified file contains 1 long encoded string(s) (200+ chars). These are commonly used to hide malicious payloads.

LOW No provenance attestation provenance

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

v1.2.9

3 findings
HIGH Long encoded string in modified file: dist/types/vultisig/keygen/v1/keygen_message_pb.js source-diff

Modified file contains 1 long encoded string(s) (200+ chars). These are commonly used to hide malicious payloads.

HIGH Long encoded string in modified file: dist/types/vultisig/keygen/v1/reshare_message_pb.js source-diff

Modified file contains 1 long encoded string(s) (200+ chars). These are commonly used to hide malicious payloads.

LOW No provenance attestation provenance

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

v1.2.8

1 finding
LOW No provenance attestation provenance

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

v1.2.7

1 finding
LOW No provenance attestation provenance

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

v1.2.6

1 finding
LOW No provenance attestation provenance

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

v1.2.5

1 finding
LOW No provenance attestation provenance

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

v1.2.4

1 finding
LOW No provenance attestation provenance

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

v1.2.3

1 finding
LOW No provenance attestation provenance

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

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

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

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

v1.1.9

1 finding
LOW No provenance attestation provenance

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

v1.1.8

1 finding
LOW No provenance attestation provenance

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

v1.1.7

1 finding
LOW No provenance attestation provenance

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

v1.1.6

1 finding
LOW No provenance attestation provenance

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

v1.1.5

1 finding
LOW No provenance attestation provenance

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

v1.1.4

1 finding
LOW No provenance attestation provenance

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

v1.1.3

1 finding
LOW No provenance attestation provenance

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

v1.1.2

1 finding
LOW No provenance attestation provenance

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

v1.1.1

2 findings
HIGH Long encoded string in modified file: dist/types/vultisig/keygen/v1/single_keygen_message_pb.js source-diff

Modified file contains 1 long encoded string(s) (200+ chars). These are commonly used to hide malicious payloads.

LOW No provenance attestation provenance

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

v1.1.0

2 findings
HIGH Long encoded string in modified file: dist/types/vultisig/keygen/v1/single_keygen_message_pb.js source-diff

Modified file contains 1 long encoded string(s) (200+ chars). These are commonly used to hide malicious payloads.

LOW No provenance attestation provenance

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

v1.0.2

2 findings
HIGH Long encoded string in modified file: dist/types/vultisig/keysign/v1/wasm_execute_contract_payload_pb.js source-diff

Modified file contains 1 long encoded string(s) (200+ chars). These are commonly used to hide malicious payloads.

LOW No provenance attestation provenance

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

v1.0.1

1 finding
LOW No provenance attestation provenance

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

v1.0.0

1 finding
LOW No provenance attestation provenance

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

v0.10.0

1 finding
LOW No provenance attestation provenance

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

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