Protocol Http est-il sûr ?

Protocol Http — Nerq Trust Score 86.0/100 (Note A). Sur la base de l'analyse de 2 dimensions de confiance, il est considéré comme sûr. Dernière mise à jour : 2026-04-05.

Oui, Protocol Http est sûr à utiliser. Protocol Http est un package npm ([![NPM version](https://img) avec un Nerq Trust Score de 86.0/100 (A), basé sur 3 dimensions de données indépendantes. It is recommandé pour une utilisation en production. Security: 90/100. Popularity: 100/100. Données de npm registry, GitHub repository, NVD, OSV.dev, and OpenSSF Scorecard. Dernière mise à jour: 2026-04-05. Données lisibles par machine (JSON).

Protocol Http est-il sûr ?

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. Recommandé pour une utilisation en production — review the full report below for specific considerations.

Analyse de Sécurité → Rapport de confidentialité de {name} →

Quel est le score de confiance de Protocol Http ?

Protocol Http a un Score de Confiance Nerq de 86.0/100, obtenant la note A. Ce score est basé sur 2 dimensions mesurées indépendamment.

Sécurité
90
Popularité
100

Quels sont les résultats de sécurité clés pour Protocol Http ?

Le signal le plus fort de Protocol Http est popularité à 100/100. Aucune vulnérabilité connue n'a été détectée. Atteint le seuil vérifié Nerq de 70+.

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

Qu'est-ce que Protocol Http et qui le maintient ?

Auteurtrivikr-aws
Catégorienpm
SourceN/A

Npm similaires par Score de Confiance

@supabase/supabase-js (90)@supabase/storage-js (90)@testing-library/react (90)@supabase/realtime-js (90)@supabase/functions-js (90)
Voir tous les Npm les plus sûrs →

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

Analyse détaillée du score

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.

Quelles données Protocol Http collecte-t-il ?

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.

Analyse complète : Rapport de confidentialité de Protocol Http · Privacy review

Protocol Http est-il sécurisé ?

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.

Analyse complète : Rapport de sécurité de Protocol Http

Comment nous avons calculé ce score

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)

Questions fréquentes

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: popularité (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: Les scores de confiance Nerq sont des évaluations automatisées basées sur des signaux publiquement disponibles. Ce ne sont pas des recommandations ou des garanties. Effectuez toujours votre propre vérification.

Nous utilisons des cookies pour l'analyse et le cache. Confidentialité