Current Time Güvenli mi?

Current Time — Nerq Trust Score 42.5/100 (E notu). 3 güven boyutunun analizine dayanarak, dikkate değer güvenlik endişeleri var olarak değerlendirilmektedir. Son güncelleme: 2026-04-06.

Current Time konusunda dikkatli olun. Current Time bir software tool Nerq Güven Puanı ile 42.5/100 (E), based on 3 bağımsız veri boyutu. Nerq Doğrulanmış eşiğinin altında Bakım: 0/100. Popülerlik: 0/100. Veriler şuradan alınmıştır: paket kayıtları, GitHub, NVD, OSV.dev ve OpenSSF Scorecard dahil birden fazla genel kaynak. Son güncelleme: 2026-04-06. Makine tarafından okunabilir veri (JSON).

Current Time Güvenli mi?

NO — USE WITH CAUTION — Current Time has a Nerq Trust Score of 42.5/100 (E). Ortalama altı güven sinyalleri ve önemli boşluklara sahiptir in güvenlik, bakım, or dokümantasyon. Not recommended for production use without thorough manual review and additional güvenlik measures.

Güvenlik Analizi → Current Time Gizlilik Raporu →

Current Time'in güven puanı nedir?

Current Time'in Nerq Güven Puanı 42.5/100 olup E notu almıştır. Bu puan 3 bağımsız olarak ölçülen boyuta dayanmaktadır.

Bakım
0
Dokümantasyon
0
Popülerlik
0

Current Time için temel güvenlik bulguları nelerdir?

Current Time'in en güçlü sinyali 0/100 ile bakım'dir. Bilinen güvenlik açığı tespit edilmemiştir. Henüz Nerq Doğrulanmış eşiğine (70+) ulaşamamıştır.

Bakım: 0/100 — düşük bakım etkinliği
Dokümantasyon: 0/100 — sınırlı belgeleme
Popülerlik: 0/100 — 5 yıldız pulsemcp

Current Time nedir ve kim tarafından yönetilmektedir?

Geliştiricihttps://github.com/phialsbasement/mcp-time
KategoriOther
Yıldız5
Kaynakhttps://github.com/songjiayang/eino-mcp

other kategorisindeki popüler alternatifler

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 Trust Score: 42/100 (E).

Nerq independently analyzes every software tool, app, and extension across multiple trust signals including güvenlik vulnerabilities, bakım activity, license uyumluluk, and topluluk benimsemesi.

How Nerq Assesses Current Time's Safety

Nerq's Trust Score is calculated from 13+ independent signals aggregated into five boyut. Here is how Current Time performs in each:

The overall Trust Score 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 güvenlik, bakım, 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 — İnceleyin repository güvenlik policy, open issues, and recent commits for signs of active bakım.
  2. Scan dependencies — Use tools like npm audit, pip-audit, or snyk to check for known vulnerabilities in Current Time's dependency tree.
  3. İnceleme 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. İnceleyin 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 güvenlik 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. İnceleyin tool's privacy policy and data retention practices, especially for sensitive or proprietary information.

Dependency güvenlik

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

Update frequency

Regularly check for updates to Current Time. Güvenlik 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 uyumluluk

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 uyumluluk with your güvenlik policies.

Keep dependencies updated

Ensure Current Time and all its dependencies are running the latest stable versions to benefit from güvenlik patches.

Follow least privilege

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

Monitor for güvenlik advisories

Subscribe to Current Time's güvenlik 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's trust score of 42.5/100 meets your organization's risk tolerance. We recommend running a manual güvenlik 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 Trust Score 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 güvenlik 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 orta 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 Current Time 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 bakım 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 güvenlik and quality. Conversely, a downward trend may signal reduced bakım, 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 — güvenlik, bakım, dokümantasyon, uyumluluk, and community — has evolved independently, providing granular visibility into which aspects of Current Time are strengthening or weakening over time.

Current Time vs Alternatifler

In the other category, Current Time scores 42.5/100. There are higher-scoring alternatives available. For a detailed comparison, see:

Temel Çıkarımlar

Sık Sorulan Sorular

Current Time Güvenli mi?
Dikkatli olun. Current Time Nerq Güven Puanı ile 42.5/100 (E). En güçlü sinyal: bakım (0/100). Puan şuna dayalı: Bakım (0/100), Popülerlik (0/100), Dokümantasyon (0/100).
Current Time'in güven puanı nedir?
Current Time: 42.5/100 (E). Puan şuna dayalı: Bakım (0/100), Popülerlik (0/100), Dokümantasyon (0/100). Yeni veriler mevcut olduğunda puanlar güncellenir. API: GET nerq.ai/v1/preflight?target=Current Time
Current Time için daha güvenli alternatifler nelerdir?
Other kategorisinde, higher-rated alternatives include Developer-Y/cs-video-courses (69/100), binhnguyennus/awesome-scalability (72/100), obra/superpowers (72/100). Current Time scores 42.5/100.
Current Time güvenlik puanı ne sıklıkla güncellenir?
Nerq continuously monitors Current Time and updates its trust score as new data becomes available. Current: 42.5/100 (E), last doğrulanmış 2026-04-06. API: GET nerq.ai/v1/preflight?target=Current Time
Current Time'i düzenlenmiş bir ortamda kullanabilir miyim?
Current Time Nerq doğrulama eşiği olan 70'e ulaşmadı. Ek inceleme önerilir.
API: /v1/preflight Trust Badge API Docs

Ayrıca bakınız

Disclaimer: Nerq güven puanları, kamuya açık sinyallere dayanan otomatik değerlendirmelerdir. Tavsiye veya garanti niteliğinde değildir. Her zaman kendi doğrulamanızı yapın.

Analiz ve önbelleğe alma için çerezler kullanıyoruz. Gizlilik