Czy Githubagentpush Dangerous Projects 1 jest bezpieczny?

Githubagentpush Dangerous Projects 1 — Nerq Trust Score 64.6/100 (Ocena C). Na podstawie analizy 5 wymiarów zaufania, jest ogólnie bezpieczny, ale z pewnymi zastrzeżeniami. Ostatnia aktualizacja: 2026-04-05.

Używaj Githubagentpush Dangerous Projects 1 z ostrożnością. Githubagentpush Dangerous Projects 1 to software tool z wynikiem zaufania Nerq 64.6/100 (C), based on 5 niezależnych wymiarów danych. Poniżej zweryfikowanego progu Nerq Bezpieczeństwo: 0/100. Konserwacja: 1/100. Popularność: 0/100. Dane pochodzą z wiele źródeł publicznych, w tym rejestry pakietów, GitHub, NVD, OSV.dev i OpenSSF Scorecard. Ostatnia aktualizacja: 2026-04-05. Dane odczytywalne maszynowo (JSON).

Czy Githubagentpush Dangerous Projects 1 jest bezpieczny?

CAUTION — Githubagentpush Dangerous Projects 1 has a Nerq Trust Score of 64.6/100 (C). Ma umiarkowane sygnały zaufania, ale wykazuje pewne obszary budzące obawy that warrant attention. Suitable for development use — review bezpieczeństwo and konserwacja signals before production deployment.

Analiza bezpieczeństwa → Raport prywatności Githubagentpush Dangerous Projects 1 →

Jaki jest wynik zaufania Githubagentpush Dangerous Projects 1?

Githubagentpush Dangerous Projects 1 ma Nerq Trust Score 64.6/100 z oceną C. Ten wynik opiera się na 5 niezależnie mierzonych wymiarach, w tym bezpieczeństwie, konserwacji i adopcji społeczności.

Bezpieczeństwo
0
Zgodność
100
Konserwacja
1
Dokumentacja
0
Popularność
0

Jakie są kluczowe ustalenia bezpieczeństwa dla Githubagentpush Dangerous Projects 1?

Najsilniejszy sygnał Githubagentpush Dangerous Projects 1 to zgodność na poziomie 100/100. Nie wykryto znanych luk w zabezpieczeniach. It has not yet reached the Nerq Verified threshold of 70+.

Ocena bezpieczeństwa: 0/100 (słaby)
Konserwacja: 1/100 — niska aktywność konserwacji
Zgodność: 100/100 — covers 52 of 52 jurisdictions
Dokumentacja: 0/100 — ograniczona dokumentacja
Popularność: 0/100 — przyjęcie przez społeczność

Czym jest Githubagentpush Dangerous Projects 1 i kto go utrzymuje?

Autordivyanshu-iitian
KategoriaDevops
Źródłohttps://github.com/divyanshu-iitian/GithubAgentPush-Dangerous-Projects-1
Protocolsrest

Zgodność z przepisami

EU AI Act Risk ClassMINIMAL
Compliance Score100/100
JurisdictionsAssessed across 52 jurisdictions

Popularne alternatywy w devops

ansible/ansible
84.3/100 · A
github
FlowiseAI/Flowise
76.9/100 · B
github
shareAI-lab/learn-claude-code
81.5/100 · A
github
continuedev/continue
84.4/100 · A
github
wshobson/agents
88.7/100 · A
github

What Is Githubagentpush Dangerous Projects 1?

Githubagentpush Dangerous Projects 1 is a DevOps tool: SmartHomeHub is an AI-driven home automation system.. Nerq Trust Score: 65/100 (C).

Nerq independently analyzes every software tool, app, and extension across multiple trust signals including bezpieczeństwo vulnerabilities, konserwacja activity, license zgodność, and przyjęcie przez społeczność.

How Nerq Assesses Githubagentpush Dangerous Projects 1's Safety

Nerq's Trust Score is calculated from 13+ independent signals aggregated into five wymiarów. Here is how Githubagentpush Dangerous Projects 1 performs in each:

The overall Trust Score of 64.6/100 (C) 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 Githubagentpush Dangerous Projects 1?

Githubagentpush Dangerous Projects 1 is designed for:

Risk guidance: Githubagentpush Dangerous Projects 1 is suitable for development and testing environments. Before production deployment, conduct a thorough review of its bezpieczeństwo posture, review the specific trust signals above, and consider whether a higher-scored alternative meets your requirements.

How to Verify Githubagentpush Dangerous Projects 1's Safety Yourself

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

  1. Check the source code — Sprawdź repository's bezpieczeństwo policy, open issues, and recent commits for signs of active konserwacja.
  2. Scan dependencies — Use tools like npm audit, pip-audit, or snyk to check for known vulnerabilities in Githubagentpush Dangerous Projects 1's dependency tree.
  3. Opinia permissions — Understand what access Githubagentpush Dangerous Projects 1 requires. Software tools should follow the principle of least privilege.
  4. Test in isolation — Run Githubagentpush Dangerous Projects 1 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=GithubAgentPush-Dangerous-Projects-1
  6. Sprawdź license — Confirm that Githubagentpush Dangerous Projects 1'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 bezpieczeństwo concerns openly. Low community engagement may indicate limited peer review of the codebase.

Common Safety Concerns with Githubagentpush Dangerous Projects 1

When evaluating whether Githubagentpush Dangerous Projects 1 is safe, consider these category-specific risks:

Data handling

Understand how Githubagentpush Dangerous Projects 1 processes, stores, and transmits your data. Sprawdź tool's privacy policy and data retention practices, especially for sensitive or proprietary information.

Dependency bezpieczeństwo

Check Githubagentpush Dangerous Projects 1's dependency tree for known vulnerabilities. Tools with outdated or unmaintained dependencies pose a higher bezpieczeństwo risk.

Update frequency

Regularly check for updates to Githubagentpush Dangerous Projects 1. Bezpieczeństwo patches and bug fixes are only effective if you're running the latest version.

Third-party integrations

If Githubagentpush Dangerous Projects 1 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 zgodność

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

Githubagentpush Dangerous Projects 1 and the EU AI Act

Githubagentpush Dangerous Projects 1 is classified as Minimal Risk under the EU AI Act. This is the lowest risk category, meaning it faces minimal regulatory requirements. However, transparency obligations still apply.

Nerq's zgodność assessment covers 52 jurisdictions worldwide. For organizations deploying AI tools in regulated environments, understanding these classifications is essential for legal zgodność.

Best Practices for Using Githubagentpush Dangerous Projects 1 Safely

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

Conduct regular audits

Periodically review how Githubagentpush Dangerous Projects 1 is used in your workflow. Check for unexpected behavior, permissions drift, and zgodność with your bezpieczeństwo policies.

Keep dependencies updated

Ensure Githubagentpush Dangerous Projects 1 and all its dependencies are running the latest stable versions to benefit from bezpieczeństwo patches.

Follow least privilege

Grant Githubagentpush Dangerous Projects 1 only the minimum permissions it needs to function. Avoid granting admin or root access.

Monitor for bezpieczeństwo advisories

Subscribe to Githubagentpush Dangerous Projects 1's bezpieczeństwo 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 Githubagentpush Dangerous Projects 1 is used within your organization, including data handling guidelines and acceptable use cases.

When Should You Avoid Githubagentpush Dangerous Projects 1?

Even promising tools aren't right for every situation. Consider avoiding Githubagentpush Dangerous Projects 1 in these scenarios:

For each scenario, evaluate whether Githubagentpush Dangerous Projects 1's trust score of 64.6/100 meets your organization's risk tolerance. We recommend running a manual bezpieczeństwo assessment alongside the automated Nerq score.

How Githubagentpush Dangerous Projects 1 Compares to Industry Standards

Nerq indexes over 6 million software tools, apps, and packages across dozens of categories. Among DevOps tools, the average Trust Score is 63/100. Githubagentpush Dangerous Projects 1's score of 64.6/100 is above the category average of 63/100.

This positions Githubagentpush Dangerous Projects 1 favorably among DevOps tools. While it outperforms the average, there is still room for improvement in certain trust wymiarów.

Industry benchmarks matter because they contextualize a tool's safety profile. A score that looks umiarkowany 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 Githubagentpush Dangerous Projects 1 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 konserwacja patterns change, Githubagentpush Dangerous Projects 1'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 bezpieczeństwo and quality. Conversely, a downward trend may signal reduced konserwacja, growing technical debt, or unresolved vulnerabilities. To track Githubagentpush Dangerous Projects 1's score over time, use the Nerq API: GET nerq.ai/v1/preflight?target=GithubAgentPush-Dangerous-Projects-1&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 — bezpieczeństwo, konserwacja, dokumentacja, zgodność, and community — has evolved independently, providing granular visibility into which aspects of Githubagentpush Dangerous Projects 1 are strengthening or weakening over time.

Githubagentpush Dangerous Projects 1 vs Alternatywy

In the devops category, Githubagentpush Dangerous Projects 1 scores 64.6/100. There are higher-scoring alternatives available. For a detailed comparison, see:

Kluczowe wnioski

Często zadawane pytania

Czy Githubagentpush Dangerous Projects 1 jest bezpieczny?
Używaj z ostrożnością. GithubAgentPush-Dangerous-Projects-1 z wynikiem zaufania Nerq 64.6/100 (C). Najsilniejszy sygnał: zgodność (100/100). Wynik oparty na Bezpieczeństwo (0/100), Konserwacja (1/100), Popularność (0/100), Dokumentacja (0/100).
Jaki jest wynik zaufania Githubagentpush Dangerous Projects 1?
GithubAgentPush-Dangerous-Projects-1: 64.6/100 (C). Wynik oparty na Bezpieczeństwo (0/100), Konserwacja (1/100), Popularność (0/100), Dokumentacja (0/100). Compliance: 100/100. Oceny aktualizują się, gdy pojawiają się nowe dane. API: GET nerq.ai/v1/preflight?target=GithubAgentPush-Dangerous-Projects-1
What are safer alternatives to Githubagentpush Dangerous Projects 1?
W kategorii Devops, higher-rated alternatives include ansible/ansible (84/100), FlowiseAI/Flowise (77/100), shareAI-lab/learn-claude-code (82/100). GithubAgentPush-Dangerous-Projects-1 scores 64.6/100.
How often is Githubagentpush Dangerous Projects 1's safety score updated?
Nerq continuously monitors Githubagentpush Dangerous Projects 1 and updates its trust score as new data becomes available. Dane pochodzą z wiele źródeł publicznych, w tym rejestry pakietów, GitHub, NVD, OSV.dev i OpenSSF Scorecard. Current: 64.6/100 (C), last zweryfikowane 2026-04-05. API: GET nerq.ai/v1/preflight?target=GithubAgentPush-Dangerous-Projects-1
Can I use Githubagentpush Dangerous Projects 1 in a regulated environment?
Githubagentpush Dangerous Projects 1 has not reached the Nerq Verified threshold of 70. Additional due diligence is recommended for regulated environments.
API: /v1/preflight Trust Badge API Docs

Zobacz także

Disclaimer: Wyniki zaufania Nerq to zautomatyzowane oceny oparte na publicznie dostępnych sygnałach. Nie stanowią rekomendacji ani gwarancji. Zawsze przeprowadzaj własną weryfikację.

Używamy plików cookie do analiz i buforowania. Prywatność