@aws-sdk/middleware-endpoint

Registry deprecationdanger

The entire package is deprecated, with npm stating that it has moved to @smithy/middleware-endpoint. This directly makes the assessed release unsuitable for a new dependency despite the active source repository.

Release historycaution

The package has had no registry release in more than three years, after 50 releases and a previously rapid median interval of about 5 days. Active repository work partly explains the gap, but it does not restore this package's release path.

Repo package mentioncaution

The repository name does not match the package and its README does not mention the package, which weakens package-to-source traceability. The AWS monorepo context partly explains the name mismatch but does not fully remove the gap.

Repo toolingcaution

The repository uses established build and test tooling, but no security scanning tools were detected. The missing scanning is a minor hygiene gap, not enough to offset the deprecation.

Workflow auditcaution

All 11 workflows were analyzed with no reported audit findings or untrusted checkout/script-injection paths. Seven of 22 action references are unpinned and one workflow grants top-level write access, creating only a modest hygiene concern.