filsnap 0.3.2
Filsnap - Metamask snap to interact with Filecoin dapps.
filsnap@0.3.2 was published on 2023-07-24. Its manifest declares 6 runtime dependencies and 0 peer requirements. Type declarations are bundled according to the package metadata. No Node.js engine requirement is declared in this manifest.
All filsnap versions · Permanent reference to 0.3.2 · View npm registry JSON · Latest release
Package specifications
| Version | 0.3.2 |
|---|---|
| License declaration | (Apache-2.0 AND MIT) |
| Published | 2023-07-24T18:09:25.244Z |
| Node.js requirement | Not declared |
| Type declarations | Bundled declarations |
| Runtime dependency count | 6 |
| Peer requirement count | 0 |
| Optional dependency count | 0 |
| Minified size | Measurement not available yet |
| Minified + gzip | Measurement not available yet |
| Unpacked distribution size | 647.84 KiB |
| Published file count | 130 |
| Package type | module |
| ES module entry | Not declared |
| Default entry | dist/src/index.js |
| Side effects declaration | Not declared |
| Direct advisories | 0 |
| Resolved graph dependencies | 46 |
| Repository stars | Unknown |
| Repository forks | Unknown |
Install filsnap 0.3.2
npm install filsnap@0.3.2 pnpm add filsnap@0.3.2 yarn add filsnap@0.3.2
Runtime dependencies
- zod ^3.21.4
- iso-base ^1.1.1
- iso-filecoin ^2.0.1
- merge-options ^3.0.4
- @metamask/key-tree ^9.0.0
- @metamask/snaps-ui ^0.32.2
Peer requirements
- None declared
Optional dependencies
- None declared
Resolved dependency graph
This deps.dev graph describes a generic 64-bit Linux environment, not your application lockfile.
- @metamask/key-tree@9.1.2 — direct
- @metamask/snaps-ui@0.32.2 — direct
- iso-base@1.1.2 — direct
- iso-filecoin@2.1.0 — direct
- merge-options@3.0.4 — direct
- zod@3.25.76 — direct
- @metamask/scure-bip39@2.1.1 — indirect
- @metamask/utils@9.3.0 — indirect
- @noble/curves@1.9.7 — indirect
- @noble/hashes@1.8.0 — indirect
- @scure/base@1.2.6 — indirect
- @metamask/utils@5.0.2 — indirect
- superstruct@1.0.4 — indirect
- base-x@4.0.1 — indirect
- bigint-mod-arith@3.3.1 — indirect
- @ipld/dag-cbor@9.2.7 — indirect
- @scure/bip32@1.4.0 — indirect
- @scure/bip39@1.3.0 — indirect
- bignumber.js@9.3.1 — indirect
- is-plain-obj@2.1.0 — indirect
- @noble/hashes@1.3.3 — indirect
- @scure/base@1.1.9 — indirect
- @ethereumjs/tx@4.2.0 — indirect
- @metamask/superstruct@3.4.1 — indirect
- @types/debug@4.1.13 — indirect
- debug@4.4.3 — indirect
- pony-cause@2.1.11 — indirect
- semver@7.8.6 — indirect
- uuid@9.0.1 — indirect
- cborg@5.1.11 — indirect
- multiformats@13.4.2 — indirect
- @noble/curves@1.4.2 — indirect
- @noble/hashes@1.4.0 — indirect
- @scure/base@1.1.9 — indirect
- @noble/hashes@1.4.0 — indirect
- @scure/base@1.1.9 — indirect
- @ethereumjs/common@3.2.0 — indirect
- @ethereumjs/rlp@4.0.1 — indirect
- @ethereumjs/util@8.1.0 — indirect
- ethereum-cryptography@2.2.1 — indirect
- @types/ms@2.1.0 — indirect
- ms@2.1.3 — indirect
- crc-32@1.2.2 — indirect
- micro-ftch@0.3.1 — indirect
- @noble/curves@1.4.2 — indirect
- @noble/hashes@1.4.0 — indirect
How to interpret the specifications
Bundlephobia measurements use its standard package build and may exclude peer dependencies. Unpacked npm distribution size includes shipped files and is a different measurement. Module declarations do not prove tree-shaking or runtime compatibility.
Advisories apply to this package version directly; transitive dependencies need separate inspection. Repository signals describe the whole repository and are current observations, including on historical-version pages.
Evidence and freshness
- Readable npm registry JSON — retrieved 2026-11-06T23:00:45.358Z
- https://api.deps.dev/v3/systems/npm/packages/filsnap/versions/0.3.2 — retrieved 2026-11-06T23:00:45.437Z
- https://api.deps.dev/v3/systems/npm/packages/filsnap/versions/0.3.2:dependencies — retrieved 2026-11-06T23:00:45.537Z