Is Hypercore Byte Stream Safe?

Hypercore Byte Stream — Nerq Trust Score 48.2/100 (D grade). Based on analysis of 2 trust dimensions, it is has notable safety concerns. Last updated: 2026-07-26.

Exercise caution with Hypercore Byte Stream. Hypercore Byte Stream is a npm package with a Nerq Trust Score of 48.2/100 (D), based on 3 independent data dimensions. Below the recommended threshold of 70. Security: 90/100. Popularity: 0/100. Data sourced from npm registry, GitHub repository, NVD, OSV.dev, and OpenSSF Scorecard. Last updated: 2026-03-25. Machine-readable data (JSON).

Is Hypercore Byte Stream safe?

NO — USE WITH CAUTION — Hypercore Byte Stream has a Nerq Trust Score of 48.2/100 (D). It has below-average trust signals with significant gaps in security, maintenance, or documentation. Not recommended for production use without thorough manual review and additional security measures.

Security Analysis → Hypercore Byte Stream Privacy Report →

What is Hypercore Byte Stream's trust score?

Hypercore Byte Stream has a Nerq Trust Score of 48.2/100, earning a D grade. This score is based on 2 independently measured dimensions including security, maintenance, and community adoption.

Security
90
Popularity
0

What are the key security findings for Hypercore Byte Stream?

Hypercore Byte Stream's strongest signal is security at 90/100. No known vulnerabilities have been detected. It has not yet reached the Nerq Verified threshold of 70+.

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

What is Hypercore Byte Stream and who maintains it?

Authormafintosh
Categorynpm Packages
SourceN/A

Similar Npm by Trust Score

react-library-boilerplate-for-npm (58)bindler (58)@yassidev/nuxt-directus (58)spectro-kubernetes-client (58)pocketto-svelte (58)
See all safest Npm →

Compare

Hypercore Byte Stream vs react-library-boilerplate-for-npmHypercore Byte Stream vs bindlerHypercore Byte Stream vs @yassidev/nuxt-directus

Safety Guide: Hypercore Byte Stream

What is Hypercore Byte Stream?

Hypercore Byte Stream is a Node.js package — A Readable stream around a Hypercore that supports reading byte ranges.

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=hypercore-byte-stream

Key Safety Concerns for Node.js package

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

Trust Assessment

Hypercore Byte Stream has a Nerq Trust Score of 48/100 (D) and has not yet reached Nerq trust threshold (70+). This score is based on automated analysis of security, maintenance, community, and quality signals.

Key Takeaways

Frequently Asked Questions

Is Hypercore Byte Stream Safe?
Exercise caution. hypercore-byte-stream with a Nerq Trust Score of 48.2/100 (D). Strongest signal: security (90/100). Score based on Security (90/100), Popularity (0/100).
What is Hypercore Byte Stream's trust score?
hypercore-byte-stream: 48.2/100 (D). Score based on Security (90/100), Popularity (0/100). Scores update as new data becomes available. API: GET nerq.ai/v1/preflight?target=hypercore-byte-stream
What are safer alternatives to Hypercore Byte Stream?
In the npm Packages category, more Node.js packages are being analyzed — check back soon. hypercore-byte-stream scores 48.2/100.
Does Hypercore Byte Stream have known vulnerabilities?
Nerq checks Hypercore Byte Stream 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 Hypercore Byte Stream actively maintained?
Hypercore Byte Stream 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