Is Subsystem Message Queue Safe?

Subsystem Message Queue — Nerq Trust Score 48.2/100 (D grade). Based on analysis of 2 trust dimensions, it is has notable safety concerns. Last updated: 2026-06-03.

Exercise caution with Subsystem Message Queue. Subsystem Message Queue 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 Subsystem Message Queue safe?

NO — USE WITH CAUTION — Subsystem Message Queue 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 → Subsystem Message Queue Privacy Report →

What is Subsystem Message Queue's trust score?

Subsystem Message Queue 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 Subsystem Message Queue?

Subsystem Message Queue'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 Subsystem Message Queue and who maintains it?

Authorttoohey
Categorynpm Packages
SourceN/A

Similar Npm by Trust Score

next-server-wrap (58)@arun-syngrid/hippaguard (58)pni (58)react-reviso (58)wdio-lambdatest-service-sdk (58)
See all safest Npm →

Compare

Subsystem Message Queue vs next-server-wrapSubsystem Message Queue vs @arun-syngrid/hippaguardSubsystem Message Queue vs pni

Safety Guide: Subsystem Message Queue

What is Subsystem Message Queue?

Subsystem Message Queue is a Node.js package — Yadah subsystem to provide a shared message queue.

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=@yadah/subsystem-message-queue

Key Safety Concerns for Node.js package

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

Trust Assessment

Subsystem Message Queue 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 Subsystem Message Queue Safe?
Exercise caution. @yadah/subsystem-message-queue 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 Subsystem Message Queue's trust score?
@yadah/subsystem-message-queue: 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=@yadah/subsystem-message-queue
What are safer alternatives to Subsystem Message Queue?
In the npm Packages category, more Node.js packages are being analyzed — check back soon. @yadah/subsystem-message-queue scores 48.2/100.
Does Subsystem Message Queue have known vulnerabilities?
Nerq checks Subsystem Message Queue 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 Subsystem Message Queue actively maintained?
Subsystem Message Queue 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