Is Captain Dackie Safe? — Trust Score: 49.7/100
According to Nerq's independent analysis of Captain Dackie, this AI assistant has a trust score of 49.7 out of 100, earning a D grade. With 3,062 stars on erc8004, 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-19. Machine-readable data (JSON).
Is Captain Dackie safe?
NO — USE WITH CAUTION — Captain Dackie has a Nerq Trust Score of 49.7/100 (D). 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 Assessment
Caution — Captain Dackie has below-average trust signals. There may be concerns around maintenance frequency, security practices, or ecosystem adoption. Proceed with care and conduct additional due diligence.
Trust Signal Breakdown
Details
| Author | 0xf9d1d63f362bbf1ee08ab9acb36fe74afc48d5f1 |
| Category | AI assistant |
| Stars | 3,062 |
| Source | https://8004scan.io/agents/captain-dackie |
| Protocols | a2a · x402 |
Popular Alternatives in AI assistant
Community Reviews
No reviews yet. Be the first to review Captain Dackie.
What Is Captain Dackie?
Captain Dackie is a AI tool in the AI assistant category. Captain Dackie is an AI agent from Capminal.
As of March 2026, Captain Dackie has 3,062 stars on erc8004, making it a notable 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 Captain Dackie's Safety
Nerq's Trust Score is calculated from 13+ independent signals aggregated into five dimensions. Here is how Captain Dackie performs in each:
- Maintenance (0/100): Captain Dackie 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 documentation, usage examples, and contribution guidelines.
- Community (1/100): Community adoption is limited. Based on GitHub stars, forks, download counts, and ecosystem integrations.
The overall Trust Score of 49.7/100 (D) 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 Captain Dackie?
Captain Dackie is designed for:
- Developers and teams working with AI assistant tools
- Organizations evaluating AI tools for their stack
- Researchers exploring AI capabilities in this domain
Risk guidance: We recommend caution with Captain Dackie. 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 Captain Dackie'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 Captain Dackie's dependency tree. - Review permissions — Understand what access Captain Dackie requires. AI tools should follow the principle of least privilege.
- Test in isolation — Run Captain Dackie 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=Captain Dackie - Review the license — Confirm that Captain Dackie'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 Captain Dackie
When evaluating whether Captain Dackie is safe, consider these category-specific risks:
Understand how Captain Dackie processes, stores, and transmits your data. Review the tool's privacy policy and data retention practices, especially for sensitive or proprietary information.
Check Captain Dackie's dependency tree for known vulnerabilities. Tools with outdated or unmaintained dependencies pose a higher security risk.
Regularly check for updates to Captain Dackie. Security patches and bug fixes are only effective if you're running the latest version.
If Captain Dackie 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 Captain Dackie's license is compatible with your intended use case. Some AI tools have restrictive licenses that limit commercial use, redistribution, or derivative works. Using Captain Dackie in violation of its license can expose your organization to legal liability.
Best Practices for Using Captain Dackie Safely
Whether you're an individual developer or an enterprise team, these practices will help you get the most from Captain Dackie while minimizing risk:
Periodically review how Captain Dackie is used in your workflow. Check for unexpected behavior, permissions drift, and compliance with your security policies.
Ensure Captain Dackie and all its dependencies are running the latest stable versions to benefit from security patches.
Grant Captain Dackie only the minimum permissions it needs to function. Avoid granting admin or root access.
Subscribe to Captain Dackie's security advisories and vulnerability disclosures. Use Nerq's API to get automated trust score updates.
Create and maintain a clear policy for how Captain Dackie is used within your organization, including data handling guidelines and acceptable use cases.
When Should You Avoid Captain Dackie?
Even promising tools aren't right for every situation. Consider avoiding Captain Dackie 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 Captain Dackie's trust score of 49.7/100 meets your organization's risk tolerance. We recommend running a manual security assessment alongside the automated Nerq score.
How Captain Dackie Compares to Industry Standards
Nerq indexes over 204,000 AI agents and tools across dozens of categories. Among AI assistant tools, the average Trust Score is 62/100. Captain Dackie's score of 49.7/100 is below the category average of 62/100.
This suggests that Captain Dackie trails behind many comparable AI assistant 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 Captain Dackie 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, Captain Dackie'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 Captain Dackie's score over time, use the Nerq API: GET nerq.ai/v1/preflight?target=Captain Dackie&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 Captain Dackie are strengthening or weakening over time.
Captain Dackie vs Alternatives
In the AI assistant category, Captain Dackie scores 49.7/100. There are higher-scoring alternatives available. For a detailed comparison, see:
- Captain Dackie vs Neta-Lumina — Trust Score: 60.3/100
- Captain Dackie vs gemma-3-12b-it-heretic — Trust Score: 58.8/100
- Captain Dackie vs kanana-2-30b-a3b-thinking-2601 — Trust Score: 59.2/100
Key Takeaways
- Captain Dackie has a Trust Score of 49.7/100 (D) and is not yet Nerq Verified.
- Captain Dackie has significant trust gaps. Consider higher-rated alternatives unless specific requirements mandate its use.
- Among AI assistant tools, Captain Dackie 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
Add This Badge to YOUR Project
Show users your project is trusted. Add this badge to your README:
[](https://nerq.ai/safe/captain-dackie)
Click to copy. Works on GitHub, GitLab, and any markdown renderer.
pip install nerq && nerq scan
Scans all dependencies for trust scores and security issues.
Related Safety Checks
Disclaimer: Nerq trust scores are automated assessments based on publicly available signals. They are not endorsements or guarantees. Always conduct your own due diligence.