Is Cc Discussion Safe?

Cc Discussion — Nerq Trust Score 58.0/100 (C grade). Based on analysis of 2 trust dimensions, it is has notable safety concerns. Last updated: 2026-04-30.

Use Cc Discussion with some caution. Cc Discussion is a Python package with a Nerq Trust Score of 58.0/100 (C), based on 3 independent data dimensions. Below the recommended threshold of 70. Security: 90/100. Popularity: 15/100. Data sourced from PyPI registry, GitHub repository, NVD, OSV.dev, and OpenSSF Scorecard. Last updated: 2026-03-20. Machine-readable data (JSON).

Is Cc Discussion safe?

CAUTION — Cc Discussion has a Nerq Trust Score of 58.0/100 (C). It has moderate trust signals but shows some areas of concern that warrant attention. Suitable for development use — review security and maintenance signals before production deployment.

Security Analysis → Cc Discussion Privacy Report →

What is Cc Discussion's trust score?

Cc Discussion has a Nerq Trust Score of 58.0/100, earning a C grade. This score is based on 2 independently measured dimensions including security, maintenance, and community adoption.

Security
90
Popularity
15

What are the key security findings for Cc Discussion?

Cc Discussion's strongest signal is security at 90/100. No known vulnerabilities have been detected. It has not yet reached the Nerq Verified threshold of 70+.

Security score: 90/100 (strong)
Popularity: 15/100 — community adoption

What is Cc Discussion and who maintains it?

Authornogataka
CategoryPython Packages
SourceN/A

Cc Discussion Across Platforms

Same developer/company in other registries:

@nogataka/smart-edit
62/100 · npm
@nogataka/easy-sdd-mcp
48/100 · npm
@nogataka/cloud-code-switcher
48/100 · npm

Similar Pypi by Trust Score

bot-managers (68)cemba-data (68)cdktf-local-build (68)cdk-rds-dump (68)checkatlas (68)
See all safest Pypi →

Compare

Cc Discussion vs bot-managersCc Discussion vs cemba-dataCc Discussion vs cdktf-local-build

Safety Guide: Cc Discussion

What is Cc Discussion?

Cc Discussion is a Python package — Multi-Claude discussion platform with ClaudeCode context.

How to Verify Safety

Run pip audit or safety check. Review on PyPI for download stats.

You can also check the trust score via API: GET /v1/preflight?target=cc-discussion

Key Safety Concerns for Python package

When evaluating any Python package, watch for: dependency vulnerabilities, malicious uploads, maintenance status.

Trust Assessment

Cc Discussion has a Nerq Trust Score of 58/100 (C) and has not yet reached Nerq trust threshold (70+). This score is based on automated analysis of security, maintenance, community, and quality signals.

Key Takeaways

Frequently Asked Questions

Is Cc Discussion Safe?
Use with some caution. cc-discussion with a Nerq Trust Score of 58.0/100 (C). Strongest signal: security (90/100). Score based on Security (90/100), Popularity (15/100).
What is Cc Discussion's trust score?
cc-discussion: 58.0/100 (C). Score based on Security (90/100), Popularity (15/100). Scores update as new data becomes available. API: GET nerq.ai/v1/preflight?target=cc-discussion
What are safer alternatives to Cc Discussion?
In the Python Packages category, more Python packages are being analyzed — check back soon. cc-discussion scores 58.0/100.
Does Cc Discussion have known vulnerabilities?
Nerq checks Cc Discussion against NVD, OSV.dev, and registry-specific vulnerability databases. Current security score: 90/100. Run your package manager's audit command for the latest findings.
Is Cc Discussion actively maintained?
Cc Discussion maintenance score: N/A. Check the repository for recent commit activity and issue responsiveness.
API: /v1/preflight Trust Badge API Docs

See Also

Disclaimer: Nerq trust scores are automated assessments based on publicly available signals. They are not endorsements or guarantees. Always conduct your own due diligence.

We use cookies for analytics and caching. Privacy