Is glin-profanity safe?
- Node.js dynamic code execution
- Node.js filesystem read
- Node.js filesystem write/delete
glin-profanity is an AI npm_package analyzed by SkillTotal's deterministic static scanner. The scan found no malicious indicators, though 4 risky constructs are reported for review. It can: dynamic code execution, filesystem read, filesystem write and network egress — capabilities are what the code can do, not a verdict on intent. Risk score 0/100 (low).
glin-profanity 3.3.0
Automated static-analysis result. It can contain false positives and false negatives, and is not a claim about the intent of glin-profanity's authors. Report a false positive.
Behavioral traits
How this component maps to the CSA agentic threat model. Descriptive — it never affects the risk score.
Findings (4)
The code turns strings into live code at runtime (eval / new Function / exec).
return new Function("m", "return import(m)")(moduleName);return new Function("m", "return import(m)")(moduleName);Why it matters: If those strings aren't fixed and trusted, they become a way to run arbitrary code.
Fix: Avoid evaluating dynamically constructed code; if unavoidable, ensure the input is a trusted constant and never derived from external data.
The component reads files from disk.
* // const saved = JSON.parse(fs.readFileSync('filter.config.json'));* // const saved = JSON.parse(fs.readFileSync('filter.config.json'));* // const saved = JSON.parse(fs.readFileSync('filter.config.json'));* // const saved = JSON.parse(fs.readFileSync('filter.config.json'));* // const saved = JSON.parse(fs.readFileSync('filter.config.json'));* // const saved = JSON.parse(fs.readFileSync('filter.config.json'));* // const saved = JSON.parse(fs.readFileSync('filter.config.json'));* // const saved = JSON.parse(fs.readFileSync('filter.config.json'));* // const saved = JSON.parse(fs.readFileSync('filter.config.json'));* // const saved = JSON.parse(fs.readFileSync('filter.config.json'));* // const saved = JSON.parse(fs.readFileSync('filter.config.json'));* // const saved = JSON.parse(fs.readFileSync('filter.config.json'));* // const saved = JSON.parse(fs.readFileSync('filter.config.json'));* // const saved = JSON.parse(fs.readFileSync('filter.config.json'));* // const saved = JSON.parse(fs.readFileSync('filter.config.json'));* // const saved = JSON.parse(fs.readFileSync('filter.config.json'));* // const saved = JSON.parse(fs.readFileSync('filter.config.json'));* // const saved = JSON.parse(fs.readFileSync('filter.config.json'));* // const saved = JSON.parse(fs.readFileSync('filter.config.json'));* // const saved = JSON.parse(fs.readFileSync('filter.config.json'));* // const saved = JSON.parse(fs.readFileSync('filter.config.json'));* // const saved = JSON.parse(fs.readFileSync('filter.config.json'));* // const saved = JSON.parse(fs.readFileSync('filter.config.json'));* // const saved = JSON.parse(fs.readFileSync('filter.config.json'));* // const saved = JSON.parse(fs.readFileSync('filter.config.json'));Why it matters: Usually legitimate, but worth confirming it can't be steered into reading sensitive files.
Fix: Confirm which files are read and that paths cannot be influenced by untrusted input to reach sensitive locations.
The component writes or deletes files on disk.
* // Save to file: fs.writeFileSync('filter.config.json', JSON.stringify(config));* // Save to file: fs.writeFileSync('filter.config.json', JSON.stringify(config));* // Save to file: fs.writeFileSync('filter.config.json', JSON.stringify(config));* // Save to file: fs.writeFileSync('filter.config.json', JSON.stringify(config));* // Save to file: fs.writeFileSync('filter.config.json', JSON.stringify(config));* // Save to file: fs.writeFileSync('filter.config.json', JSON.stringify(config));* // Save to file: fs.writeFileSync('filter.config.json', JSON.stringify(config));* // Save to file: fs.writeFileSync('filter.config.json', JSON.stringify(config));* // Save to file: fs.writeFileSync('filter.config.json', JSON.stringify(config));* // Save to file: fs.writeFileSync('filter.config.json', JSON.stringify(config));* // Save to file: fs.writeFileSync('filter.config.json', JSON.stringify(config));* // Save to file: fs.writeFileSync('filter.config.json', JSON.stringify(config));* // Save to file: fs.writeFileSync('filter.config.json', JSON.stringify(config));* // Save to file: fs.writeFileSync('filter.config.json', JSON.stringify(config));* // Save to file: fs.writeFileSync('filter.config.json', JSON.stringify(config));* // Save to file: fs.writeFileSync('filter.config.json', JSON.stringify(config));* // Save to file: fs.writeFileSync('filter.config.json', JSON.stringify(config));* // Save to file: fs.writeFileSync('filter.config.json', JSON.stringify(config));* // Save to file: fs.writeFileSync('filter.config.json', JSON.stringify(config));* // Save to file: fs.writeFileSync('filter.config.json', JSON.stringify(config));* // Save to file: fs.writeFileSync('filter.config.json', JSON.stringify(config));* // Save to file: fs.writeFileSync('filter.config.json', JSON.stringify(config));* // Save to file: fs.writeFileSync('filter.config.json', JSON.stringify(config));* // Save to file: fs.writeFileSync('filter.config.json', JSON.stringify(config));* // Save to file: fs.writeFileSync('filter.config.json', JSON.stringify(config));Why it matters: Usually legitimate, but worth confirming the paths can't be controlled by untrusted input.
Fix: Confirm which files are written/deleted and that paths cannot be influenced by untrusted input.
The component makes outbound network requests.
const response = await fetch(`${baseUrl}${endpoint}`, {const response = await fetch(`${baseUrl}${endpoint}`, {const response = await fetch(`${baseUrl}${endpoint}`, {const response = await fetch(`${baseUrl}${endpoint}`, {const response = await fetch(`${baseUrl}/audio/transcriptions`, {const response = await fetch(
* const response = await fetch('https://api.openai.com/v1/audio/transcriptions', {const response = await fetch(`${baseUrl}/audio/transcriptions`, {const response = await fetch(
const response = await fetch(`${baseUrl}/audio/transcriptions`, {const response = await fetch(
const response = await fetch(`${baseUrl}/audio/transcriptions`, {const response = await fetch(
Why it matters: Usually legitimate, but confirm the destinations are expected and no sensitive data leaves.
Fix: Confirm the destination hosts are expected and that no sensitive data is sent off-host.
Check your own component
Run the same evidence-backed scan on any MCP server, agent skill, or package.
Scan your own componentHow we determine this: deterministic static analysis (regex + AST), evidence-anchored, no code execution. Methodology →