@smithy/middleware-endpointv3.2.1

latest

License: Permissive (Apache-2.0)

Published:

[![NPM version](https://img.shields.io/npm/v/@smithy/middleware-endpoint/latest.svg)](https://www.npmjs.com/package/@smithy/middleware-endpoint) [![NPM downloads](https://img.shields.io/npm/dm/@smithy/middleware-endpoint.svg)](https://www.npmjs.com/packag

Pending

Info: Analyzing

Processing in progress, check later.

SAFE Assessment| Preliminary analysis results

Compliance

Licenses

No license compliance issues

Secrets

No sensitive information found

Security

Vulnerabilities

No known vulnerabilities detected

Hardening

No application hardening issues

Threats

Tampering

No evidence of software tampering

Malware

No evidence of malware inclusion

Issues

No issues found

Behaviors

See all behaviors

Contains references to environment variables related to Amazon Web Services (AWS).

settings

Serializes data into the JSON format.

file

Vulnerabilities

Downloads

608.27M

Recorded Downloads Since 2021

Maintenance

Maintainers

Dependencies

Declared Dependencies

Dependents

432

Dependents

Issues per Version Graph

Scanned

FAQ for @smithy/middleware-endpoint

What is @smithy/middleware-endpoint?

Is @smithy/middleware-endpoint malicious or is it safe to use?

The npm package @smithy/middleware-endpoint was scanned for malware, software tampering, risky behaviors, exposed secrets and known vulnerabilities. Caution is advised as this package is still in review by ReversingLabs threat researchers for inclusion of novel supply chain threats.

Is @smithy/middleware-endpoint popular?

The npm package @smithy/middleware-endpoint is not widely used. It has 608M recorded downloads. A package's popularity is not a good indicator of its safety, visit the SAFE Assessment section to see the full analysis of package deployment risk categories.

How do I secure @smithy/middleware-endpoint once it is in my app?

Since we can't know when or where malicious attacks will happen, we recommend tracking how @smithy/middleware-endpoint behaviors change over multiple software releases. By adopting differential analysis in your release process, you can detect unexpected changes to a @smithy/middleware-endpoint version, which can prevent advanced software supply chain attacks. Read how our technology can help prevent future attacks similar to SolarWinds and 3CX.