Is Middleware Location Constraint Safe?

Middleware Location Constraint — Nerq Trust Score 73.5/100 (B grade). Based on analysis of 2 trust dimensions, it is generally safe but has some concerns. Last updated: 2026-03-31.

Yes, Middleware Location Constraint is safe to use. Middleware Location Constraint is a Node.js package ([![NPM version](https://img) with a Nerq Trust Score of 73.5/100 (B), based on 3 independent data dimensions. It is recommended for production use. Security: 80/100. Popularity: 95/100. Data sourced from npm registry, GitHub repository, NVD, OSV.dev, and OpenSSF Scorecard. Last updated: 2026-03-31. Machine-readable data (JSON).

Is Middleware Location Constraint safe?

YES — Middleware Location Constraint has a Nerq Trust Score of 73.5/100 (B). It meets Nerq's trust threshold with strong signals across security, maintenance, and community adoption. Recommended for production use — review the full report below for specific considerations.

Security Analysis → {name} Privacy Report →

What is Middleware Location Constraint's trust score?

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

Security
80
Popularity
95

What are the key security findings for Middleware Location Constraint?

Middleware Location Constraint's strongest signal is popularity at 95/100. No known vulnerabilities have been detected. It meets the Nerq Verified threshold of 70+.

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

What is Middleware Location Constraint and who maintains it?

Authoramzn-oss
Categorynpm
SourceN/A

Similar Npm by Trust Score

babel-plugin-jest-hoist (74)@smithy/util-stream (74)@aws-sdk/middleware-bucket-endpoint (74)@aws-sdk/middleware-ssec (74)@smithy/middleware-retry (74)
See all safest Npm →

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 packages

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

Trust Assessment

Middleware Location Constraint has a Nerq Trust Score of 74/100 (B) and meets Nerq trust threshold. This score is based on automated analysis of security, maintenance, community, and quality signals.

Key Takeaways

Detailed Score Analysis

DimensionScore
Security80/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.

What data does Middleware Location Constraint collect?

Middleware Location Constraint is a Node.js package maintained by amzn-oss. It receives approximately 16,987,964 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: 80/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 73.5/100 (B) is computed from npm registry, GitHub repository, NVD, OSV.dev, and OpenSSF Scorecard. The score reflects 5 independent dimensions: security (80/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 March 31, 2026. Data version: 1.0.

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

Frequently Asked Questions

Is Middleware Location Constraint safe to use?
Yes, it is safe to use. @aws-sdk/middleware-location-constraint has a Nerq Trust Score of 73.5/100 (B). Strongest signal: popularity (95/100). Score based on security (80/100), popularity (95/100).
What is Middleware Location Constraint's trust score?
@aws-sdk/middleware-location-constraint: 73.5/100 (B). Score based on: security (80/100), popularity (95/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 category, more Node.js packages are being analyzed — check back soon. @aws-sdk/middleware-location-constraint scores 73.5/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: 80/100. Run your package manager's audit command for the latest findings.
How actively maintained is Middleware Location Constraint?
Middleware Location Constraint has a trust score of 73.5/100 (B). Meets Nerq Verified threshold.
API: /v1/preflight Trust Badge API Docs

Disclaimer: Nerq trust scores are automated assessments based on publicly available signals. They are not endorsements or guarantees. Always conduct your own due diligence.

We use cookies for analytics and caching. Privacy Policy