Is Memory Safe?

Memory — Nerq Trust Score 73.2/100 (B grade). Based on analysis of 2 trust dimensions, it is generally safe but has some concerns. Last updated: 2026-07-08.

Yes, Memory is safe to use. Memory is a npm package with a Nerq Trust Score of 73.2/100 (B), based on 3 independent data dimensions. Recommended for production use. Security: 90/100. Popularity: 90/100. Data sourced from npm registry, GitHub repository, NVD, OSV.dev, and OpenSSF Scorecard. Last updated: 2026-04-12. Machine-readable data (JSON).

Is Memory safe?

YES — Memory has a Nerq Trust Score of 73.2/100 (B). It meets Nerq's trust threshold with strong signals across security, maintenance, and community adoption. Recommended for production use — review the full report below for specific considerations.

Security Analysis → Memory Privacy Report →

What is Memory's trust score?

Memory has a Nerq Trust Score of 73.2/100, earning a B grade. This score is based on 2 independently measured dimensions including security, maintenance, and community adoption.

Security
90
Popularity
90

What are the key security findings for Memory?

Memory's strongest signal is security at 90/100. No known vulnerabilities have been detected. It meets the Nerq Verified threshold of 70+.

Security score: 90/100 (strong)
Popularity: 90/100 — community adoption

What is Memory and who maintains it?

Authorjaredwray
Categorynpm Packages
SourceN/A

Similar Npm by Trust Score

@react-native-community/cli (83)@storybook/addon-coverage (83)@mergeapi/react-merge-link (83)@floating-ui/react-dom (83)@aws-sdk/xml-builder (83)
See all safest Npm →

Compare

Memory vs @react-native-community/cliMemory vs @storybook/addon-coverageMemory vs @mergeapi/react-merge-link

Safety Guide: Memory

What is Memory?

Memory is a Node.js package — High Performance In-Memory Cache for Node.js.

How to Verify Safety

Run npm audit to check for vulnerabilities. Review the package's GitHub repository for recent commits.

You can also check the trust score via API: GET /v1/preflight?target=@cacheable/memory

Key Safety Concerns for Node.js package

When evaluating any Node.js package, watch for: dependency vulnerabilities, malicious packages, typosquatting.

Trust Assessment

Memory has a Nerq Trust Score of 73/100 (B) and meets Nerq trust threshold. This score is based on automated analysis of security, maintenance, community, and quality signals.

Key Takeaways

Detailed Score Analysis

DimensionScore
Security90/100
Maintenance61/100
Popularity90/100
Quality80/100
Community40/100

Based on 5 dimensions. Data from npm registry, GitHub repository, NVD, OSV.dev, and OpenSSF Scorecard.

What data does Memory collect?

Memory is a Node.js package maintained by jaredwray. It receives approximately 4,570,030 weekly downloads. Licensed under MIT.

As a development package, Memory does not directly collect end-user personal data. However, applications built with it may collect data depending on implementation. Privacy score: 80/100.

Review the package's dependencies for potential supply chain risks. Run your package manager's audit command regularly.

Full analysis: Memory Privacy Report · Privacy review

Is Memory secure?

Security score: 90/100. Memory has 0 known vulnerabilities (CVEs) in the National Vulnerability Database. This is a clean record.

Licensed under MIT, allowing code inspection. Open-source packages allow independent security review of the source code.

Run your package manager's audit command (`npm audit`, `pip audit`, `cargo audit`) to check for known vulnerabilities in your dependency tree.

Full analysis: Memory Security Report

How we calculated this score

Memory's trust score of 73.2/100 (B) is computed from npm registry, GitHub repository, NVD, OSV.dev, and OpenSSF Scorecard. The score reflects 5 independent dimensions: security (90/100), maintenance (61/100), popularity (90/100), quality (80/100), community (40/100). Each dimension is weighted equally to produce the composite trust score.

Nerq analyzes over 7.5 million entities across 26 registries using the same methodology, enabling direct cross-entity comparison. Scores are updated continuously as new data becomes available.

This page was last reviewed on July 08, 2026. Data version: 1.0.

Full methodology documentation · Machine-readable data (JSON API)

Frequently Asked Questions

Is Memory Safe?
Yes, it is safe to use. @cacheable/memory with a Nerq Trust Score of 73.2/100 (B). Strongest signal: security (90/100). Score based on Security (90/100), Popularity (90/100).
What is Memory's trust score?
@cacheable/memory: 73.2/100 (B). Score based on Security (90/100), Popularity (90/100). Scores update as new data becomes available. API: GET nerq.ai/v1/preflight?target=@cacheable/memory
What are safer alternatives to Memory?
In the npm Packages category, more Node.js packages are being analyzed — check back soon. @cacheable/memory scores 73.2/100.
Does Memory have known vulnerabilities?
Nerq checks Memory against NVD, OSV.dev, and registry-specific vulnerability databases. Current security score: 90/100. Run your package manager's audit command for the latest findings.
Is Memory actively maintained?
Memory maintenance score: N/A. Check the repository for recent commit activity and issue responsiveness.
API: /v1/preflight Trust Badge API Docs

See Also

Disclaimer: Nerq trust scores are automated assessments based on publicly available signals. They are not endorsements or guarantees. Always conduct your own due diligence.

We use cookies for analytics and caching. Privacy