Gathering detailed insights and metrics for jest-serializer
Gathering detailed insights and metrics for jest-serializer
Installations
npm install jest-serializerDeveloper Guide
BETA
Typescript
Yes
Module System
CommonJS, ESM
Min. Node Version
^12.13.0 || ^14.15.0 || ^16.13.0 || >=17.0.0
Node Version
16.14.2
NPM Version
lerna/4.0.0/node@v16.14.2+x64 (darwin)
Releases
208
Languages
5
TypeScript
JavaScript
CSS
Shell
Handlebars
TypeScript (79.11%)
JavaScript (20.31%)
CSS (0.56%)
Shell (0.01%)
Handlebars (0.01%)
Developer
Download Statistics
Total Downloads
0
Last Day
0
Last Week
0
Last Month
0
Last Year
0
GitHub Statistics
MIT License
44,885 Stars
7,448 Commits
6,571 Forks
561 Watchers
5 Branches
1,575 Contributors
Updated on Jul 12, 2025
Maintainers
5
Package Meta Information
Latest Version
28.0.0
Package Id
jest-serializer@28.0.0
Unpacked Size
6.50 kB
Size
2.81 kB
File Count
5
NPM Version
lerna/4.0.0/node@v16.14.2+x64 (darwin)
Node Version
16.14.2
Total Downloads
Cumulative downloads
Total Downloads
NaN
Last Day
0%
NaN
Compared to previous day
Last Week
0%
NaN
Compared to previous week
Last Month
0%
NaN
Compared to previous month
Last Year
0%
NaN
Compared to previous year
Weekly Downloads
Monthly Downloads
Yearly Downloads
Dependencies
2
Dev Dependencies
1
jest-serializer
DEPRECATED: Use
v8APIs directly: https://nodejs.org/api/v8.html#serialization-api
Module for serializing and deserializing object into memory and disk. The Node core v8 implementations are used. This seriializer have the advantage of being able to serialize Map, Set, undefined, NaN, etc..
Install
1$ yarn add jest-serializer
API
Three kinds of API groups are exposed:
In-memory serialization: serialize and deserialize
This set of functions take or return a Buffer. All the process happens in memory. This is useful when willing to transfer over HTTP, TCP or via UNIX pipes.
1import {deserialize, serialize} from 'jest-serializer'; 2 3const myObject = { 4 foo: 'bar', 5 baz: [0, true, '2', [], {}], 6}; 7 8const buffer = serialize(myObject); 9const myCopyObject = deserialize(buffer);
Synchronous persistent filesystem: readFileSync and writeFileSync
This set of functions allow to send to disk a serialization result and retrieve it back, in a synchronous way. It mimics the fs API so it looks familiar.
1import {readFileSync, writeFileSync} from 'jest-serializer'; 2 3const myObject = { 4 foo: 'bar', 5 baz: [0, true, '2', [], {}], 6}; 7 8const myFile = '/tmp/obj'; 9 10writeFileSync(myFile, myObject); 11const myCopyObject = readFileSync(myFile);
No vulnerabilities found.
Reason
30 commit(s) and 6 issue activity found in the last 90 days -- score normalized to 10
Reason
no dangerous workflow patterns detected
Reason
security policy file detected
Details
- Info: security policy file detected: SECURITY.md:1
- Info: Found linked content: SECURITY.md:1
- Info: Found disclosure, vulnerability, and/or timelines in security policy: SECURITY.md:1
- Info: Found text in security policy: SECURITY.md:1
Reason
license file detected
Details
- Info: project has a license file: LICENSE:0
- Info: FSF or OSI recognized license: MIT License: LICENSE:0
Reason
all dependencies are pinned
Details
- Info: 26 out of 26 GitHub-owned GitHubAction dependencies pinned
- Info: 13 out of 13 third-party GitHubAction dependencies pinned
Reason
project is fuzzed
Details
- Info: TypeScriptPropertyBasedTesting integration found: packages/diff-sequences/src/__tests__/index.property.test.ts:9
- Info: TypeScriptPropertyBasedTesting integration found: packages/expect/src/__tests__/__arbitraries__/sharedSettings.ts:9
- Info: TypeScriptPropertyBasedTesting integration found: packages/expect/src/__tests__/matchers-toContain.property.test.ts:9
- Info: TypeScriptPropertyBasedTesting integration found: packages/expect/src/__tests__/matchers-toContainEqual.property.test.ts:9
- Info: TypeScriptPropertyBasedTesting integration found: packages/expect/src/__tests__/matchers-toEqual.property.test.ts:9
- Info: TypeScriptPropertyBasedTesting integration found: packages/expect/src/__tests__/matchers-toStrictEqual.property.test.ts:10
- Info: TypeScriptPropertyBasedTesting integration found: packages/diff-sequences/src/__tests__/index.property.test.ts:9
- Info: TypeScriptPropertyBasedTesting integration found: packages/expect/src/__tests__/__arbitraries__/sharedSettings.ts:9
- Info: TypeScriptPropertyBasedTesting integration found: packages/expect/src/__tests__/matchers-toContain.property.test.ts:9
- Info: TypeScriptPropertyBasedTesting integration found: packages/expect/src/__tests__/matchers-toContainEqual.property.test.ts:9
- Info: TypeScriptPropertyBasedTesting integration found: packages/expect/src/__tests__/matchers-toEqual.property.test.ts:9
- Info: TypeScriptPropertyBasedTesting integration found: packages/expect/src/__tests__/matchers-toStrictEqual.property.test.ts:10
Reason
binaries present in source code
Details
- Warn: binary detected: e2e/native-esm/add.wasm:1
- Warn: binary detected: e2e/native-esm/wasm-bindgen/index_bg.wasm:1
Reason
Found 21/30 approved changesets -- score normalized to 7
Reason
branch protection is not maximal on development and all release branches
Details
- Info: 'allow deletion' disabled on branch 'main'
- Info: 'force pushes' disabled on branch 'main'
- Warn: 'branch protection settings apply to administrators' is disabled on branch 'main'
- Warn: could not determine whether codeowners review is allowed
- Warn: no status checks found to merge onto branch 'main'
- Warn: PRs are not required to make changes on branch 'main'; or we don't have data to detect it.If you think it might be the latter, make sure to run Scorecard with a PAT or use Repo Rules (that are always public) instead of Branch Protection settings
Reason
no effort to earn an OpenSSF best practices badge detected
Reason
detected GitHub workflow tokens with excessive permissions
Details
- Info: found token with 'none' permissions: .github/workflows/lock.yml:1
- Info: topLevel 'contents' permission set to 'read': .github/workflows/nightly.yml:13
- Info: topLevel 'contents' permission set to 'read': .github/workflows/nodejs.yml:15
- Warn: no topLevel permission defined: .github/workflows/pkg-pr-new.yml:1
- Warn: no topLevel permission defined: .github/workflows/prepare-cache.yml:1
- Warn: no topLevel permission defined: .github/workflows/test-nightly.yml:1
- Warn: no topLevel permission defined: .github/workflows/test.yml:1
- Info: no jobLevel write permissions found
Reason
SAST tool is not run on all commits -- score normalized to 0
Details
- Warn: 0 commits out of 21 are checked with a SAST tool
Reason
15 existing vulnerabilities detected
Details
- Warn: Project is vulnerable to: GHSA-r5fx-8r73-v86c
- Warn: Project is vulnerable to: GHSA-28hp-fgcr-2r4h
- Warn: Project is vulnerable to: GHSA-89mq-4x47-5v83
- Warn: Project is vulnerable to: GHSA-5cp4-xmrw-59wf
- Warn: Project is vulnerable to: GHSA-mhp6-pxh8-r675
- Warn: Project is vulnerable to: GHSA-2qqx-w9hr-q5gx
- Warn: Project is vulnerable to: GHSA-2vrf-hf26-jrp5
- Warn: Project is vulnerable to: GHSA-j58c-ww9w-pwp5
- Warn: Project is vulnerable to: GHSA-mqm9-c95h-x2p6
- Warn: Project is vulnerable to: GHSA-prc3-vjfx-vhm9
- Warn: Project is vulnerable to: GHSA-qwqh-hm9m-p5hr
- Warn: Project is vulnerable to: MAL-2022-2913
- Warn: Project is vulnerable to: MAL-2022-4017
- Warn: Project is vulnerable to: GHSA-4v9v-hfq4-rm2v
- Warn: Project is vulnerable to: GHSA-9jgg-88mc-972h
Score
6.1
/10
Last Scanned on 2025-07-07
The Open Source Security Foundation is a cross-industry collaboration to improve the security of open source software (OSS). The Scorecard provides security health metrics for open source projects.
Learn More