Free tools for developers
Small, free tools from AIssue that answer one question well. No account and nothing to install: use the tool, get the answer. When you want the same check every day, a free account does it for you.
Dependency security
Dependency vulnerability check
Drop a lockfile (requirements.txt, package-lock.json, poetry.lock and more). We check every package version against the OSV.dev vulnerability database and email you a report with fix commands and a ready-made prompt for your coding agent.
Open the toolGitHub repo vulnerability check
Paste the address of a public GitHub repository. We find every lockfile on its default branch, check each package version against OSV.dev and email you the report, grouped by lockfile, with the fixes.
Open the toolPackage vulnerability database
Search a package to see which of its versions have known vulnerabilities, how severe they are, the version that fixes them and the command to upgrade. Every advisory has its own page.
Open the toolAdvisory digest for your stack
Pick the packages you care about by name, or a ready-made stack (Django, FastAPI, Next.js, Rails...). Every week or every day, get the new and updated advisories for them, with severity, affected versions and the fixed version.
Open the toolFor monitored repositories
Licences, SBOM and AI compliance
EU AI Act risk check
Answer about 15 questions about your AI system. See its likely risk category under the EU AI Act, whether you are its provider or deployer, and a checklist of obligations with articles and dates.
Open the toolDependency licence check
Drop a lockfile and say what you are building. We look up the licence of every package version and email you the counts, with GPL, AGPL, unknown and source-available licences flagged for your kind of project and explained in plain words.
Open the toolSBOM summary generator
Drop a lockfile and get a readable SBOM summary by email: the components, their licences, known vulnerabilities, the AI components in your dependencies and how it measures up to the NTIA minimum elements. The CycloneDX and SPDX files are part of Pro.
Open the toolMCP config audit
Paste an MCP config (mcp.json, claude_desktop_config.json, .vscode/mcp.json...). It is checked in your browser, without being uploaded, for written-in tokens, servers that run whatever version is latest, plain-HTTP remotes and filesystem access that is too broad.
Open the toolLast updated .