Apakah Go Roast Aman?
Go Roast — Nerq Trust Score 54.1/100 (Nilai D). Skor berdasarkan 5 independent trust signals.
Go Roast adalah software tool dengan Skor Kepercayaan Nerq sebesar 54.1/100 (D), based on 5 dimensi data independen. Keamanan: 0/100. Pemeliharaan: 1/100. Popularitas: 0/100. Data bersumber dari berbagai sumber publik termasuk registri paket, GitHub, NVD, OSV.dev, dan OpenSSF Scorecard. Terakhir diperbarui: n/a. Data yang dapat dibaca mesin (JSON).
Apakah Go Roast Aman?
Rincian Skor Kepercayaan — Go Roast has a Nerq Trust Score of 54.1/100 (D). Measured across 5 independent trust signals.
Berapa skor kepercayaan Go Roast?
Go Roast memiliki Skor Kepercayaan Nerq 54.1/100 dengan nilai D. Skor ini didasarkan pada 5 dimensi yang diukur secara independen.
Apa temuan keamanan utama untuk Go Roast?
Sinyal terkuat Go Roast adalah kepatuhan pada 97/100. Tidak ada kerentanan yang diketahui terdeteksi.
Apa itu Go Roast dan siapa yang mengelolanya?
| Pembuat | jarocki |
| Kategori | Keamanan |
| Sumber | https://github.com/jarocki/go-roast |
| Frameworks | anthropic |
| Protocols | mcp · rest |
Kepatuhan Regulasi
| EU AI Act Risk Class | MINIMAL |
| Compliance Score | 97/100 |
| Jurisdictions | Assessed across 52 jurisdictions |
Alternatif Populer di keamanan
What Is Go Roast?
Go Roast is a keamanan tool: go-roast processes and decodes Interactsh OAST domain names for keamanan purposes.. Nerq Trust Score: 54/100 (D).
Nerq independently analyzes every software tool, app, and extension across multiple trust signals including keamanan vulnerabilities, pemeliharaan activity, license kepatuhan, and adopsi komunitas.
How Nerq Assesses Go Roast's Safety
Nerq's Trust Score is calculated from 13+ independent signals aggregated into five dimensi. Here is how Go Roast performs in each:
- Keamanan (0/100): Go Roast's keamanan posture is poor. This score factors in known CVEs, dependency vulnerabilities, keamanan policy presence, and code signing practices.
- Pemeliharaan (1/100): Go Roast is potentially abandoned. We track commit frequency, release cadence, issue response times, and PR merge rates.
- Documentation (1/100): Documentation quality is insufficient. This includes README completeness, API dokumentasi, usage examples, and contribution guidelines.
- Compliance (97/100): Go Roast is broadly compliant. Assessed against regulations in 52 jurisdictions including the EU AI Act, CCPA, and GDPR.
- Community (0/100): Community adoption is limited. Berdasarkan GitHub stars, forks, download counts, and ecosystem integrations.
The overall Trust Score of 54.1/100 (D) is the weighted combination of these measured signals. It is a measurement, not a pass/fail or suitability judgment — weigh the individual signals against your own requirements.
Who Typically Evaluates Go Roast?
Go Roast is commonly evaluated by:
- Developers and teams working with keamanan tools
- Organizations evaluating AI tools for their stack
- Researchers exploring AI capabilities in this domain
How to read the signals: Go Roast's measured signals (keamanan 0/100, pemeliharaan 1/100, dokumentasi 1/100, community 0/100) are shown above. These are measurements, not a suitability judgment — weigh each signal against the requirements of your own use case and risk tolerance.
How to Verify Go Roast's Safety Yourself
While Nerq provides automated trust analysis, we recommend these additional steps before adopting any software tool:
- Check the source code — Tinjau repository's keamanan policy, open issues, and recent commits for signs of active pemeliharaan.
- Scan dependencies — Use tools like
npm audit,pip-audit, orsnykto check for known vulnerabilities in Go Roast's dependency tree. - Ulasan permissions — Understand what access Go Roast requires. Software tools should follow the principle of least privilege.
- Test in isolation — Run Go Roast 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=go-roast - Tinjau license — Confirm that Go Roast'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 keamanan concerns openly. Low community engagement may indicate limited peer review of the codebase.
Common Safety Concerns with Go Roast
When evaluating whether Go Roast is safe, consider these category-specific risks:
Understand how Go Roast processes, stores, and transmits your data. Tinjau tool's privacy policy and data retention practices, especially for sensitive or proprietary information.
Check Go Roast's dependency tree for known vulnerabilities. Tools with outdated or unmaintained dependencies pose a higher keamanan risk.
Regularly check for updates to Go Roast. Keamanan patches and bug fixes are only effective if you're running the latest version.
If Go Roast 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 Go Roast's license is compatible with your intended use case. Some AI tools have restrictive licenses that limit commercial use, redistribution, or derivative works. Using Go Roast in violation of its license can expose your organization to legal liability.
Go Roast and the EU AI Act
Go Roast is classified as Minimal Risk under the EU AI Act. This is the lowest risk category, meaning it faces minimal regulatory requirements. However, transparency obligations still apply.
Nerq's kepatuhan assessment covers 52 jurisdictions worldwide. For organizations deploying AI tools in regulated environments, understanding these classifications is essential for legal kepatuhan.
Best Practices for Using Go Roast Safely
Whether you're an individual developer or an enterprise team, these practices will help you get the most from Go Roast while minimizing risk:
Periodically review how Go Roast is used in your workflow. Check for unexpected behavior, permissions drift, and kepatuhan with your keamanan policies.
Ensure Go Roast and all its dependencies are running the latest stable versions to benefit from keamanan patches.
Grant Go Roast only the minimum permissions it needs to function. Avoid granting admin or root access.
Subscribe to Go Roast's keamanan advisories and vulnerability disclosures. Use Nerq's API to get automated trust score updates.
Create and maintain a clear policy for how Go Roast is used within your organization, including data handling guidelines and acceptable use cases.
Situations That Warrant Independent Review of Go Roast
Nerq's signals are one input. In the following situations, evaluate Go Roast's measured signals against your own requirements before making a decision:
- Environments handling sensitive or regulated data (healthcare, finance, government)
- Mission-critical systems where downtime has significant business impact
- Deployments with strict regulatory requirements that must be independently validated
For each situation, compare Go Roast's measured trust score of 54.1/100 and its individual signals against your organization's own criteria. Nerq does not assert whether Go Roast is suitable for any particular use.
How Go Roast Compares to Industry Standards
Nerq indexes over 6 million software tools, apps, and packages across dozens of categories. Among keamanan tools, the average Trust Score is 67/100. Go Roast's score of 54.1/100 is below the category average of 67/100.
This suggests that Go Roast trails behind many comparable keamanan tools. Organizations with strict keamanan 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 sedang 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 Go Roast 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 pemeliharaan patterns change, Go Roast'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 keamanan and quality. Conversely, a downward trend may signal reduced pemeliharaan, growing technical debt, or unresolved vulnerabilities. To track Go Roast's score over time, use the Nerq API: GET nerq.ai/v1/preflight?target=go-roast&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 — keamanan, pemeliharaan, dokumentasi, kepatuhan, and community — has evolved independently, providing granular visibility into which aspects of Go Roast are strengthening or weakening over time.
Go Roast vs Alternatif
In the keamanan category, Go Roast scores 54.1/100. There are higher-scoring alternatives available. For a detailed comparison, see:
- Go Roast vs Ciphey — Trust Score: 63.4/100
- Go Roast vs strix — Trust Score: 64.4/100
- Go Roast vs SWE-agent — Trust Score: 76.9/100
Kesimpulan Utama
- Go Roast has a measured Nerq Trust Score of 54.1/100 (D) — a composite of independent signals, not a suitability judgment.
- Among keamanan tools, Go Roast scores below the category average of 67/100 (a positional measurement relative to peers).
- The individual signals — keamanan, pemeliharaan, dokumentasi, kepatuhan, community — are shown above. Weigh them against your own requirements.
- Query the current measured values via Nerq's Preflight API.
Pertanyaan yang Sering Diajukan
Apakah Go Roast Aman?
Berapa skor kepercayaan Go Roast?
Apa alternatif yang lebih aman dari Go Roast?
Seberapa sering skor keamanan Go Roast diperbarui?
Bisakah saya menggunakan Go Roast di lingkungan yang diatur?
Lihat juga
Disclaimer: Skor kepercayaan Nerq adalah penilaian otomatis berdasarkan sinyal yang tersedia secara publik. Ini bukan rekomendasi atau jaminan. Selalu lakukan verifikasi mandiri Anda sendiri.