@atlassecurity/auth@1.1.3
Atlas SDK - Node.js binding for Atlas.dll (Windows x64).
AI Security Review
scanned 8d ago · by lpm-firewall-aiThe inspected JavaScript exposes an authentication SDK and its install hook writes a local marker. The shipped DLL has unresolved runtime behavior, so a warning is warranted without a confirmed attack or basis for blocking publication.
Decision evidence
public snapshot- Importing src/index.js loads the shipped Atlas.dll through the native binding.
- Startup invokes the native library when the caller calls the exported method.
- The DLL analysis lists network and process creation imports and strings referring to startup updates; these findings do not establish that those behaviors execute.
- The DLL analysis says some native call targets were not inspected, leaving runtime behavior unresolved.
- The postinstall hook writes a local developer marker; the unresolved concern is the native runtime.
- The exposed authentication and account methods take credentials and are called through explicit API methods.
- The inspected install hook writes a local marker and shows no network call.
Source & flagged code
6 flagged · loading sourcePackage defines install-time lifecycle scripts.
package.jsonView on unpkgInstall-time lifecycle script is not statically allowlisted and needs review.
package.jsonView on unpkgFindings
Affected versions and remediation
This report applies to @atlassecurity/auth@1.1.3.
See all versions of @atlassecurity/auth for other recorded verdicts.
- Review the evidence and your use of @atlassecurity/auth@1.1.3 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.