Este Pheromon sigur?
Pheromon — Nerq Trust Score 37.0/100 (Nota E). Pe baza analizei a 3 dimensiuni de încredere, este are riscuri de securitate semnificative. Ultima actualizare: 2026-04-21.
Fiți precauți cu Pheromon. Pheromon este un software tool cu un Scor de Încredere Nerq de 37.0/100 (E), based on 3 dimensiuni independente de date. Sub pragul verificat Nerq Mentenanță: 0/100. Popularitate: 0/100. Date provenite din multiple surse publice inclusiv registre de pachete, GitHub, NVD, OSV.dev și OpenSSF Scorecard. Ultima actualizare: 2026-04-21. Date citibile de mașină (JSON).
Este Pheromon sigur?
NO — USE WITH CAUTION — Pheromon has a Nerq Trust Score of 37.0/100 (E). Are semnale de încredere sub medie cu lacune semnificative in securitate, mentenanță, or documentație. Not recommended for production use without thorough manual review and additional securitate measures.
Care este scorul de încredere al Pheromon?
Pheromon are un Nerq Trust Score de 37.0/100 cu nota E. Acest scor se bazează pe 3 dimensiuni măsurate independent, inclusiv securitate, întreținere și adopție comunitară.
Care sunt principalele constatări de securitate pentru Pheromon?
Cel mai puternic semnal al Pheromon este mentenanță la 0/100. Nu au fost detectate vulnerabilități cunoscute. It has not yet reached the Nerq Verified threshold of 70+.
Ce este Pheromon și cine îl întreține?
| Autor | 0xb66ee72cfa34c557172509a7098ada1d2a1268ee |
| Categorie | Automation |
| Stele | 1 |
| Sursă | https://8004scan.io/agents/pheromon |
| Protocols | x402 |
Alternative populare în automation
What Is Pheromon?
Pheromon is a automation platform: Pheromon automates workflows in various sectors.. It has 1 GitHub stars. Nerq Trust Score: 37/100 (E).
Nerq independently analyzes every software tool, app, and extension across multiple trust signals including securitate vulnerabilities, mentenanță activity, license conformitate, and adoptare comunitară.
How Nerq Assesses Pheromon's Safety
Nerq's Trust Score is calculated from 13+ independent signals aggregated into five dimensiuni. Here is how Pheromon performs in each:
- Mentenanță (0/100): Pheromon is potentially abandoned. We track commit frequency, release cadence, issue response times, and PR merge rates.
- Documentation (0/100): Documentation quality is insufficient. This includes README completeness, API documentație, usage examples, and contribution guidelines.
- Community (0/100): Community adoption is limited. Bazat pe GitHub stars, forks, download counts, and ecosystem integrations.
The overall Trust Score of 37.0/100 (E) reflects the weighted combination of these signals. This is below the Nerq Verified threshold of 70. We recommend additional due diligence before production deployment.
Who Should Use Pheromon?
Pheromon is designed for:
- Teams automating repetitive workflows
- Organizations connecting multiple tools and services
- Developers building event-driven AI pipelines
Risk guidance: We recommend caution with Pheromon. The low trust score suggests potential risks in securitate, mentenanță, or community support. Consider using a more established alternative for any production or sensitive workload.
How to Verify Pheromon's Safety Yourself
While Nerq provides automated trust analysis, we recommend these additional steps before adopting any software tool:
- Check the source code — Verificați repository securitate policy, open issues, and recent commits for signs of active mentenanță.
- Scan dependencies — Use tools like
npm audit,pip-audit, orsnykto check for known vulnerabilities in Pheromon's dependency tree. - Recenzie permissions — Understand what access Pheromon requires. Software tools should follow the principle of least privilege.
- Test in isolation — Run Pheromon 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=Pheromon - Verificați license — Confirm that Pheromon'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 securitate concerns openly. Low community engagement may indicate limited peer review of the codebase.
Common Safety Concerns with Pheromon
When evaluating whether Pheromon is safe, consider these category-specific risks:
Understand how Pheromon processes, stores, and transmits your data. Verificați tool's privacy policy and data retention practices, especially for sensitive or proprietary information.
Check Pheromon's dependency tree for known vulnerabilities. Tools with outdated or unmaintained dependencies pose a higher securitate risk.
Regularly check for updates to Pheromon. Securitate patches and bug fixes are only effective if you're running the latest version.
If Pheromon 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 Pheromon's license is compatible with your intended use case. Some AI tools have restrictive licenses that limit commercial use, redistribution, or derivative works. Using Pheromon in violation of its license can expose your organization to legal liability.
Best Practices for Using Pheromon Safely
Whether you're an individual developer or an enterprise team, these practices will help you get the most from Pheromon while minimizing risk:
Periodically review how Pheromon is used in your workflow. Check for unexpected behavior, permissions drift, and conformitate with your securitate policies.
Ensure Pheromon and all its dependencies are running the latest stable versions to benefit from securitate patches.
Grant Pheromon only the minimum permissions it needs to function. Avoid granting admin or root access.
Subscribe to Pheromon's securitate advisories and vulnerability disclosures. Use Nerq's API to get automated trust score updates.
Create and maintain a clear policy for how Pheromon is used within your organization, including data handling guidelines and acceptable use cases.
When Should You Avoid Pheromon?
Even promising tools aren't right for every situation. Consider avoiding Pheromon in these scenarios:
- Production environments handling sensitive customer data
- Regulated industries (healthcare, finance, government) without additional conformitate review
- Mission-critical systems where downtime has significant business impact
For each scenario, evaluate whether Pheromon's trust score of 37.0/100 meets your organization's risk tolerance. We recommend running a manual securitate assessment alongside the automated Nerq score.
How Pheromon Compares to Industry Standards
Nerq indexes over 6 million software tools, apps, and packages across dozens of categories. Among automation tools, the average Trust Score is 64/100. Pheromon's score of 37.0/100 is below the category average of 64/100.
This suggests that Pheromon trails behind many comparable automation tools. Organizations with strict securitate 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 moderat 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 Pheromon 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 mentenanță patterns change, Pheromon'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 securitate and quality. Conversely, a downward trend may signal reduced mentenanță, growing technical debt, or unresolved vulnerabilities. To track Pheromon's score over time, use the Nerq API: GET nerq.ai/v1/preflight?target=Pheromon&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 — securitate, mentenanță, documentație, conformitate, and community — has evolved independently, providing granular visibility into which aspects of Pheromon are strengthening or weakening over time.
Pheromon vs Alternative
In the automation category, Pheromon scores 37.0/100. There are higher-scoring alternatives available. For a detailed comparison, see:
- Pheromon vs Windows Desktop Control — Trust Score: 62.0/100
- Pheromon vs gemma-7b — Trust Score: 68.9/100
- Pheromon vs Tianji — Trust Score: 60.7/100
Concluzii principale
- Pheromon has a Trust Score of 37.0/100 (E) and is not yet Nerq Verified.
- Pheromon has significant trust gaps. Consider higher-rated alternatives unless specific requirements mandate its use.
- Among automation tools, Pheromon scores below the category average of 64/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.
Întrebări frecvente
Este Pheromon sigur?
Care este scorul de încredere al Pheromon?
Care sunt alternative mai sigure la Pheromon?
Cât de des este actualizat scorul de securitate al Pheromon?
Pot folosi Pheromon într-un mediu reglementat?
Vezi și
Disclaimer: Scorurile de încredere Nerq sunt evaluări automatizate bazate pe semnale disponibile public. Nu sunt recomandări sau garanții. Efectuați întotdeauna propria verificare.