Github Repository Creatorは安全ですか?

Github Repository Creator — Nerq Trust Score 43.4/100 (Eグレード). 3つの信頼次元の分析に基づき、顕著なセキュリティ上の懸念があると評価されています。 最終更新:2026-04-02。

Github Repository Creatorには注意が必要です。 Github Repository Creator is a software tool のNerq信頼スコアは 43.4/100 (E), based on 3 独立したデータ次元. It is below the recommended threshold of 70. メンテナンス: 0/100. Popularity: 0/100. データソース: multiple public sources including package registries, GitHub, NVD, OSV.dev, and OpenSSF Scorecard. 最終更新: 2026-04-02. 機械可読データ(JSON).

Github Repository Creatorは安全ですか?

NO — USE WITH CAUTION — Github Repository Creator のNerq信頼スコアは 43.4/100 (E). 平均以下の信頼シグナルで、重大なギャップがあります in セキュリティ, メンテナンス, or ドキュメント. Not recommended for production use without thorough manual review and additional セキュリティ measures.

セキュリティ分析 → プライバシーレポート →

Github Repository Creatorの信頼スコアは?

Github Repository CreatorのNerq信頼スコアは43.4/100で、Eグレードです。このスコアはセキュリティ、メンテナンス、コミュニティ採用を含む3の独立した次元に基づいています。

メンテナンス
0
ドキュメント
0
人気度
0

Github Repository Creatorの主なセキュリティ調査結果は?

Github Repository Creatorの最も強いシグナルはメンテナンスで0/100です。 既知の脆弱性は検出されていません。 Nerq認証閾値70+にまだ達していません。

メンテナンス: 0/100 — メンテナンス活動が低い
Documentation: 0/100 — 限定的なドキュメント
Popularity: 0/100 — 2 スター( pulsemcp

Github Repository Creatorとは何で、誰が管理していますか?

作者https://github.com/flickleafy/mcp-github-repo-creator
カテゴリcoding
Stars2
Sourcehttps://github.com/flickleafy/mcp-github-repo-creator

codingの人気の代替品

Significant-Gravitas/AutoGPT
74.7/100 · B
github
ollama/ollama
73.8/100 · B
github
langchain-ai/langchain
86.4/100 · A
github
x1xhlol/system-prompts-and-models-of-ai-tools
73.8/100 · B
github
anomalyco/opencode
87.9/100 · A
github

What Is Github Repository Creator?

Github Repository Creator is a software tool in the coding category: Automates GitHub repository creation based on local codebase analysis.. It has 2 GitHub stars. Nerq Trust Score: 43/100 (E).

Nerq independently analyzes every software tool, app, and extension across multiple trust signals including セキュリティ vulnerabilities, メンテナンス activity, license コンプライアンス, and コミュニティでの採用.

How Nerq Assesses Github Repository Creator's Safety

Nerq's Trust Score is calculated from 13+ independent signals aggregated into five 次元. Here is how Github Repository Creator performs in each:

The overall Trust Score of 43.4/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 Github Repository Creator?

Github Repository Creator is designed for:

Risk guidance: We recommend caution with Github Repository Creator. 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 Github Repository Creator'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 Github Repository Creator's dependency tree.
  3. レビュー permissions — Understand what access Github Repository Creator requires. Software tools should follow the principle of least privilege.
  4. Test in isolation — Run Github Repository Creator 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=GitHub Repository Creator
  6. 確認してください license — Confirm that Github Repository Creator'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 Github Repository Creator

When evaluating whether Github Repository Creator is safe, consider these category-specific risks:

Data handling

Understand how Github Repository Creator processes, stores, and transmits your data. 確認してください tool's privacy policy and data retention practices, especially for sensitive or proprietary information.

Dependency セキュリティ

Check Github Repository Creator's dependency tree for known vulnerabilities. Tools with outdated or unmaintained dependencies pose a higher セキュリティ risk.

Update frequency

Regularly check for updates to Github Repository Creator. セキュリティ patches and bug fixes are only effective if you're running the latest version.

Third-party integrations

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

Best Practices for Using Github Repository Creator Safely

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

Conduct regular audits

Periodically review how Github Repository Creator is used in your workflow. Check for unexpected behavior, permissions drift, and コンプライアンス with your セキュリティ policies.

Keep dependencies updated

Ensure Github Repository Creator and all its dependencies are running the latest stable versions to benefit from セキュリティ patches.

Follow least privilege

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

Monitor for セキュリティ advisories

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

When Should You Avoid Github Repository Creator?

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

For each scenario, evaluate whether Github Repository Creatorの信頼スコア 43.4/100 meets your organization's risk tolerance. We recommend running a manual セキュリティ assessment alongside the automated Nerq score.

How Github Repository Creator 比較s to Industry Standards

Nerq indexes over 6 million software tools, apps, and packages across dozens of categories. Among coding tools, the average Trust Score is 62/100. Github Repository Creator's score of 43.4/100 is below the category average of 62/100.

This suggests that Github Repository Creator trails behind many comparable coding 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.

Trust Score History

Nerq continuously monitors Github Repository Creator 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, Github Repository Creator'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 Github Repository Creator's score over time, use the Nerq API: GET nerq.ai/v1/preflight?target=GitHub Repository Creator&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 Github Repository Creator are strengthening or weakening over time.

Github Repository Creator vs 代替品

In the coding category, Github Repository Creator scores 43.4/100. There are higher-scoring alternatives available. For a detailed comparison, see:

重要なポイント

よくある質問

Is Github Repository Creator 安全に使用できます?
注意が必要です。 GitHub Repository Creator のNerq信頼スコアは 43.4/100 (E). 最も強いシグナル: メンテナンス (0/100). スコアの基準: メンテナンス (0/100), 人気度 (0/100), ドキュメント (0/100).
Github Repository Creator's trust scoreとは?
GitHub Repository Creator: 43.4/100 (E). スコアの基準:: メンテナンス (0/100), 人気度 (0/100), ドキュメント (0/100). Scores update as new data becomes available. API: GET nerq.ai/v1/preflight?target=GitHub Repository Creator
Github Repository Creatorのより安全な代替品は?
In the coding category, higher-rated alternatives include Significant-Gravitas/AutoGPT (75/100), ollama/ollama (74/100), langchain-ai/langchain (86/100). GitHub Repository Creator scores 43.4/100.
How often is Github Repository Creator's safety score updated?
Nerq continuously monitors Github Repository Creator and updates its trust score as new data becomes available. データソース: multiple public sources including package registries, GitHub, NVD, OSV.dev, and OpenSSF Scorecard. Current: 43.4/100 (E), last 認証済み 2026-04-02. API: GET nerq.ai/v1/preflight?target=GitHub Repository Creator
Can I use Github Repository Creator in a regulated environment?
Github Repository Creator 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