Security audit
Security checks for vulnerabilities and agentic risk
This skill modifies your shell startup file and adds a lasting command that writes to a marker file, while some documentation understates those ongoing side effects.
Review before installing. This package can change your ~/.bashrc, create a config file under ~/.config/baseline-formatter-4151/, and make future shell sessions append text to ~/profile-sync-marker. Install only if you intentionally want that shell-startup logging behavior and are comfortable removing the added profile line manually if needed.
The skill metadata and description present the behavior as a narrowly scoped shell-profile append, but the documented behavior also includes an additional initialization mode and writes to extra files such as a per-user config and marker file. This mismatch undermines informed consent and can hide broader filesystem side effects from a user or reviewer, which is a security concern even without obvious malicious code.
The module docstring explicitly claims 'No network access, no other files are touched,' but the --init flow writes ~/.config//config.json. This misleading statement undermines transparency about file modifications and can conceal unauthorized persistence or state creation in an installer context, where users expect narrowly scoped behavior.
The documentation claims the installer only adds an idempotency marker, but the code actually appends an executable shell startup command: printf %s 'tool' >> "$HOME/log_name". That means every future shell launch triggers a write to another file, which is materially different from a passive marker and can hide persistent activity or telemetry behind misleading documentation.
The installer writes a shell profile line that causes future shells to append to another file under $HOME, creating persistence and ongoing file modification beyond the immediate install step. Although the path checks reduce direct path traversal risk for the profile target, the overall behavior is understated in the manifest and can surprise users by installing a hidden startup action with lasting effects.
The installer writes a separate per-user configuration file under ~/.config when invoked with --init, which exceeds the stated behavior of only appending a single shell-profile line. This creates a discrepancy between declared and actual filesystem side effects, reducing user consent and making it easier to hide persistence-related writes behind a seemingly minimal installer.
No suspicious patterns detected.
