@atlassecurity/auth@1.1.1
Atlas SDK - Node.js binding for Atlas.dll (Windows x64).
AI Security Review
scanned 14d ago · by lpm-firewall-aiThe visible install hook performs a limited marker write, and the JavaScript wrapper fits an authentication SDK. The central native library is loaded but its behavior cannot be assessed from the inspected source, leaving a concrete unresolved risk that warrants a warning.
Decision evidence
public snapshot- The manifest runs a postinstall script and declares the native binding dependency.
- The postinstall script writes a version and timestamp marker under the user’s local application-data directory.
- The runtime loads Atlas.dll through koffi, but the native library’s behavior is not visible in the inspected JavaScript source.
- The JavaScript wrapper exposes authentication and webhook functions through Atlas.dll.
- The inspected install hook contains no evident network or package-file rewrite behavior; its visible write is the AtlasAuth marker.
- The visible wrapper maps SDK calls to named Atlas.dll functions and contains no child-process or eval use.
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 unpkgThe manifest runs a postinstall script and declares the native binding dependency.
package.jsonView on unpkg · L16Findings
Affected versions and remediation
This report applies to @atlassecurity/auth@1.1.1.
See all versions of @atlassecurity/auth for other recorded verdicts.
- Review the evidence and your use of @atlassecurity/auth@1.1.1 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.