registry / trackly-cli / 0.24.0
trackly-cli@0.24.0
Search Thousands of jobs across Thousands of companies with the Trackly CLI and MCP server for Claude, ChatGPT, Codex and Cursor. Filter by role, location, salary and sponsorship; track jobs and prepare applications.
AI Security Review
scanned 2d ago · by lpm-firewall-aiThe flagged command execution is used for explicit agent setup, and the package has no install lifecycle hook. Runtime MCP analytics are disclosed, sent through Trackly, filtered before transmission, and can be disabled with environment settings.
Static reason
One or more suspicious static signals were detected.; previous stored version diff introduced dangerous source
Trigger
The user runs a CLI command or starts the MCP server; agent setup requires an explicit setup command.
Impact
No malicious behavior identified. Analytics are disclosed and can be disabled through environment settings.
Mechanism
The CLI sends feature requests to Trackly. MCP analytics relay events to the Trackly service and filter captured parameters through an allowlist.
AI rationale
The flagged command execution is used for explicit agent setup, and the package has no install lifecycle hook. Runtime MCP analytics are disclosed, sent through Trackly, filtered before transmission, and can be disabled with environment settings.
Network endpoints3
closeai.mba/api/jobscout/mcp-analyticscloseai.mba/api/jobscout/mcp-analytics/anonymouscloseai.mba/api/jobscout/analytics-preference
Decision evidence
public snapshotAI called this Clean at 94.0% confidence as Benign with low false-positive risk.
Evidence for AI clean decision
- The manifest exposes a `trackly` CLI and lists no install lifecycle hooks.
- MCP usage analytics are disclosed in the README, which describes the collected data and exclusions.
- Analytics can be disabled with `TRACKLY_MCP_ANALYTICS_DISABLED` or by setting `TRACKLY_MCP_ANALYTICS_ENABLED` false.
- Analytics use the Trackly service; captured MCP parameters are projected through an allowlist before sending.
- Agent skill setup runs through the explicit `trackly agent setup` command.
Evidence against
- MCP analytics run by default and the README says there is no account-level opt-out.
- The CLI and MCP server make network requests to the Trackly service as part of their features.
Behavioral surface
ChildProcessCryptoEnvironmentVarsFilesystemNetwork
HighEntropyStringsUrlStrings
Source & flagged code
6 flaggedscripts/verify-audit-exceptions.jsView file
6const path = require('node:path');
L7: const { spawnSync } = require('node:child_process');
L8:
High
Child Process
Package source references child process execution.
scripts/verify-audit-exceptions.jsView on unpkg · L6bin/trackly#virtual:normalized:round1View file
18const { color, isJSON, jobDateDetailLines, outputJobs, outputCompanies, outputStats, outputContacts, outputReferralCampaign, outputNetworkBrief, outputCompanyBrief, outputCompanyWo...
L19: const http = require("http");
L20: const crypto = require("crypto");
L21: const { spawnSync } = require("child_process");
L22: const { version: VERSION } = require("../package.json");
L23: const { doctorAgent, resumeValidationStatus, setupAgent } = require("../lib/agent");
...
L223:
L224: function failNow(message, exitCode = 1) {
L225: outputError(message);
...
L311: // Flags deprecated in the API-docs-plan fixup. Still accepted by parseArgs so old
L312: // scripts don"t ERR_NOT_FOUND, but cmdJobs hard-rejects them with a migration hint\n// — silent no-op would be worse than noise (per PR #13 Codex
High
Command Output Exfiltration
Source combines command execution, command-output handling, and outbound requests; review data flow before blocking.
Findings
1 Critical3 High2 Medium6 Low
CriticalPrevious Version Dangerous Deltalib/agent.js
HighChild Processscripts/verify-audit-exceptions.js
HighCommand Output Exfiltrationbin/trackly#virtual:normalized:round1
HighSemantic Analysis Limitedbin/trackly#virtual:normalized:round1
MediumNetwork
MediumEnvironment Vars
LowScripts Present
LowFilesystem
LowHigh Entropy Strings
LowUrl Strings
LowSuspicious Lifecycle Evidencepackage.json
LowAi Review EvidenceREADME.md
Affected versions and remediation
This report applies to trackly-cli@0.24.0.
See all versions of trackly-cli for other recorded verdicts.
- Review the evidence and your use of trackly-cli@0.24.0 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.