T08 · Insecure Dependencies
- Location
reference/TOOL.MD:6- Finding
Unpinned Third-Party Python Dependencies
- Content
View full analysis
- Remediation
View remediation
Security audit
Security checks for vulnerabilities and agentic risk
The skill is mostly aligned with adding paper citations, but it can automatically change project bibliography files using unvalidated remote metadata and its documentation overstates what the code safely does.
Review this skill carefully before installing. Use it only in a disposable branch or backup copy of a paper project, inspect proposed references before compiling, pin dependencies in a virtual environment, and do not rely on the documented backup or citation-insertion behavior unless the implementation is fixed.
reference/TOOL.MD:6Unpinned Third-Party Python Dependencies
reference/TOOL.MD:52Untrusted Scholar Metadata Written to BibTeX Without Validation or Escaping
The top-level description says the tool 'inserts citation markers in key sections,' implying modification of TeX source files. However, the code shown only reads TeX files, searches Google Scholar, appends entries to custom.bib, and writes ADD.MD; there is no logic that edits .tex files to insert citations.
The tool automatically appends entries to a project's BibTeX file and creates/overwrites a report file, but the description does not clearly warn users that project files will be modified. In a research or Overleaf context, silent modification of source files can lead to accidental repository changes, data integrity issues, or unintended commits, especially when run on trusted project directories.
This note describes behavior centered on section-aware citation insertion. The implementation never parses section boundaries such as Introduction, Related Work, or Method, and never writes back to any .tex file, so the documented intent contradicts the actual code.
The documentation promises a detailed report, which suggests listing added references or other substantive details. In reality, the report generation code writes only 'Total {new_count} citations' to ADD.MD, so the stated output materially overstates what the tool produces.