soajs.controller@4.3.19
soajs multi tenant API gateway
AI Security Review
scanned 3d ago · by lpm-firewall-aiThe no-CA Kubernetes connection path disables TLS verification while transmitting a bearer token, creating a concrete security risk. This supports a warning for a critical vulnerability, but the inspected source does not establish malicious behavior.
Decision evidence
public snapshot- The package manifest defines only a test script and declares the Kubernetes client dependency.
- Registry configuration supplies a Kubernetes URL and bearer token to the driver.
- When CA configuration is absent, the driver sends the bearer token with TLS verification disabled.
- The flagged registry code loads configured container deployment settings; the manifest shows no install lifecycle hook.
- The insecure transport branch is part of the package’s Kubernetes integration, not evidence of credential theft or unrelated code execution.
Source & flagged code
6 flagged · loading sourcePackage contains a possible secret pattern.
test/unit/mw/key/index.jsView on unpkg · L17Hardcoded password in test/unit/mw/key/index.js
test/unit/mw/key/index.jsView on unpkg · L178Package source references dynamic require/import behavior.
Gruntfile.jsView on unpkg · L10Findings
Affected versions and remediation
This report applies to soajs.controller@4.3.19.
See all versions of soajs.controller for other recorded verdicts.
- Review the evidence and your use of soajs.controller@4.3.19 before allowing it. Restrict the permissions described in this report.
- Choose an independently verified alternative or release. This report does not establish that other versions are safe.
Evidence last updated: .
Think this verdict is wrong? Dispute it on GitHub or read how reports are produced.