soajs.controller@4.3.17
soajs multi tenant API gateway
AI Security Review
scanned 9d ago · by lpm-firewall-aiThe inspected source does not support a malicious verdict, but the Kubernetes client can send a configured bearer token with TLS verification disabled when CA configuration is absent. This warrants a warning for the conditional transport risk.
Decision evidence
public snapshot- The manifest contains only a test script and no install lifecycle hook; the entry point starts the controller service.
- In high availability mode, awareness uses the Kubernetes driver for service discovery.
- The driver takes the API URL, bearer token, and optional CA from deployment configuration.
- Without CA configuration, the client sends the bearer token with TLS verification disabled.
- The Kubernetes URL and token come from deployment registry configuration, and the client is used for Kubernetes service discovery.
- The source shows no unrelated credential recipient or malicious install behavior.
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.17.
See all versions of soajs.controller for other recorded verdicts.
- Review the evidence and your use of soajs.controller@4.3.17 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.