Is Permshell Safe?
Permshell — Nerq Trust Score 38.0/100 (E grade). Score based on 3 independent trust signals.
Permshell is a software tool with a Nerq Trust Score of 38.0/100 (E), based on 3 independent data dimensions. Maintenance: 0/100. Popularity: 0/100. Data sourced from multiple public sources including package registries, GitHub, NVD, OSV.dev, and OpenSSF Scorecard. Last updated: n/a. Machine-readable data (JSON).
Is Permshell safe?
Trust Score Breakdown — Permshell has a Nerq Trust Score of 38.0/100 (E). Measured across 3 independent trust signals.
What is Permshell's trust score?
Permshell has a Nerq Trust Score of 38.0/100, earning a E grade. This score is based on 3 independently measured dimensions including security, maintenance, and community adoption.
What are the key security findings for Permshell?
Permshell's strongest signal is maintenance at 0/100. No known vulnerabilities have been detected.
What is Permshell and who maintains it?
| Author | https://github.com/mcollina/perm-shell-mcp |
| Category | Security |
| Stars | 1 |
| Source | https://github.com/mcollina/perm-shell-mcp |
Popular Alternatives in security
What Is Permshell?
Permshell is a security tool: PermShell enables secure local system access through user-approved shell command execution.. It has 1 GitHub stars. Nerq Trust Score: 38/100 (E).
Nerq independently analyzes every software tool, app, and extension across multiple trust signals including security vulnerabilities, maintenance activity, license compliance, and community adoption.
How Nerq Assesses Permshell's Safety
Nerq's Trust Score is calculated from 13+ independent signals aggregated into five dimensions. Here is how Permshell performs in each:
- Maintenance (0/100): Permshell 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 (0/100): Community adoption is limited. Based on GitHub stars, forks, download counts, and ecosystem integrations.
The overall Trust Score of 38.0/100 (E) 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 Permshell?
Permshell is commonly evaluated by:
- Developers and teams working with security tools
- Organizations evaluating AI tools for their stack
- Researchers exploring AI capabilities in this domain
How to read the signals: Permshell's measured signals (maintenance 0/100, documentation 0/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 Permshell's Safety Yourself
While Nerq provides automated trust analysis, we recommend these additional steps before adopting any software 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 Permshell's dependency tree. - Review permissions — Understand what access Permshell requires. Software tools should follow the principle of least privilege.
- Test in isolation — Run Permshell 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=PermShell - Review the license — Confirm that Permshell'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 Permshell
When evaluating whether Permshell is safe, consider these category-specific risks:
Understand how Permshell processes, stores, and transmits your data. Review the tool's privacy policy and data retention practices, especially for sensitive or proprietary information.
Check Permshell's dependency tree for known vulnerabilities. Tools with outdated or unmaintained dependencies pose a higher security risk.
Regularly check for updates to Permshell. Security patches and bug fixes are only effective if you're running the latest version.
If Permshell 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 Permshell's license is compatible with your intended use case. Some AI tools have restrictive licenses that limit commercial use, redistribution, or derivative works. Using Permshell in violation of its license can expose your organization to legal liability.
Best Practices for Using Permshell Safely
Whether you're an individual developer or an enterprise team, these practices will help you get the most from Permshell while minimizing risk:
Periodically review how Permshell is used in your workflow. Check for unexpected behavior, permissions drift, and compliance with your security policies.
Ensure Permshell and all its dependencies are running the latest stable versions to benefit from security patches.
Grant Permshell only the minimum permissions it needs to function. Avoid granting admin or root access.
Subscribe to Permshell's security advisories and vulnerability disclosures. Use Nerq's API to get automated trust score updates.
Create and maintain a clear policy for how Permshell is used within your organization, including data handling guidelines and acceptable use cases.
Situations That Warrant Independent Review of Permshell
Nerq's signals are one input. In the following situations, evaluate Permshell'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 Permshell's measured trust score of 38.0/100 and its individual signals against your organization's own criteria. Nerq does not assert whether Permshell is suitable for any particular use.
How Permshell Compares to Industry Standards
Nerq indexes over 6 million software tools, apps, and packages across dozens of categories. Among security tools, the average Trust Score is 67/100. Permshell's score of 38.0/100 is below the category average of 67/100.
This suggests that Permshell trails behind many comparable security 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 Permshell 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, Permshell'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 Permshell's score over time, use the Nerq API: GET nerq.ai/v1/preflight?target=PermShell&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 Permshell are strengthening or weakening over time.
Permshell vs Alternatives
In the security category, Permshell scores 38.0/100. There are higher-scoring alternatives available. For a detailed comparison, see:
- Permshell vs Ciphey — Trust Score: 63.4/100
- Permshell vs strix — Trust Score: 64.4/100
- Permshell vs SWE-agent — Trust Score: 76.9/100
Key Takeaways
- Permshell has a measured Nerq Trust Score of 38.0/100 (E) — a composite of independent signals, not a suitability judgment.
- Among security tools, Permshell scores below the category average of 67/100 (a positional measurement relative to peers).
- The individual signals — security, maintenance, documentation, compliance, community — are shown above. Weigh them against your own requirements.
- Query the current measured values via Nerq's Preflight API.
Frequently Asked Questions
Is Permshell Safe?
What is Permshell's trust score?
What are safer alternatives to Permshell?
How often is Permshell's safety score updated?
Can I use Permshell in a regulated environment?
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.