soajs.controller
soajs multi tenant API gateway
This report shows the evidence for soajs.controller@4.3.20. 2 of 9 known versions are blocked or flagged. The newest version, 4.3.21, is allowed. See all versions.
AI Security Review
scanned 3d ago · by lpm-firewall-aiThe source traces a configured Kubernetes token from registry configuration into an authenticated request whose CA branch uses a package-selected hardcoded host. This is a concrete credential disclosure path and warrants blocking.
Decision evidence
public snapshot- Registry loading passes a stored Kubernetes token, URL, and CA configuration into the node lookup path.
- When CA configuration is present, the Kubernetes driver uses a hardcoded server at http://server.com instead of the configured cluster URL.
- If the CA request options have no authentication, the driver sets the stored token as the bearer credential.
- The registry node lookup calls the Kubernetes node API, completing the path that sends requests using the configured authentication.
- The manifest lists a test script, with no install lifecycle hook; the identified exposure is in runtime behavior.
- The exposure requires runtime use of the Kubernetes registry path with CA configuration; the ordinary non-CA branch uses the configured URL.
- The package manifest has no install lifecycle hook.
Source & flagged code
7 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.20.
The versions list below shows the verdict for each recorded version.
- Avoid installing soajs.controller@4.3.20. Remove it from direct dependencies and check your lockfile for transitive copies.
- Choose an independently verified alternative or release. This report does not establish that other versions are safe.
- If this version ran, investigate the affected machine and build environment. Rotate credentials it could access and rebuild from a trusted environment.
Evidence last updated: .
Think this verdict is wrong? Dispute it on GitHub or read how reports are produced.