@opennextjs/aws
Open source Next.js serverless adapter
88%
Total Score
healthy
Frequent stable releases, active project backing, and npm provenance outweigh workflow hygiene gaps.
Health Score Breakdown
The project uses build tooling, but no security scanning tools were detected; this is a modest transparency and maintenance gap rather than a severe risk.
No repository security policy was found, leaving vulnerability-reporting expectations unclear for a package used in deployment infrastructure.
All six workflows were analyzed, with no untrusted checkout or script-injection findings, but all 18 action references are unpinned and three workflows grant top-level write access. The audit also found a high-confidence archived action and ad hoc package installs; the trusted-publishing finding is informational here.
Vulnerabilities
| Title | Versions | Severity |
|---|---|---|
AIKIDO-2025-10204 @opennextjs/aws is vulnerable to Authorization Bypass in versions 2.3.0 - 3.5.3. | 2.3.0 - 3.5.3 | Critical |
Package versions
Maintainers
Direct Dependencies
| Dependency | Last Release | Score |
|---|---|---|
 yaml Version ^2.9.1 | — | — |
chalk Version ^5.6.2 | — | — |
cookie Version ^1.1.1 | — | — |
esbuild Version 0.28.2 | — | — |
express Version ^5.2.1 | — | — |
Weekly Downloads
Info
- Last Published
- 21 hours ago
- Created
- 2 years ago
- Unpacked Size
- 0.7 MB
Are You Affected?
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 27001CompliantISO 42001Compliant
FedRAMPImplementing© All Intel data is openly available and commercially licensed.