Is Javascript Clients Shared Safe?

Javascript Clients Shared — Nerq Trust Score 48.2/100 (D grade). Score based on 2 independent trust signals. Last analyzed: 2026-03-25

Javascript Clients Shared is a npm package with a Nerq Trust Score of 48.2/100 (D), based on 3 independent data dimensions. Last analyzed: 2026-03-25 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 Javascript Clients Shared safe?

Trust Score Breakdown — Javascript Clients Shared has a Nerq Trust Score of 48.2/100 (D). Measured across 2 independent trust signals (as of 2026-03-25).

Security Analysis → Javascript Clients Shared Privacy Report →

What is Javascript Clients Shared's trust score?

Javascript Clients Shared 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 Javascript Clients Shared?

Javascript Clients Shared's strongest signal is security at 90/100. No known vulnerabilities have been detected.

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

What is Javascript Clients Shared and who maintains it?

Authorhyperkid
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

Javascript Clients Shared vs react-library-boilerplate-for-npmJavascript Clients Shared vs bindlerJavascript Clients Shared vs @yassidev/nuxt-directus

Safety Guide: Javascript Clients Shared

What is Javascript Clients Shared?

Javascript Clients Shared is a Node.js package — If you want to use [RedHatInsights/shared](https://github.com/RedHatInsights/shared) you shouldn't use get requests directly, but rather use this client to integrate with this service..

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=@redhat-cloud-services/javascript-clients-shared

Key Safety Concerns for Node.js package

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

Measured Signals

Javascript Clients Shared has a Nerq Trust Score of 48/100 (D). This score is a composite of automated measurements of security, maintenance, community, and quality signals.

Key Takeaways

Frequently Asked Questions

Is Javascript Clients Shared Safe?
@redhat-cloud-services/javascript-clients-shared 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 Javascript Clients Shared's trust score?
@redhat-cloud-services/javascript-clients-shared: 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=@redhat-cloud-services/javascript-clients-shared
What are safer alternatives to Javascript Clients Shared?
In the npm Packages category, more Node.js packages are being analyzed — check back soon. @redhat-cloud-services/javascript-clients-shared scores 48.2/100.
Does Javascript Clients Shared have known vulnerabilities?
Nerq checks Javascript Clients Shared 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 Javascript Clients Shared actively maintained?
Javascript Clients Shared 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 measurements based on publicly available signals. They are not endorsements, verdicts, or guarantees of suitability. Always evaluate the signals against your own requirements.

We use cookies for analytics and caching. Privacy