Is Pre Push Commit Naming Safe?

Pre Push Commit Naming — Nerq Trust Score 46.2/100 (D grade). Based on analysis of 2 trust dimensions, it is has notable safety concerns. Last updated: 2026-07-26.

Exercise caution with Pre Push Commit Naming. Pre Push Commit Naming is a npm package 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).

Safety Guide: Pre Push Commit Naming

What is Pre Push Commit Naming?

Pre Push Commit Naming is a Node.js package.

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=pre-push-commit-naming

Key Safety Concerns for Node.js package

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

Trust Assessment

Pre Push Commit Naming 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

• Pre Push Commit Naming has a Trust Score of 46/100 (D).
• Review carefully before use — below trust threshold.
• Always verify independently using the Nerq API.

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