Is Components Safe?

Components — Nerq Trust Score 70.5/100 (B grade). Based on analysis of 2 trust dimensions, it is generally safe but has some concerns. Last updated: 2026-04-28.

Yes, Components is safe to use. Components is a npm package with a Nerq Trust Score of 70.5/100 (B), based on 3 independent data dimensions. Recommended for production use. Security: 90/100. Popularity: 15/100. Data sourced from npm registry, GitHub repository, NVD, OSV.dev, and OpenSSF Scorecard. Last updated: 2026-03-22. Machine-readable data (JSON).

Is Components safe?

YES — Components has a Nerq Trust Score of 70.5/100 (B). It meets Nerq's trust threshold with strong signals across security, maintenance, and community adoption. Recommended for production use — review the full report below for specific considerations.

Security Analysis → Components Privacy Report →

What is Components's trust score?

Components has a Nerq Trust Score of 70.5/100, earning a B grade. This score is based on 2 independently measured dimensions including security, maintenance, and community adoption.

Security
90
Popularity
15

What are the key security findings for Components?

Components's strongest signal is security at 90/100. No known vulnerabilities have been detected. It meets the Nerq Verified threshold of 70+.

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

What is Components and who maintains it?

Authorxinchaoduyanh
Categorynpm Packages
SourceN/A

Similar Npm by Trust Score

@carbon/utilities (80)watskeburt (80)@salesforce/code-analyzer-regex-engine (80)@react-email/code-block (80)@ng-web-apis/resize-observer (80)
See all safest Npm →

Compare

Components vs @carbon/utilitiesComponents vs watskeburtComponents vs @salesforce/code-analyzer-regex-engine

Safety Guide: Components

What is Components?

Components is a Node.js package — A quick library starter for React with Tailwind CSS, Vite, TypeScript and Shadcn-ui components..

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=@classon/components

Key Safety Concerns for Node.js package

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

Trust Assessment

Components has a Nerq Trust Score of 70/100 (B) and meets Nerq trust threshold. This score is based on automated analysis of security, maintenance, community, and quality signals.

Key Takeaways

Detailed Score Analysis

DimensionScore
Security90/100
Maintenance100/100
Popularity15/100
Quality55/100
Community65/100

Based on 5 dimensions. Data from npm registry, GitHub repository, NVD, OSV.dev, and OpenSSF Scorecard.

What data does Components collect?

Privacy assessment for Components is not yet available. See our methodology for how Nerq measures privacy, or the public privacy review for any community-contributed notes.

Is Components secure?

Security score: 90/100. Components has 0 known vulnerabilities (CVEs) in the National Vulnerability Database. This is a clean record.

License information not available. Open-source packages allow independent security review of the source code.

Run your package manager's audit command (`npm audit`, `pip audit`, `cargo audit`) to check for known vulnerabilities in your dependency tree.

Full analysis: Components Security Report

How we calculated this score

Components's trust score of 70.5/100 (B) is computed from npm registry, GitHub repository, NVD, OSV.dev, and OpenSSF Scorecard. The score reflects 5 independent dimensions: security (90/100), maintenance (100/100), popularity (15/100), quality (55/100), community (65/100). Each dimension is weighted equally to produce the composite trust score.

Nerq analyzes over 7.5 million entities across 26 registries using the same methodology, enabling direct cross-entity comparison. Scores are updated continuously as new data becomes available.

This page was last reviewed on April 28, 2026. Data version: 0.0.

Full methodology documentation · Machine-readable data (JSON API)

Frequently Asked Questions

Is Components Safe?
Yes, it is safe to use. @classon/components with a Nerq Trust Score of 70.5/100 (B). Strongest signal: security (90/100). Score based on Security (90/100), Popularity (15/100).
What is Components's trust score?
@classon/components: 70.5/100 (B). Score based on Security (90/100), Popularity (15/100). Scores update as new data becomes available. API: GET nerq.ai/v1/preflight?target=@classon/components
What are safer alternatives to Components?
In the npm Packages category, more Node.js packages are being analyzed — check back soon. @classon/components scores 70.5/100.
Does Components have known vulnerabilities?
Nerq checks Components 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 Components actively maintained?
Components 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