Is Config Conventional Safe?

Config Conventional — Nerq Trust Score 82.2/100 (A- grade). Based on analysis of 2 trust dimensions, it is considered safe to use. Last updated: 2026-06-24.

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

Is Config Conventional safe?

YES — Config Conventional has a Nerq Trust Score of 82.2/100 (A-). 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 → Config Conventional Privacy Report →

What is Config Conventional's trust score?

Config Conventional has a Nerq Trust Score of 82.2/100, earning a A- grade. This score is based on 2 independently measured dimensions including security, maintenance, and community adoption.

Security
90
Popularity
90

What are the key security findings for Config Conventional?

Config Conventional'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: 90/100 — community adoption

What is Config Conventional and who maintains it?

Authormarionebl
Categorynpm Packages
SourceN/A

Similar Npm by Trust Score

@supabase/storage-js (90)@supabase/realtime-js (90)@supabase/functions-js (90)@testing-library/react (90)@supabase/supabase-js (90)
See all safest Npm →

Compare

Config Conventional vs @supabase/storage-jsConfig Conventional vs @supabase/realtime-jsConfig Conventional vs @supabase/functions-js

Safety Guide: Config Conventional

What is Config Conventional?

Config Conventional is a Node.js package — Shareable commitlint config enforcing conventional commits.

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=@commitlint/config-conventional

Key Safety Concerns for Node.js package

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

Trust Assessment

Config Conventional has a Nerq Trust Score of 82/100 (A-) 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
Popularity90/100
Quality65/100
Community55/100

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

What data does Config Conventional collect?

Config Conventional is a Node.js package maintained by marionebl. It receives approximately 5,129,705 weekly downloads. Licensed under MIT.

As a development package, Config Conventional does not directly collect end-user personal data. However, applications built with it may collect data depending on implementation. Privacy score: 80/100.

Review the package's dependencies for potential supply chain risks. Run your package manager's audit command regularly.

Full analysis: Config Conventional Privacy Report · Privacy review

Is Config Conventional secure?

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

Licensed under MIT, allowing code inspection. 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: Config Conventional Security Report

How we calculated this score

Config Conventional's trust score of 82.2/100 (A-) 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 (90/100), quality (65/100), community (55/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 June 24, 2026. Data version: 1.0.

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

Frequently Asked Questions

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