Безопасен ли Raw Keyring?

Raw Keyring — Nerq Trust Score 54.9/100 (Оценка C-). На основе анализа 1 измерений доверия, считается имеющим заметные проблемы безопасности. Последнее обновление: 2026-06-20.

Используйте Raw Keyring с осторожностью. Raw Keyring — это software tool с рейтингом доверия Nerq 54.9/100 (C-), based on 3 независимых показателей данных. Ниже верифицированного порога Nerq Данные из множественные публичные источники, включая реестры пакетов, GitHub, NVD, OSV.dev и OpenSSF Scorecard. Последнее обновление: 2026-06-20. Машинночитаемые данные (JSON).

Безопасен ли Raw Keyring?

CAUTION — Raw Keyring has a Nerq Trust Score of 54.9/100 (C-). Умеренные сигналы доверия, но есть отдельные области, требующие внимания that warrant attention. Suitable for development use — review безопасность and обслуживание signals before production deployment.

Анализ безопасности → Отчёт о конфиденциальности Raw Keyring →

Каков рейтинг доверия Raw Keyring?

Raw Keyring имеет Nerq Trust Score 54.9/100 с оценкой C-. Этот балл основан на 1 независимо измеренных параметрах, включая безопасность, обслуживание и принятие сообществом.

Соответствие
82

Каковы основные выводы по безопасности Raw Keyring?

Самый сильный сигнал Raw Keyring — соответствие на уровне 82/100. Известных уязвимостей не обнаружено. It has not yet reached the Nerq Verified threshold of 70+.

Соответствие: 82/100 — covers 42 of 52 jurisdictions

Что такое Raw Keyring и кто его поддерживает?

Разработчикaws-crypto-tools-ci-bot
КатегорияUncategorized
Источникhttps://www.npmjs.com/package/@aws-crypto/raw-keyring

Соответствие нормативам

EU AI Act Risk ClassNot assessed
Compliance Score82/100
JurisdictionsAssessed across 52 jurisdictions

Raw Keyring на других платформах

Тот же разработчик/компания в других реестрах:

@aws-crypto/web-crypto-backend
48/100 · npm
@aws-crypto/crc32
48/100 · npm
@aws-crypto/crc32c
48/100 · npm
@aws-crypto/hkdf-node
46/100 · npm
@aws-crypto/decrypt-node
46/100 · npm

What Is Raw Keyring?

Raw Keyring is a software tool in the uncategorized category: The AWS Шифрование SDK for JavaScript is a client-side encryption library designed to make it easy for everyone to encrypt and decrypt data using industry standards and best practices. It uses a data format compatible with the AWS Шифрование SDKs in other. Nerq Trust Score: 55/100 (C-).

Nerq independently analyzes every software tool, app, and extension across multiple trust signals including безопасность vulnerabilities, обслуживание activity, license соответствие, and принятие сообществом.

How Nerq Assesses Raw Keyring's Safety

Nerq's Trust Score is calculated from 13+ independent signals aggregated into five показателей. Here is how Raw Keyring performs in each:

The overall Trust Score of 54.9/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 Raw Keyring?

Raw Keyring is designed for:

Risk guidance: Raw Keyring 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 Raw Keyring'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 Raw Keyring's dependency tree.
  3. Отзыв permissions — Understand what access Raw Keyring requires. Software tools should follow the principle of least privilege.
  4. Test in isolation — Run Raw Keyring 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=@aws-crypto/raw-keyring
  6. Проверьте license — Confirm that Raw Keyring'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 Raw Keyring

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

Data handling

Understand how Raw Keyring processes, stores, and transmits your data. Проверьте tool's privacy policy and data retention practices, especially for sensitive or proprietary information.

Dependency безопасность

Check Raw Keyring's dependency tree for known vulnerabilities. Tools with outdated or unmaintained dependencies pose a higher безопасность risk.

Update frequency

Regularly check for updates to Raw Keyring. Безопасность patches and bug fixes are only effective if you're running the latest version.

Third-party integrations

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

Best Practices for Using Raw Keyring Safely

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

Conduct regular audits

Periodically review how Raw Keyring is used in your workflow. Check for unexpected behavior, permissions drift, and соответствие with your безопасность policies.

Keep dependencies updated

Ensure Raw Keyring and all its dependencies are running the latest stable versions to benefit from безопасность patches.

Follow least privilege

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

Monitor for безопасность advisories

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

When Should You Avoid Raw Keyring?

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

For each scenario, evaluate whether Raw Keyring's trust score of 54.9/100 meets your organization's risk tolerance. We recommend running a manual безопасность assessment alongside the automated Nerq score.

How Raw Keyring Compares to Industry Standards

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

This places Raw Keyring in line with the typical uncategorized 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 Raw Keyring 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, Raw Keyring'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 Raw Keyring's score over time, use the Nerq API: GET nerq.ai/v1/preflight?target=@aws-crypto/raw-keyring&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 Raw Keyring are strengthening or weakening over time.

Основные выводы

Часто задаваемые вопросы

Безопасен ли Raw Keyring?
Используйте с осторожностью. @aws-crypto/raw-keyring с рейтингом доверия Nerq 54.9/100 (C-). Самый сильный сигнал: соответствие (82/100). Рейтинг основан на multiple trust показателей.
Каков рейтинг доверия Raw Keyring?
@aws-crypto/raw-keyring: 54.9/100 (C-). Рейтинг основан на multiple trust показателей. Compliance: 82/100. Баллы обновляются при появлении новых данных. API: GET nerq.ai/v1/preflight?target=@aws-crypto/raw-keyring
Какие более безопасные альтернативы Raw Keyring?
В категории Uncategorized, анализируется ещё больше software tool — проверьте позже. @aws-crypto/raw-keyring scores 54.9/100.
Как часто обновляется оценка безопасности Raw Keyring?
Nerq continuously monitors Raw Keyring and updates its trust score as new data becomes available. Current: 54.9/100 (C-), last верифицировано 2026-06-20. API: GET nerq.ai/v1/preflight?target=@aws-crypto/raw-keyring
Могу ли я использовать Raw Keyring в регулируемой среде?
Raw Keyring не достиг порога верификации Nerq 70. Рекомендуется дополнительная проверка.
API: /v1/preflight Trust Badge API Docs

См. также

Disclaimer: Рейтинги доверия Nerq — это автоматические оценки, основанные на публично доступных сигналах. Они не являются рекомендацией или гарантией. Всегда проводите собственную проверку.

Мы используем файлы cookie для аналитики и кэширования. Конфиденциальность