¿Es Protocol Http Seguro?

Protocol Http — Nerq Trust Score 86.0/100 (Grado A). Basado en el análisis de 2 dimensiones de confianza, se considera seguro de usar. Última actualización: 2026-04-05.

Sí, Protocol Http es seguro para usar. Protocol Http es un paquete npm ([![NPM version](https://img) con un Nerq Trust Score de 86.0/100 (A), basado en 3 dimensiones de datos independientes. It is recomendado para uso en producción. Security: 90/100. Popularity: 100/100. Datos de npm registry, GitHub repository, NVD, OSV.dev, and OpenSSF Scorecard. Última actualización: 2026-04-05. Datos legibles por máquina (JSON).

¿Es Protocol Http Seguro?

YES — Protocol Http has a Nerq Trust Score of 86.0/100 (A). It meets Nerq's trust threshold with strong signals across security, maintenance, and community adoption. Recomendado para uso en producción — review the full report below for specific considerations.

Análisis de Seguridad → Informe de Privacidad de {name} →

¿Cuál es la puntuación de confianza de Protocol Http?

Protocol Http tiene una Puntuación de Confianza Nerq de 86.0/100, obteniendo un grado A. Esta puntuación se basa en 2 dimensiones medidas independientemente.

Seguridad
90
Popularidad
100

¿Cuáles son los hallazgos de seguridad clave de Protocol Http?

La señal más fuerte de Protocol Http es popularidad con 100/100. No se han detectado vulnerabilidades conocidas. Cumple con el umbral verificado de Nerq de 70+.

Security score: 90/100 (strong)
Popularity: 100/100 — community adoption

¿Qué es Protocol Http y quién lo mantiene?

Autortrivikr-aws
Categoríanpm
FuenteN/A

Similar Npm por Puntuación de Confianza

@supabase/supabase-js (90)@supabase/storage-js (90)@testing-library/react (90)@supabase/realtime-js (90)@supabase/functions-js (90)
Ver los más seguros Npm →

Compare

Protocol Http vs @supabase/supabase-jsProtocol Http vs @supabase/storage-jsProtocol Http vs @testing-library/react

Safety Guide: Protocol Http

What is Protocol Http?

Protocol Http is a Node.js package — [![NPM version](https://img.shields.io/npm/v/@smithy/protocol-http/latest.svg)](https://www.npmjs.com/package/@smithy/protocol-http) [![NPM downloads](https://img.shields.io/npm/dm/@smithy/protocol-ht.

How to Verify Safety

Run npm audit to check for vulnerabilities. Review the package's GitHub repository for recent commits.

You can also check the trust score via API: GET /v1/preflight?target=@smithy/protocol-http

Key Safety Concerns for Node.js packages

When evaluating any Node.js package, watch for: dependency vulnerabilities, malicious packages, typosquatting.

Trust Assessment

Protocol Http has a Nerq Trust Score of 86/100 (A) and meets Nerq trust threshold. This score is based on automated analysis of security, maintenance, community, and quality signals.

Key Takeaways

Análisis Detallado de Puntuación

DimensionScore
Security90/100
Privacy80/100
Reliability90/100
Transparency85/100
Maintenance60/100

Based on 5 dimensions. Data from npm registry, GitHub repository, NVD, OSV.dev, and OpenSSF Scorecard.

¿Qué datos recopila Protocol Http?

Protocol Http is a Node.js package maintained by trivikr-aws. It receives approximately 50,977,750 weekly downloads. Licensed under Apache-2.0.

As a development package, Protocol Http does not directly collect end-user personal data. However, applications built with it may collect data depending on implementation. Privacy score: 80/100.

Review the package's dependencies for potential supply chain risks. Run your package manager's audit command regularly.

Análisis completo: Informe de Privacidad de Protocol Http · Privacy review

¿Es Protocol Http seguro?

Security score: 90/100. Protocol Http has 0 known vulnerabilities (CVEs) in the National Vulnerability Database. This is a clean record.

Licensed under Apache-2.0, allowing code inspection. Open-source packages allow independent security review of the source code.

Run your package manager's audit command (`npm audit`, `pip audit`, `cargo audit`) to check for known vulnerabilities in your dependency tree.

Análisis completo: Informe de Seguridad de Protocol Http

Cómo calculamos esta puntuación

Protocol Http's trust score of 86.0/100 (A) is computed from npm registry, GitHub repository, NVD, OSV.dev, and OpenSSF Scorecard. The score reflects 5 independent dimensions: security (90/100), privacy (80/100), reliability (90/100), transparency (85/100), maintenance (60/100). Each dimension is weighted equally to produce the composite trust score.

Nerq analyzes over 7.5 million entities across 26 registries using the same methodology, enabling direct cross-entity comparison. Scores are updated continuously as new data becomes available.

This page was last reviewed on April 05, 2026. Data version: 1.0.

Full methodology documentation · Machine-readable data (JSON API)

Preguntas Frecuentes

Is Protocol Http safe to use?
Yes, it is safe to use. @smithy/protocol-http has a Nerq Trust Score of 86.0/100 (A). Strongest signal: popularidad (100/100). Score based on security (90/100), popularity (100/100).
What is Protocol Http's trust score?
@smithy/protocol-http: 86.0/100 (A). Score based on: security (90/100), popularity (100/100). Scores update as new data becomes available. API: GET nerq.ai/v1/preflight?target=@smithy/protocol-http
What are safer alternatives to Protocol Http?
In the npm category, more Node.js packages are being analyzed — check back soon. @smithy/protocol-http scores 86.0/100.
Does Protocol Http have known vulnerabilities?
Nerq checks Protocol Http against NVD, OSV.dev, and registry-specific vulnerability databases. Current security score: 90/100. Run your package manager's audit command for the latest findings.
How actively maintained is Protocol Http?
Protocol Http has a trust score of 86.0/100 (A). Meets Nerq Verified threshold.
API: /v1/preflight Trust Badge API Docs

Disclaimer: Las puntuaciones de confianza de Nerq son evaluaciones automatizadas basadas en señales disponibles públicamente. No son respaldos ni garantías. Siempre realice su propia diligencia debida.

Usamos cookies para análisis y caché. Privacidad