n8n-nodes-techmap
Based on the RiskyPlugins AI security review of the observed evidence. The review covers version 0.1.1, not the analysed version 0.2.1.
No individual score drivers were recorded for this analysis.
Analysis record
- Analysed
- Today 22 November 2026
- Version
- v0.2.1
- Artifact
- SHA256 37c7794f…7b099a
- Detail
- Full list
Is n8n-nodes-techmap safe?
This package is an n8n community node built by joerg.rech that connects your workflows to the Techmap job postings API. It lets you search international job listings and generate RSS feeds. The code reaches out to api.techmap.io and job-postings-rss-feed.p.rapidapi.com to pull data. That is exactly what you would expect from a node designed to fetch job feeds. It declares no special host permissions.
The scanner flagged a dozen URLs and domains, including techmap.io and rapidapi.com. These are just the legitimate endpoints the node needs to do its job. It also triggered twelve low-severity code-smell rules. Those typically fire on standard Node.js patterns like reading environment variables or making HTTP requests. None of these findings point to hidden instructions, credential theft, or unexpected network traffic.
The package only talks to the APIs it advertises. It contains no tool-poisoning or suspicious data collection. The scanner alerts are just noise from normal API integration code. You can use this node to pull job data into n8n without worrying about it siphoning your secrets.
No findings
The analyzer reported nothing for this version.
No findings
The analyzer reported nothing for this version.
AI Security Report
AI Security Review
Evidence context: threat category none; evidence quality strong.
The n8n-nodes-techmap package is a community node for the n8n workflow automation platform. Its stated purpose is to integrate with the Techmap job postings APIs, allowing users to search international job postings and build RSS feed URLs. The evidence bundle contains 27 total findings, split between 15 medium-severity IoC detections and 12 low-severity code-smell rules. There are zero findings for malware, tool-poisoning, obfuscation, or suspicious network behavior.
When we look at the tool-poisoning category, the count is exactly zero. The package does not contain hidden AI directives, invisible Unicode characters, or XML-style instruction tags aimed at manipulating an AI agent. This is expected, as n8n community nodes are workflow components rather than MCP servers that define tool descriptions for LLMs. The absence of tool-poisoning findings immediately removes the defining threat of the agent ecosystem from consideration.
Credential scope is minimal. The code-smell findings likely include generic matches for environment variable reads, which is standard practice for any node that needs an API key to authenticate with a third-party service like RapidAPI. There are no findings targeting sensitive local paths like .ssh, .aws, or .kube. The package does not attempt to harvest local secrets.
Network destinations are entirely consistent with the package documentation. The IoC findings list api.techmap.io, techmap.io, job-postings-rss-feed.p.rapidapi.com, and daily-international-job-postings.p.rapidapi.com. These are the exact endpoints a developer would expect to see when integrating with Techmap job data feeds via RapidAPI. The inclusion of docs.n8n.io and n8n.io simply reflects links to the n8n community node installation guides and the sustainable use license. There are no calls to unknown domains, telemetry servers, or suspicious external infrastructure.
The strongest counterargument to a clean bill of health is the sheer volume of code-smell findings. Twelve low-severity rules triggered, which might make a casual observer worry about hidden malicious logic. However, code-smell rules are documented false-positive drivers. They fire on basic Node.js patterns like process.env, fetch, and standard HTTP request structures. In a package that exists solely to make HTTP requests to an external API, these patterns are the entire point of the code. The IoC count is similarly inflated by the package legitimately listing its API endpoints in documentation or configuration files.
Ultimately, n8n-nodes-techmap does exactly what it says on the tin. It talks to Techmap and RapidAPI, reads standard environment variables for authentication, and avoids any suspicious behavior. The scanner tripped on normal API integration patterns, resulting in a noisy but entirely benign report.
Key Reasons
- Zero tool-poisoning findings and no hidden AI directives
- Network endpoints exclusively match documented Techmap and RapidAPI integrations
- No credential-access findings targeting sensitive local paths like .ssh or .aws
- Code-smell findings are standard Node.js HTTP and environment variable patterns
False Positive Considerations
- IoC extractor flagging legitimate API endpoints like api.techmap.io and rapidapi.com
- Code-smell rules triggering on standard Node.js HTTP request and process.env patterns
Reviewed 2026-10-10 · version 0.1.1; recommended action: suppress false positive; model confidence 95%.
Source Code Not Available
Source code is not available for this version of the extension.
About This Extension
Frequently Asked Questions
Similar Extensions
Related extensions from the same publisher or marketplace