Is Code Splitting Safe?

Code Splitting — 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-06.

Exercise caution with Code Splitting. Code Splitting 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 Code Splitting safe?

NO — USE WITH CAUTION — Code Splitting 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 → Code Splitting Privacy Report →

What is Code Splitting's trust score?

Code Splitting 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 Code Splitting?

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

Authoryhjor
Categorynpm Packages
SourceN/A

Similar Npm by Trust Score

rn-dropdown-select (58)evo-shadcn-ui-default-theme-lib (58)hit-canvas (58)@betterdb/agent (58)@agenttoll/sdk (58)
See all safest Npm →

Compare

Code Splitting vs rn-dropdown-selectCode Splitting vs evo-shadcn-ui-default-theme-libCode Splitting vs hit-canvas

Safety Guide: Code Splitting

What is Code Splitting?

Code Splitting is a Node.js package — React Router 4 Code Splitting Helper.

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=code-splitting

Key Safety Concerns for Node.js package

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

Trust Assessment

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