Is Commitlint Config Safe?

Commitlint Config — Nerq Trust Score 78.0/100 (B+ grade). Based on analysis of 2 trust dimensions, it is generally safe but has some concerns. Last updated: 2026-03-30.

Yes, Commitlint Config is safe to use. Commitlint Config is a Node.js package with a Nerq Trust Score of 78.0/100 (B+), based on 3 independent data dimensions. It is recommended for production use. Security: 90/100. Popularity: 45/100. Data sourced from npm registry, GitHub repository, NVD, OSV.dev, and OpenSSF Scorecard. Last updated: 2026-03-30. Machine-readable data (JSON).

Is Commitlint Config safe?

YES — Commitlint Config has a Nerq Trust Score of 78.0/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 → {name} Privacy Report →

What is Commitlint Config's trust score?

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

Security
90
Popularity
45

What are the key security findings for Commitlint Config?

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

What is Commitlint Config and who maintains it?

Authormarsibarsi
Categorynpm
SourceN/A

Similar Npm by Trust Score

postcss-merge-rules (88)@vitest/spy (88)@vitest/coverage-v8 (88)jest-worker (88)rollup (88)
See all safest Npm →

Safety Guide: Commitlint Config

What is Commitlint Config?

Commitlint Config is a Node.js package — Taiga UI commitlint config.

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

Key Safety Concerns for Node.js packages

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

Trust Assessment

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

Key Takeaways

Frequently Asked Questions

Is Commitlint Config safe to use?
Yes, it is safe to use. @taiga-ui/commitlint-config has a Nerq Trust Score of 78.0/100 (B+). Strongest signal: security (90/100). Score based on security (90/100), popularity (45/100).
What is Commitlint Config's trust score?
@taiga-ui/commitlint-config: 78.0/100 (B+). Score based on: security (90/100), popularity (45/100). Scores update as new data becomes available. API: GET nerq.ai/v1/preflight?target=@taiga-ui/commitlint-config
What are safer alternatives to Commitlint Config?
In the npm category, more Node.js packages are being analyzed — check back soon. @taiga-ui/commitlint-config scores 78.0/100.
Does Commitlint Config have known vulnerabilities?
Nerq checks Commitlint Config 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.
How actively maintained is Commitlint Config?
Commitlint Config has a trust score of 78.0/100 (B+). Meets Nerq Verified threshold.
API: /v1/preflight Trust Badge API Docs

Disclaimer: Nerq trust scores are automated assessments based on publicly available signals. They are not endorsements or guarantees. Always conduct your own due diligence.