Is Git Conventional Commits Safe?

Git Conventional Commits — Nerq Trust Score 46.2/100 (D grade). Based on analysis of 2 trust dimensions, it is has notable safety concerns. Last updated: 2026-05-02.

Exercise caution with Git Conventional Commits. Git Conventional Commits is a npm package (git conventional commits util) 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 Git Conventional Commits safe?

NO — USE WITH CAUTION — Git Conventional Commits 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 → Git Conventional Commits Privacy Report →

What is Git Conventional Commits's trust score?

Git Conventional Commits 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 Git Conventional Commits?

Git Conventional Commits'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 Git Conventional Commits and who maintains it?

Authorqoomon
Categorynpm Packages
SourceN/A

Git Conventional Commits Across Platforms

Same developer/company in other registries:

git-conventional-commits
53/100 · crates

Similar Npm by Trust Score

svelte-deep-wind-preprocess (56)avalynx-form (56)esm_002 (56)create-vite-slides (56)vite-plugin-auto-skeleton (56)
See all safest Npm →

Compare

Git Conventional Commits vs svelte-deep-wind-preprocessGit Conventional Commits vs avalynx-formGit Conventional Commits vs esm_002

Safety Guide: Git Conventional Commits

What is Git Conventional Commits?

Git Conventional Commits is a Node.js package — git conventional commits util.

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=git-conventional-commits

Key Safety Concerns for Node.js package

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

Trust Assessment

Git Conventional Commits 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

Detailed Score Analysis

DimensionScore
Security90/100
Maintenance50/100
Popularity0/100
Quality30/100
Community35/100

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

What data does Git Conventional Commits collect?

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

Is Git Conventional Commits secure?

Security score: 90/100. Git Conventional Commits 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: Git Conventional Commits Security Report

Git Conventional Commits Across Platforms

Same developer/company in other registries:

git-conventional-commits (crates, 53/100)

How we calculated this score

Git Conventional Commits's trust score of 46.2/100 (D) is computed from npm registry, GitHub repository, NVD, OSV.dev, and OpenSSF Scorecard. The score reflects 5 independent dimensions: security (90/100), maintenance (50/100), popularity (0/100), quality (30/100), community (35/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 May 02, 2026. Data version: 0.0.

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

Frequently Asked Questions

Is Git Conventional Commits Safe?
Exercise caution. git-conventional-commits 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 Git Conventional Commits's trust score?
git-conventional-commits: 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=git-conventional-commits
What are safer alternatives to Git Conventional Commits?
In the npm Packages category, more Node.js packages are being analyzed — check back soon. git-conventional-commits scores 46.2/100.
Does Git Conventional Commits have known vulnerabilities?
Nerq checks Git Conventional Commits 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 Git Conventional Commits actively maintained?
Git Conventional Commits 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