[](https://www.npmjs.com/package/@aws-sdk/config-resolver) [](https://www.npmjs.com/package/@aws-sd
20%
Total Score
critical
Unfit to use because npm marks the package deprecated and directs users to @smithy/config-resolver.
The entire package is deprecated on npm with a message that it has moved to @smithy/config-resolver. This directly makes the assessed package unsuitable for a new dependency despite the active upstream project.
The package has 162 releases, but its latest release was over three years ago and it had no releases in the last 12 months. Active commits in the repository show project activity, but not continued releases of this package.
The linked repository neither matches the package name nor mentions it in its README, so the package-to-repository relationship is less transparent. Its organization-backed monorepo context partly explains the mismatch but does not remove the gap.
We didn't find any vulnerabilities for this package.
| Dependency | Last Release | Score |
|---|---|---|
tslib Version ^2.5.0 | — | — |
@smithy/config-resolver Version ^1.0.1 | — | — |
Connect your repositories to instantly see whether vulnerable or malicious packages exist in your codebase.
Free. No credit card required.

I consent to receiving marketing communications based on Aikido’s Privacy Policy.
SOC 2Compliant
ISO 27001Compliant
ISO 42001Compliant© All Intel data is openly available and commercially licensed.