Is IlhamKassim/resume-builder safe?
https://github.com/IlhamKassim/resume-builder
IlhamKassim/resume-builder is a legitimate single-user Next.js resume-tailoring tool with well-structured, security-conscious code. The primary concerns are PII exposure (the owner's real contact info and work history are committed to a public test fixture and remain in git history by explicit choice), and agent-configuration files that could direct an AI agent to take real GitHub actions (creating/closing issues) on the owner's repository. No malicious code, data exfiltration, install hooks, or prompt injection payloads were found; the SKILL.md is empty and installation was clean.
Category Scores
Findings (7)
MEDIUM Real PII committed to public repository in test fixture -12 ▶
lib/tests/fixtures/profile-fixture.ts contains the real name, email address, phone number, LinkedIn URL, and detailed work/education history of Mohammad Ilham bin Kassim. This file is committed to a public GitHub repository and is trivially readable by anyone. ADR-0003 additionally acknowledges that git history contains this data going back to commit ad223f4 and that rewriting history was explicitly declined.
MEDIUM AGENTS.md directs agents to take real GitHub actions on owner's repo -8 ▶
docs/agents/issue-tracker.md provides explicit, detailed gh CLI command templates for creating issues, adding labels, commenting, and closing issues against IlhamKassim/resume-builder. An AI agent working in this directory following these instructions could inadvertently create or modify real GitHub issues, label them, or close them based on conversational context.
LOW AGENTS.md misleads agents about Next.js version to redirect to node_modules docs -7 ▶
The nextjs-agent-rules block in AGENTS.md asserts 'This is NOT the Next.js you know — This version has breaking changes' and instructs agents to 'Read the relevant guide in node_modules/next/dist/docs/ before writing any code.' This is sourced from the mattpocock/skills framework but could cause agents to distrust their training knowledge about Next.js and seek additional direction from the node_modules documentation path.
LOW Profile data bundled client-side if deployed -6 ▶
SPEC.md and ADR-0003 both document that app/page.tsx and app/preview/page.tsx import myProfile as a Client Component, meaning the profile data is bundled into client-side JavaScript. For local-only use this is intentional, but represents a latent data exposure risk if the app is ever deployed publicly.
INFO Clean installation — only GitHub contacted 0 ▶
Network monitoring confirms the git clone connected exclusively to GitHub (140.82.121.3:443). No DNS queries to attacker-controlled domains, no unexpected process spawning, no new listening ports established. The connection state diff is clean.
INFO All honeypot canary files intact 0 ▶
Monitoring confirms no canary file (.env, SSH keys, AWS credentials, npmrc, docker config, GCP credentials) was read or modified by anything attributable to the cloned repository. Early syscall accesses to these files predate the clone and belong to the audit framework's baseline phase.
INFO No malicious install hooks or executable payloads 0 ▶
package.json contains no preinstall, postinstall, or prepare lifecycle scripts. No .gitattributes filter drivers, no git hooks, no submodules, no symlinks outside the repo. All TypeScript source code is standard Next.js application logic with no eval(), no dynamic requires, and no obfuscation.