← Home

@msafe/aptos-aip62-wallet

npm Homepage

MSafe Aptos Wallet

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

msafe-adminhydee_ch

Accepted risks

Findings the reviewer chose to accept rather than block on.

SourceRuleReasonAccepted byWhen
maintainer-change maintainer-takeover AI (maintainer-change): Publisher is a known maintainer by email match; long-lived version, no takeover behavior. ai
maintainer-change maintainer-removed AI (maintainer-change): Same known-maintainer explanation applies. ai
maintainer-change maintainer-added AI (maintainer-change): Same known-maintainer explanation applies. ai
dependencies unvetted-dep:bellhop-iframe AI (dependencies): Legitimate iframe-messaging lib fitting wallet-adapter's cross-window communication needs. ai
phantom-deps phantom-dep:graphql AI (phantom-deps): Declared as runtime dep but used indirectly via graphql-request; stable false positive for this package. ai
phantom-deps phantom-dep:@telegram-apps/bridge AI (phantom-deps): Telegram bridge likely used conditionally for Telegram wallet context; stable false positive. ai
phantom-deps phantom-dep:@mizuwallet-sdk/core AI (phantom-deps): May be used indirectly or conditionally; stable false positive for this package. ai
phantom-deps phantom-dep:graphql-request AI (phantom-deps): Likely bundled or used transitively; stable false positive for this package. ai

Versions (showing 16 of 16)

Version Deps Published
1.0.18 4 / 7
1.0.17 4 / 7
1.0.16 4 / 7
1.0.13 4 / 7
1.0.12 4 / 7
1.0.11 4 / 7
1.0.10 4 / 7
1.0.9 4 / 7
1.0.8 5 / 7
1.0.7 4 / 7
1.0.6 4 / 7
1.0.5 4 / 7
1.0.4 4 / 7
1.0.3 4 / 7
1.0.2 4 / 7
1.0.1 0 / 7

v1.0.17

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: msafe → msafe-admin (on 2025-04-05, known maintainer) provenance

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

v1.0.16

1 finding
LOW No provenance attestation provenance

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

v1.0.13

1 finding
LOW No provenance attestation provenance

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

v1.0.12

1 finding
LOW No provenance attestation provenance

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

v1.0.11

1 finding
LOW No provenance attestation provenance

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

v1.0.10

1 finding
LOW No provenance attestation provenance

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

v1.0.9

1 finding
LOW No provenance attestation provenance

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

v1.0.8

1 finding
LOW No provenance attestation provenance

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

v1.0.7

1 finding
LOW No provenance attestation provenance

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

v1.0.6

1 finding
LOW No provenance attestation provenance

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

v1.0.5

1 finding
LOW No provenance attestation provenance

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

v1.0.4

1 finding
LOW No provenance attestation provenance

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

v1.0.3

1 finding
LOW No provenance attestation provenance

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

v1.0.2

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