Is Require Main Filename Safe?
Require Main Filename — Nerq Trust Score 63.8/100 (C+ grade). Score based on 2 independent trust signals. Last analyzed: 2026-08-17
Require Main Filename is a npm package (shim for require) with a Nerq Trust Score of 63.8/100 (C+), based on 3 independent data dimensions. Last analyzed: 2026-08-17 Security: 90/100. Popularity: 100/100. Data sourced from npm registry, GitHub repository, NVD, OSV.dev, and OpenSSF Scorecard. Last updated: 2026-08-17. Machine-readable data (JSON).
Is Require Main Filename safe?
Trust Score Breakdown — Require Main Filename has a Nerq Trust Score of 63.8/100 (C+). Measured across 2 independent trust signals (as of 2026-08-17).
What is Require Main Filename's trust score?
Require Main Filename has a Nerq Trust Score of 63.8/100, earning a C+ grade. This score is based on 2 independently measured dimensions including security, maintenance, and community adoption.
What are the key security findings for Require Main Filename?
Require Main Filename's strongest signal is popularity at 100/100. No known vulnerabilities have been detected.
What is Require Main Filename and who maintains it?
| Author | bcoe |
| Category | npm Packages |
| Source | N/A |
Similar Npm by Trust Score
Compare
Safety Guide: Require Main Filename
What is Require Main Filename?
Require Main Filename is a Node.js package — shim for require.main.filename() that works in as many environments as possible.
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=require-main-filename
Key Safety Concerns for Node.js package
When evaluating any Node.js package, watch for: dependency vulnerabilities, malicious packages, typosquatting.
Measured Signals
Require Main Filename has a Nerq Trust Score of 64/100 (C+). This score is a composite of automated measurements of security, maintenance, community, and quality signals.
Key Takeaways
- Require Main Filename has a Trust Score of 64/100 (C+).
- The score is a measured composite — it is not a suitability judgment. Evaluate the individual signals against your own requirements.
- Query the current measured values via the Nerq API.
Detailed Score Analysis
| Dimension | Score |
|---|---|
| Security | 90/100 |
| Maintenance | 35/100 |
| Popularity | 100/100 |
| Quality | 65/100 |
| Community | 30/100 |
Based on 5 dimensions. Data from npm registry, GitHub repository, NVD, OSV.dev, and OpenSSF Scorecard.
What data does Require Main Filename collect?
Require Main Filename is a Node.js package maintained by bcoe. It receives approximately 41,747,454 weekly downloads. Licensed under ISC.
As a development package, Require Main Filename 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: Require Main Filename Privacy Report · Privacy review
Is Require Main Filename secure?
Security score: 90/100. Require Main Filename has 0 known vulnerabilities (CVEs) in the National Vulnerability Database. This is a clean record.
Licensed under ISC, 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: Require Main Filename Security Report
How we calculated this score
Require Main Filename's trust score of 63.8/100 (C+) is computed from npm registry, GitHub repository, NVD, OSV.dev, and OpenSSF Scorecard. The score reflects 5 independent dimensions: security (90/100), maintenance (35/100), popularity (100/100), quality (65/100), community (30/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.
Signals last measured on August 17, 2026. Data version: 1.0.
Full methodology documentation · Machine-readable data (JSON API)
Frequently Asked Questions
Is Require Main Filename Safe?
What is Require Main Filename's trust score?
What are safer alternatives to Require Main Filename?
Does Require Main Filename have known vulnerabilities?
Is Require Main Filename actively maintained?
Popular in npm Packages
Browse Categories
See Also
Disclaimer: Nerq trust scores are automated measurements based on publicly available signals. They are not endorsements, verdicts, or guarantees of suitability. Always evaluate the signals against your own requirements.