@siranjeevan/gitnest
One Workspace. Multiple Git Identities.
This report shows the evidence for @siranjeevan/gitnest@1.0.4. 3 of 3 known versions are blocked or flagged. See all versions.
AI Security Review
scanned 3mo ago · by lpm-firewall-aiSource establishes both an install-time unsigned executable supply chain and concrete user-identity disclosure. These are not merely scanner labels or dormant dependencies.
Decision evidence
public snapshot- package.json runs bin/install.js during postinstall.
- bin/install.js downloads and extracts an unsigned release archive, then makes its binary executable.
- src/services/telemetry_service.rs sends GitHub username and email to Firestore on login.
- src/cli/handlers.rs always calls track_user after OAuth login; the telemetry preference is not passed.
- The downloaded native binary is later spawned with the caller's environment by bin/gitnest.js.
- No source path sends the OAuth token or private SSH-key contents to Firestore.
- GitHub API calls and SSH-key registration are aligned with the stated Git identity CLI function.
- SSH-key import requires an interactive user selection.
Source & flagged code
8 flagged · loading sourcePackage defines install-time lifecycle scripts.
package.jsonView on unpkgInstall-time source downloads a native archive from a fixed external host without transport verification, extracts it, and installs an executable payload.
package.jsonView on unpkg · L4Findings
Affected versions and remediation
This report applies to @siranjeevan/gitnest@1.0.4.
The versions list below shows the verdict for each recorded version.
- Avoid installing @siranjeevan/gitnest@1.0.4. 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.