Is 300 Safe?

300 — Nerq Trust Score 46.2/100 (D grade). Based on analysis of 2 trust dimensions, it is has notable safety concerns. Last updated: 2026-07-22.

Exercise caution with 300. 300 is a npm package with a Nerq Trust Score of 46.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 300 safe?

NO — USE WITH CAUTION — 300 has a Nerq Trust Score of 46.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 → 300 Privacy Report →

What is 300's trust score?

300 has a Nerq Trust Score of 46.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 300?

300'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 300 and who maintains it?

Authorxiaosheng
Categorynpm Packages
SourceN/A

300 Across Platforms

Same developer/company in other registries:

法语300句有声完整版
53/100 · ios

Similar Npm by Trust Score

create-sss (56)sysdb (56)better-auth-lead (56)@typeserve/core (56)happy-translate (56)
See all safest Npm →

Compare

300 vs create-sss300 vs sysdb300 vs better-auth-lead

Safety Guide: 300

What is 300?

300 is a Node.js package — test.

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=300

Key Safety Concerns for Node.js package

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

Trust Assessment

300 has a Nerq Trust Score of 46/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 300 Safe?
Exercise caution. 300 with a Nerq Trust Score of 46.2/100 (D). Strongest signal: security (90/100). Score based on Security (90/100), Popularity (0/100).
What is 300's trust score?
300: 46.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=300
What are safer alternatives to 300?
In the npm Packages category, more Node.js packages are being analyzed — check back soon. 300 scores 46.2/100.
Does 300 have known vulnerabilities?
Nerq checks 300 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 300 actively maintained?
300 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