sm-crypto

sm-crypto

sm-crypto@0.5.8 was published on 2026-10-26. Its manifest declares 1 runtime dependency and 0 peer requirements. Bundled type declarations are not declared in the inspected metadata. No Node.js engine requirement is declared in this manifest.

All sm-crypto versions · Permanent reference to 0.5.8

Package specifications

Version0.5.8
License declarationMIT
Published2026-10-26T05:00:49.704Z
Node.js requirementNot declared
Type declarationsNot declared
Runtime dependency count1
Peer requirement count0
Optional dependency count0
Minified sizeMeasurement not available yet
Minified + gzipMeasurement not available yet
Unpacked distribution size111.61 KiB
Published file count20
Package typeNot declared
ES module entryNot declared
Default entrysrc/index.js
Side effects declarationNot declared
Direct advisories0
Resolved graph dependencies1
Repository stars1163
Repository forks287

Install sm-crypto 0.5.8

npm install sm-crypto@0.5.8
pnpm add sm-crypto@0.5.8
yarn add sm-crypto@0.5.8

Runtime dependencies

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.

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.

OpenSSF repository checks

Provider assessment: 2026-08-24T00:00:00Z. These are repository checks, not a jsL maintenance score.

Code-Review0/10 — Found 2/28 approved changesets -- score normalized to 0
Security-Policy9/10 — security policy file detected
Maintained10/10 — 14 commit(s) and 1 issue activity found in the last 90 days -- score normalized to 10
Binary-Artifacts10/10 — no binaries found in the repo
CII-Best-Practices0/10 — no effort to earn an OpenSSF best practices badge detected
Fuzzing0/10 — project is not fuzzed
License10/10 — license file detected
Branch-Protection0/10 — branch protection not enabled on development/release branches
SAST0/10 — SAST tool is not run on all commits -- score normalized to 0

Evidence and freshness