Doctorgpt은(는) 안전한가요?

Doctorgpt — Nerq Trust Score 56.0/100 (D 등급). 4개의 신뢰 차원 분석 결과, 주목할 만한 보안 우려가 있음으로 평가됩니다. 마지막 업데이트: 2026-04-07.

Doctorgpt을(를) 주의하며 사용하세요. Doctorgpt 은(는) software tool입니다 Nerq 신뢰 점수 56.0/100 (D), 4개의 독립적으로 측정된 데이터 차원 기반. Nerq 인증 기준 미달 유지보수: 0/100. 인기도: 0/100. 패키지 레지스트리, GitHub, NVD, OSV.dev, OpenSSF Scorecard를 포함한 여러 공개 소스에서 수집된 데이터. 마지막 업데이트: 2026-04-07. 기계 판독 가능 데이터 (JSON).

Doctorgpt은(는) 안전한가요?

CAUTION — Doctorgpt has a Nerq Trust Score of 56.0/100 (D). 보통 수준의 신뢰 신호가 있지만 일부 우려 사항이 있습니다 that warrant attention. Suitable for development use — review 보안 and 유지보수 signals before production deployment.

보안 분석 → Doctorgpt 개인정보 보고서 →

Doctorgpt의 신뢰 점수는?

Doctorgpt의 Nerq 신뢰 점수는 56.0/100이며 D 등급입니다. 이 점수는 보안, 유지보수, 커뮤니티 채택을 포함한 4개의 독립적으로 측정된 차원을 기반으로 합니다.

규정 준수
100
유지보수
0
문서화
0
인기도
0

Doctorgpt의 주요 보안 발견 사항은?

Doctorgpt의 가장 강한 신호는 규정 준수이며 100/100입니다. 알려진 취약점이 감지되지 않았습니다. 아직 Nerq 인증 임계값 70+에 도달하지 못했습니다.

유지보수: 0/100 — 낮은 유지관리 활동
규정 준수: 100/100 — covers 52 of 52 관할권s
문서화: 0/100 — 제한적 문서화
인기도: 0/100 — 16 스타 수: huggingface space full

Doctorgpt은(는) 무엇이며 누가 관리하나요?

개발자llSourcell
카테고리Health
스타16
출처https://huggingface.co/spaces/llSourcell/doctorGPT
Protocolshuggingface_hub

규정 준수

EU AI Act Risk ClassNot assessed
Compliance Score100/100
JurisdictionsAssessed across 52 관할권s

health의 인기 대안

shibing624/MedicalGPT
62.6/100 · C
github
OpenHealthForAll/open-health
62.6/100 · C
github
FreedomIntelligence/Awesome-AI4Med
62.6/100 · C
github
scutcyr/BianQue
59.0/100 · D
github
huifer/WellAlly-health
61.4/100 · C
github

다른 플랫폼의 Doctorgpt

다른 레지스트리의 동일 개발자/회사:

github.com/llSourcell/kerala
46/100 · go

What Is Doctorgpt?

Doctorgpt is a software tool in the health category: AI-driven health assistant. It has 16 GitHub stars. Nerq Trust Score: 56/100 (D).

Nerq independently analyzes every software tool, app, and extension across multiple trust signals including 보안 vulnerabilities, 유지보수 activity, license 규정 준수, and 커뮤니티 채택.

How Nerq Assesses Doctorgpt's Safety

Nerq's Trust Score is calculated from 13+ independent signals aggregated into five 차원. Here is how Doctorgpt performs in each:

The overall Trust Score of 56.0/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 Doctorgpt?

Doctorgpt is designed for:

Risk guidance: Doctorgpt is suitable for development and testing environments. Before production deployment, conduct a thorough review of its 보안 posture, review the specific trust signals above, and consider whether a higher-scored alternative meets your requirements.

How to Verify Doctorgpt's Safety Yourself

While Nerq provides automated trust analysis, we recommend these additional steps before adopting any software tool:

  1. Check the source code — 다음을 검토하세요: repository 보안 policy, open issues, and recent commits for signs of active 유지보수.
  2. Scan dependencies — Use tools like npm audit, pip-audit, or snyk to check for known vulnerabilities in Doctorgpt's dependency tree.
  3. 리뷰 permissions — Understand what access Doctorgpt requires. Software tools should follow the principle of least privilege.
  4. Test in isolation — Run Doctorgpt in a sandboxed environment before granting access to production data or systems.
  5. Monitor continuously — Use Nerq's API to set up automated trust checks: GET nerq.ai/v1/preflight?target=doctorGPT
  6. 다음을 검토하세요: license — Confirm that Doctorgpt'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.
  7. 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 보안 concerns openly. Low community engagement may indicate limited peer review of the codebase.

Common Safety Concerns with Doctorgpt

When evaluating whether Doctorgpt is safe, consider these category-specific risks:

Data handling

Understand how Doctorgpt processes, stores, and transmits your data. 다음을 검토하세요: tool's privacy policy and data retention practices, especially for sensitive or proprietary information.

Dependency 보안

Check Doctorgpt's dependency tree for known vulnerabilities. Tools with outdated or unmaintained dependencies pose a higher 보안 risk.

Update frequency

Regularly check for updates to Doctorgpt. 보안 patches and bug fixes are only effective if you're running the latest version.

Third-party integrations

If Doctorgpt 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.

License and IP 규정 준수

Verify that Doctorgpt's license is compatible with your intended use case. Some AI tools have restrictive licenses that limit commercial use, redistribution, or derivative works. Using Doctorgpt in violation of its license can expose your organization to legal liability.

Best Practices for Using Doctorgpt Safely

Whether you're an individual developer or an enterprise team, these practices will help you get the most from Doctorgpt while minimizing risk:

Conduct regular audits

Periodically review how Doctorgpt is used in your workflow. Check for unexpected behavior, permissions drift, and 규정 준수 with your 보안 policies.

Keep dependencies updated

Ensure Doctorgpt and all its dependencies are running the latest stable versions to benefit from 보안 patches.

Follow least privilege

Grant Doctorgpt only the minimum permissions it needs to function. Avoid granting admin or root access.

Monitor for 보안 advisories

Subscribe to Doctorgpt's 보안 advisories and vulnerability disclosures. Use Nerq's API to get automated trust score updates.

Document usage policies

Create and maintain a clear policy for how Doctorgpt is used within your organization, including data handling guidelines and acceptable use cases.

When Should You Avoid Doctorgpt?

Even promising tools aren't right for every situation. Consider avoiding Doctorgpt in these scenarios:

For each scenario, evaluate whether Doctorgpt's trust score of 56.0/100 meets your organization's risk tolerance. We recommend running a manual 보안 assessment alongside the automated Nerq score.

How Doctorgpt Compares to Industry Standards

Nerq indexes over 6 million software tools, apps, and packages across dozens of categories. Among health tools, the average Trust Score is 62/100. Doctorgpt's score of 56.0/100 is near the category average of 62/100.

This places Doctorgpt in line with the typical health tool tool. It meets baseline expectations but does not distinguish itself from peers on trust metrics.

Industry benchmarks matter because they contextualize a tool's safety profile. A score that looks 보통 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 Doctorgpt 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 유지보수 patterns change, Doctorgpt'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 보안 and quality. Conversely, a downward trend may signal reduced 유지보수, growing technical debt, or unresolved vulnerabilities. To track Doctorgpt's score over time, use the Nerq API: GET nerq.ai/v1/preflight?target=doctorGPT&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 — 보안, 유지보수, 문서화, 규정 준수, and community — has evolved independently, providing granular visibility into which aspects of Doctorgpt are strengthening or weakening over time.

Doctorgpt vs 대안

In the health category, Doctorgpt scores 56.0/100. There are higher-scoring alternatives available. For a detailed comparison, see:

주요 요점

자주 묻는 질문

Doctorgpt은(는) 안전한가요?
주의하며 사용하세요. doctorGPT Nerq 신뢰 점수 56.0/100 (D). 가장 강력한 신호: 규정 준수 (100/100). 유지보수 (0/100), 인기도 (0/100), 문서화 (0/100) 기반 점수.
Doctorgpt의 신뢰 점수는?
doctorGPT: 56.0/100 (D). 유지보수 (0/100), 인기도 (0/100), 문서화 (0/100) 기반 점수. Compliance: 100/100. 새로운 데이터가 제공되면 점수가 업데이트됩니다. API: GET nerq.ai/v1/preflight?target=doctorGPT
Doctorgpt의 더 안전한 대안은?
Health 카테고리에서, higher-rated alternatives include shibing624/MedicalGPT (63/100), OpenHealthForAll/open-health (63/100), FreedomIntelligence/Awesome-AI4Med (63/100). doctorGPT scores 56.0/100.
Doctorgpt의 보안 점수는 얼마나 자주 업데이트되나요?
Nerq continuously monitors Doctorgpt and updates its trust score as new data becomes available. Current: 56.0/100 (D), last 인증됨 2026-04-07. API: GET nerq.ai/v1/preflight?target=doctorGPT
규제 환경에서 Doctorgpt을 사용할 수 있나요?
Doctorgpt은 Nerq 인증 임계값 70에 도달하지 못했습니다. 추가 검토가 권장됩니다.
API: /v1/preflight Trust Badge API Docs

참고 항목

Disclaimer: Nerq 신뢰 점수는 공개적으로 사용 가능한 신호를 기반으로 한 자동 평가입니다. 추천이나 보증이 아닙니다. 항상 직접 확인하세요.

분석 및 캐싱을 위해 쿠키를 사용합니다. 개인정보