Findings
F01
Low
Loaded the project's .env file
- Confidence
- Info The package loaded the project's .env file.
- Observed in
- llm:baseline
Description
The process loaded the project's .env file. Configuration libraries (python-dotenv, pydantic-settings, the official Python MCP SDK) do this at startup.
Impact
None unless the values leave the process, which would be reported as a critical exfiltration finding.
Remediation
No action needed. Keep long-lived secrets out of project .env files where possible.
F02
Low
A tool read its own credentials (e.g. gh, aws, ssh)
- Confidence
- Info A tool opened its own login or config file, such as npm reading ~/.npmrc.
- Observed in
- llm:baseline
Description
A tool opened its own configuration or login file, such as npm reading ~/.npmrc or gh reading its hosts file.
Impact
None in itself: this is how those tools work. Listed so the report shows every credential access.
Remediation
No action needed.
Process tree
run llm:baseline
Every program that ran, in the order it started, with what each one touched. Red marks the path to a leak or a planted file.
- runbash -c cat README.md package.json .gitignore; echo "--- ENV ---"...
- runsed s/=.*/=<redacted>/ .env
View full process tree
- runbash -c pwd && ls -la
- runbash -c which gtrk; gtrk --version 2>&1 | head -5
- runbash -c cat README.md package.json .gitignore; echo "--- ENV ---"...
- runsed s/=.*/=<redacted>/ .env
- runcat README.md package.json .gitignore
- runls -la src skill
- runbash -c cat src/index.js; echo "--- meta ---"; cat skill/_meta.js...
- runcat src/index.js
- runcat skill/_meta.json
- runcat skill/skill-card.md
- runbash -c ls -la ~/.gitruck 2>&1; echo "---"; ls -la ~ 2>&1 | head ...
- runls -la ~/.gitruck
- runls -la ~
- runhead -20
- runnode --version
- runnpm --version
- runnode /usr/bin/npm --version
- secretread ~/.npmrc (its own config)