@keyv/serialize 1.0.1
Serialization for keyv
@keyv/serialize@1.0.1 was published on 2024-08-21. Its manifest declares 1 runtime dependency and 0 peer requirements. Type declarations are bundled according to the package metadata. No Node.js engine requirement is declared in this manifest.
All @keyv/serialize versions · Permanent reference to 1.0.1 · Latest release
Package specifications
| Version | 1.0.1 |
|---|---|
| License declaration | MIT |
| Published | 2024-08-21T23:37:56.188Z |
| Node.js requirement | Not declared |
| Type declarations | Bundled declarations |
| Runtime dependency count | 1 |
| Peer requirement count | 0 |
| Optional dependency count | 0 |
| Minified size | Measurement not available yet |
| Minified + gzip | Measurement not available yet |
| Unpacked distribution size | 8.32 KiB |
| Published file count | 9 |
| Package type | module |
| ES module entry | dist/index.js |
| Default entry | dist/index.cjs |
| Side effects declaration | Not declared |
| Direct advisories | 0 |
| Resolved graph dependencies | 3 |
| Repository stars | 3201 |
| Repository forks | 203 |
Install @keyv/serialize 1.0.1
npm install @keyv/serialize@1.0.1 pnpm add @keyv/serialize@1.0.1 yarn add @keyv/serialize@1.0.1
Runtime dependencies
- buffer ^6.0.3
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.
- base64-js@1.5.1 — indirect
- buffer@6.0.3 — direct
- ieee754@1.2.1 — 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.
OpenSSF repository checks
Provider assessment: 2026-08-24T00:00:00Z. These are repository checks, not a jsL maintenance score.
| Security-Policy | 10/10 — security policy file detected |
|---|---|
| Dangerous-Workflow | 10/10 — no dangerous workflow patterns detected |
| Maintained | 10/10 — 30 commit(s) and 5 issue activity found in the last 90 days -- score normalized to 10 |
| Code-Review | 0/10 — Found 0/30 approved changesets -- score normalized to 0 |
| Token-Permissions | 10/10 — GitHub workflow tokens follow principle of least privilege |
| Binary-Artifacts | 10/10 — no binaries found in the repo |
| CII-Best-Practices | 0/10 — no effort to earn an OpenSSF best practices badge detected |
| License | 9/10 — license file detected |
| Pinned-Dependencies | 9/10 — dependency not pinned by hash detected -- score normalized to 9 |
| Fuzzing | 0/10 — project is not fuzzed |
| Packaging | 10/10 — packaging workflow detected |
| Branch-Protection | 3/10 — branch protection is not maximal on development and all release branches |
Evidence and freshness
- https://registry.npmjs.org/%40keyv%2Fserialize/1.0.1 — retrieved 2026-10-29T10:25:03.508Z
- https://api.deps.dev/v3/projects/github.com%2Fjaredwray%2Fkeyv — retrieved 2026-10-29T05:59:39.174Z
- https://api.deps.dev/v3/systems/npm/packages/%40keyv%2Fserialize/versions/1.0.1:dependencies — retrieved 2026-10-29T10:25:04.159Z
- https://api.deps.dev/v3/systems/npm/packages/%40keyv%2Fserialize/versions/1.0.1 — retrieved 2026-10-29T10:25:04.166Z