Current Time은(는) 안전한가요?

Current Time — Nerq 신뢰 점수 42.5/100 (E 등급). 3개의 신뢰 차원 분석 결과, 주목할 만한 보안 우려가 있음으로 평가됩니다. 마지막 업데이트: 2026-04-02.

Current Time에 대해 주의하세요. Current Time is a software tool Nerq 신뢰 점수 42.5/100 (E), based on 3 독립적인 데이터 차원. 권장 기준인 70 미만입니다. 유지보수: 0/100. Popularity: 0/100. 데이터 출처: multiple public sources including package registries, GitHub, NVD, OSV.dev, and OpenSSF Scorecard. 최종 업데이트: 2026-04-02. 기계 판독 가능 데이터 (JSON).

Current Time은(는) 안전한가요?

아니오 — 주의하며 사용 — Current Time 의 Nerq 신뢰 점수는 42.5/100 (E). 보안, 유지보수 또는 문서화에서 심각한 격차와 함께 평균 이하의 신뢰 신호가 있습니다. 철저한 수동 검토 및 추가 보안 조치 없이는 프로덕션 사용이 권장되지 않습니다.

보안 분석 → {name} 개인정보 보고서 →

Current Time의 신뢰 점수는?

Current Time 의 Nerq 신뢰 점수는 42.5/100, earning a E grade. This score is based on 3 independently measured 차원 including 보안, 유지보수, and 커뮤니티 채택.

유지보수
0
문서화
0
인기도
0

Current Time의 주요 보안 발견 사항은?

Current Time's strongest signal is 유지보수 at 0/100. No known vulnerabilities have been detected. It has not yet reached the Nerq Verified threshold of 70+.

유지보수: 0/100 — 유지보수 활동 저조
Documentation: 0/100 — 제한된 문서화
Popularity: 0/100 — 5 스타 수: pulsemcp

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

개발자https://github.com/phialsbasement/mcp-time
카테고리other
스타5
출처https://github.com/songjiayang/eino-mcp

other의 인기 대안

Developer-Y/cs-video-courses
69.3/100 · C
github
binhnguyennus/awesome-scalability
71.8/100 · B
github
obra/superpowers
71.8/100 · B
github
ultralytics/yolov5
71.8/100 · B
github
deepfakes/faceswap
69.3/100 · C
github

What Is Current Time?

Current Time is a software tool in the other category: Provides current time information across different timezones.. It has 5 GitHub stars. Nerq 신뢰 점수: 42/100 (E).

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

How Nerq Assesses Current Time's Safety

Nerq's 신뢰 점수 is calculated from 13+ independent signals aggregated into five 차원. Here is how Current Time performs in each:

The overall 신뢰 점수 of 42.5/100 (E) 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 Current Time?

Current Time is designed for:

Risk guidance: We recommend caution with Current Time. The low trust score suggests potential risks in 보안, 유지보수, or community support. Consider using a more established alternative for any production or sensitive workload.

How to Verify Current Time'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 Current Time's dependency tree.
  3. 리뷰 permissions — Understand what access Current Time requires. Software tools should follow the principle of least privilege.
  4. Test in isolation — Run Current Time 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=Current Time
  6. 다음을 검토하세요: license — Confirm that Current Time'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 Current Time

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

Data handling

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

Dependency 보안

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

Update frequency

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

Third-party integrations

If Current Time 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 Current Time's license is compatible with your intended use case. Some AI tools have restrictive licenses that limit commercial use, redistribution, or derivative works. Using Current Time in violation of its license can expose your organization to legal liability.

Best Practices for Using Current Time Safely

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

Conduct regular audits

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

Keep dependencies updated

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

Follow least privilege

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

Monitor for 보안 advisories

Subscribe to Current Time'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 Current Time is used within your organization, including data handling guidelines and acceptable use cases.

When Should You Avoid Current Time?

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

For each scenario, evaluate whether Current Time의 신뢰 점수 42.5/100 meets your organization's risk tolerance. We recommend running a manual 보안 assessment alongside the automated Nerq score.

How Current Time Compares to Industry Standards

Nerq indexes over 6 million software tools, apps, and packages across dozens of categories. Among other tools, the average 신뢰 점수 is 62/100. Current Time's score of 42.5/100 is below the category average of 62/100.

This suggests that Current Time trails behind many comparable other tools. Organizations with strict 보안 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 보통 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.

신뢰 점수 History

Nerq continuously monitors Current Time and recalculates its 신뢰 점수 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, Current Time'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 Current Time's score over time, use the Nerq API: GET nerq.ai/v1/preflight?target=Current Time&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 Current Time are strengthening or weakening over time.

Current Time vs 대안

other 카테고리에서, Current Time의 점수는 42.5/100입니다. There are higher-scoring alternatives available. For a detailed comparison, see:

주요 요점

자주 묻는 질문

Current Time은(는) 사용하기에 안전한가요?
주의하세요. Current Time 의 Nerq 신뢰 점수는 42.5/100 (E). 가장 강력한 신호: 유지보수 (0/100). 점수 기반: 유지보수 (0/100), 인기도 (0/100), 문서화 (0/100).
Current Time's trust score이(가) 무엇인가요?
Current Time: 42.5/100 (E). 점수 기반:: 유지보수 (0/100), 인기도 (0/100), 문서화 (0/100). 새로운 데이터가 제공되면 점수가 업데이트됩니다. API: GET nerq.ai/v1/preflight?target=Current Time
Current Time의 더 안전한 대안은 무엇인가요?
other 카테고리에서, 더 높은 평가를 받은 대안으로는 Developer-Y/cs-video-courses (69/100), binhnguyennus/awesome-scalability (72/100), obra/superpowers (72/100). Current Time의 점수는 42.5/100입니다.
How often is Current Time's safety score updated?
Nerq continuously monitors Current Time and updates its trust score as new data becomes available. 데이터 출처: multiple public sources including package registries, GitHub, NVD, OSV.dev, and OpenSSF Scorecard. Current: 42.5/100 (E), last 인증됨 2026-04-02. API: GET nerq.ai/v1/preflight?target=Current Time
Current Time을(를) 규제 환경에서 사용할 수 있나요?
Current Time has not reached the Nerq Verified threshold of 70. Additional due diligence is recommended for regulated environments.
API: /v1/preflight Trust Badge API Docs

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

We use cookies for analytics and caching. 개인정보 Policy