Is Promises Safe?
According to Nerq's independent analysis of promises, this npm has a trust score of 25.0 out of 100, earning a F grade. With 0 stars on npm, it is below the recommended threshold of 70. Data sourced from 13+ independent signals including GitHub, NVD, OSV.dev, and OpenSSF Scorecard. Last updated: 2026-03-20. Machine-readable data (JSON).
Is Promises safe?
NO — USE WITH CAUTION — Promises has a Nerq Trust Score of 25.0/100 (F). 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.
Trust Score Breakdown
Key Findings
Details
| Author | jacwright |
| Category | npm |
| Stars | 0 |
| Source | N/A |
What Is Promises?
Promises is a AI tool in the npm category. A flexible and generic promise implementation for Javascript libraries
As of March 2026, Promises is available on npm, making it an emerging tool in the AI ecosystem. But popularity alone does not equal safety — which is why Nerq independently analyzes every tool across 13+ trust signals.
How Nerq Assesses Promises's Safety
Nerq evaluates every AI tool across 13+ independent trust signals drawn from public sources including GitHub, NVD, OSV.dev, OpenSSF Scorecard, and package registries. These signals are grouped into five core dimensions: Security (known CVEs, dependency vulnerabilities, security policies), Maintenance (commit frequency, release cadence, issue response times), Documentation (README quality, API docs, examples), Compliance (license, regulatory alignment across 52 jurisdictions), and Community (stars, forks, downloads, ecosystem integrations).
Promises receives an overall Trust Score of 25.0/100 (F), which Nerq considers low. This is below the Nerq Verified threshold of 70. We recommend additional due diligence before production deployment.
Nerq updates trust scores continuously as new data becomes available. To get the latest assessment, query the API: GET nerq.ai/v1/preflight?target=promises
Each dimension is weighted according to its importance for the tool's category. For example, Security and Maintenance carry higher weight for tools that handle sensitive data or execute code, while Community and Documentation are weighted more heavily for developer-facing libraries and frameworks. This ensures that Promises's score reflects the risks most relevant to its actual usage patterns. The final score is a weighted average across all five dimensions, normalized to a 0-100 scale with letter grades from A (highest) to F (lowest).
Who Should Use Promises?
Promises is designed for:
- Developers and teams working with npm tools
- Organizations evaluating AI tools for their stack
- Researchers exploring AI capabilities in this domain
Risk guidance: We recommend caution with Promises. The low trust score suggests potential risks in security, maintenance, or community support. Consider using a more established alternative for any production or sensitive workload.
How to Verify Promises's Safety Yourself
While Nerq provides automated trust analysis, we recommend these additional steps before adopting any AI tool:
- Check the source code — Review the repository security policy, open issues, and recent commits for signs of active maintenance.
- Scan dependencies — Use tools like
npm audit,pip-audit, orsnykto check for known vulnerabilities in Promises's dependency tree. - Review permissions — Understand what access Promises requires. AI tools should follow the principle of least privilege.
- Test in isolation — Run Promises in a sandboxed environment before granting access to production data or systems.
- Monitor continuously — Use Nerq's API to set up automated trust checks:
GET nerq.ai/v1/preflight?target=promises - Review the license — Confirm that Promises's license is compatible with your intended use case. Pay attention to restrictions on commercial use, redistribution, and derivative works. Some AI tools use dual licensing or have separate terms for enterprise customers that differ from the open-source license.
- Check community signals — Look at the project's issue tracker, discussion forums, and social media presence. A healthy community actively reports bugs, contributes fixes, and discusses security concerns openly. Low community engagement may indicate limited peer review of the codebase.
Common Safety Concerns with Promises
When evaluating whether Promises is safe, consider these category-specific risks:
Understand how Promises processes, stores, and transmits your data. Review the tool's privacy policy and data retention practices, especially for sensitive or proprietary information.
Check Promises's dependency tree for known vulnerabilities. Tools with outdated or unmaintained dependencies pose a higher security risk.
Regularly check for updates to Promises. Security patches and bug fixes are only effective if you're running the latest version.
If Promises connects to external APIs or services, each integration point is a potential attack surface. Audit all third-party connections, verify that data shared with external services is minimized, and ensure that integration credentials are rotated regularly.
Verify that Promises's license is compatible with your intended use case. Some AI tools have restrictive licenses that limit commercial use, redistribution, or derivative works. Using Promises in violation of its license can expose your organization to legal liability.
Best Practices for Using Promises Safely
Whether you're an individual developer or an enterprise team, these practices will help you get the most from Promises while minimizing risk:
Periodically review how Promises is used in your workflow. Check for unexpected behavior, permissions drift, and compliance with your security policies.
Ensure Promises and all its dependencies are running the latest stable versions to benefit from security patches.
Grant Promises only the minimum permissions it needs to function. Avoid granting admin or root access.
Subscribe to Promises's security advisories and vulnerability disclosures. Use Nerq's API to get automated trust score updates.
Create and maintain a clear policy for how Promises is used within your organization, including data handling guidelines and acceptable use cases.
When Should You Avoid Promises?
Even promising tools aren't right for every situation. Consider avoiding Promises in these scenarios:
- Production environments handling sensitive customer data
- Regulated industries (healthcare, finance, government) without additional compliance review
- Mission-critical systems where downtime has significant business impact
For each scenario, evaluate whether Promises's trust score of 25.0/100 meets your organization's risk tolerance. We recommend running a manual security assessment alongside the automated Nerq score.
How Promises Compares to Industry Standards
Nerq indexes over 204,000 AI agents and tools across dozens of categories. Among npm tools, the average Trust Score is 62/100. Promises's score of 25.0/100 is below the category average of 62/100.
This suggests that Promises trails behind many comparable npm tools. Organizations with strict security requirements should evaluate whether higher-scoring alternatives better meet their needs.
Industry benchmarks matter because they contextualize a tool's safety profile. A score that looks moderate in isolation may actually represent strong performance within a challenging category — or vice versa. Nerq's category-relative analysis helps teams make informed decisions by showing not just absolute quality, but how a tool ranks against its direct peers.
Trust Score History
Nerq continuously monitors Promises and recalculates its Trust Score as new data becomes available. Our scoring engine ingests real-time signals from source repositories, vulnerability databases (NVD, OSV.dev), package registries, and community metrics. When a new CVE is published, a major release ships, or maintenance patterns change, Promises's score is updated within 24 hours.
Historical trust trends reveal whether a tool is improving, stable, or declining over time. A tool that consistently maintains or improves its score demonstrates ongoing commitment to security and quality. Conversely, a downward trend may signal reduced maintenance, growing technical debt, or unresolved vulnerabilities. To track Promises's score over time, use the Nerq API: GET nerq.ai/v1/preflight?target=promises&include=history
Nerq retains trust score snapshots at regular intervals, enabling trend analysis across weeks and months. Enterprise users can access detailed historical reports showing how each dimension — security, maintenance, documentation, compliance, and community — has evolved independently, providing granular visibility into which aspects of Promises are strengthening or weakening over time.
Key Takeaways
- Promises has a Trust Score of 25.0/100 (F) and is not yet Nerq Verified.
- Promises has significant trust gaps. Consider higher-rated alternatives unless specific requirements mandate its use.
- Among npm tools, Promises scores below the category average of 62/100, suggesting room for improvement relative to peers.
- Always verify safety independently — use Nerq's Preflight API for automated, up-to-date trust checks before integration.
Frequently Asked Questions
Is promises safe to use?
What is promises's trust score?
Are there safer alternatives to promises?
How often is Promises's safety score updated?
Can I use Promises in a regulated environment?
Disclaimer: Nerq trust scores are automated assessments based on publicly available signals. They are not endorsements or guarantees. Always conduct your own due diligence.