Is Middleware Location Constraint Safe?

Middleware Location Constraint — Nerq Trust Score 82.8/100 (A- grade). Score based on 2 independent trust signals. Last analyzed: 2026-08-24

Middleware Location Constraint is a npm package ([![NPM version](https://img) with a Nerq Trust Score of 82.8/100 (A-), based on 3 independent data dimensions. Last analyzed: 2026-08-24 Security: 90/100. Popularity: 100/100. Data sourced from npm registry, GitHub repository, NVD, OSV.dev, and OpenSSF Scorecard. Last updated: 2026-08-24. Machine-readable data (JSON).

Is Middleware Location Constraint safe?

Trust Score Breakdown — Middleware Location Constraint has a Nerq Trust Score of 82.8/100 (A-). Measured across 2 independent trust signals (as of 2026-08-24).

Security Analysis → Middleware Location Constraint Privacy Report →

What is Middleware Location Constraint's trust score?

Middleware Location Constraint has a Nerq Trust Score of 82.8/100, earning a A- grade. This score is based on 2 independently measured dimensions including security, maintenance, and community adoption.

Security
90
Popularity
100

What are the key security findings for Middleware Location Constraint?

Middleware Location Constraint's strongest signal is popularity at 100/100. No known vulnerabilities have been detected.

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

What is Middleware Location Constraint and who maintains it?

Authoramzn-oss
Categorynpm Packages
SourceN/A

Similar Npm by Trust Score

@supabase/functions-js (90)workbox-webpack-plugin (89)expo-router (89)@auth0/auth0-spa-js (89)@react-native-community/datetimepicker (89)
See all safest Npm →

Compare

Middleware Location Constraint vs @supabase/functions-jsMiddleware Location Constraint vs workbox-webpack-pluginMiddleware Location Constraint vs expo-router

Safety Guide: Middleware Location Constraint

What is Middleware Location Constraint?

Middleware Location Constraint is a Node.js package — [![NPM version](https://img.shields.io/npm/v/@aws-sdk/middleware-location-constraint/latest.svg)](https://www.npmjs.com/package/@aws-sdk/middleware-location-constraint) [![NPM downloads](https://img.s.

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=@aws-sdk/middleware-location-constraint

Key Safety Concerns for Node.js package

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

Measured Signals

Middleware Location Constraint has a Nerq Trust Score of 83/100 (A-). This score is a composite of automated measurements of security, maintenance, community, and quality signals.

Key Takeaways

Detailed Score Analysis

DimensionScore
Security90/100
Maintenance90/100
Popularity100/100
Quality80/100
Community45/100

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

What data does Middleware Location Constraint collect?

Middleware Location Constraint is a Node.js package maintained by amzn-oss. It receives approximately 24,993,892 weekly downloads. Licensed under Apache-2.0.

As a development package, Middleware Location Constraint 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.

Full analysis: Middleware Location Constraint Privacy Report · Privacy review

Is Middleware Location Constraint secure?

Security score: 90/100. Middleware Location Constraint 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.

Full analysis: Middleware Location Constraint Security Report

How we calculated this score

Middleware Location Constraint's trust score of 82.8/100 (A-) is computed from npm registry, GitHub repository, NVD, OSV.dev, and OpenSSF Scorecard. The score reflects 5 independent dimensions: security (90/100), maintenance (90/100), popularity (100/100), quality (80/100), community (45/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.

Signals last measured on August 24, 2026. Data version: 1.0.

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

Frequently Asked Questions

Is Middleware Location Constraint Safe?
@aws-sdk/middleware-location-constraint with a Nerq Trust Score of 82.8/100 (A-). Strongest signal: popularity (100/100). Score based on Security (90/100), Popularity (100/100).
What is Middleware Location Constraint's trust score?
@aws-sdk/middleware-location-constraint: 82.8/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=@aws-sdk/middleware-location-constraint
What are safer alternatives to Middleware Location Constraint?
In the npm Packages category, more Node.js packages are being analyzed — check back soon. @aws-sdk/middleware-location-constraint scores 82.8/100.
Does Middleware Location Constraint have known vulnerabilities?
Nerq checks Middleware Location Constraint 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.
Is Middleware Location Constraint actively maintained?
Middleware Location Constraint maintenance score: N/A. Check the repository for recent commit activity and issue responsiveness.
API: /v1/preflight Trust Badge API Docs

See Also

Disclaimer: Nerq trust scores are automated measurements based on publicly available signals. They are not endorsements, verdicts, or guarantees of suitability. Always evaluate the signals against your own requirements.

We use cookies for analytics and caching. Privacy