Import a website's software
import_softwareTells the monitor what software the website and its server run, so their vulnerabilities are checked. Send a file's contents (package.json, package-lock.json, yarn.lock, pnpm-lock.yaml, bun.lock, mix.lock, composer.json/.lock, requirements.txt, Pipfile.lock, poetry.lock, Gemfile.lock, go.mod, Cargo.lock, pom.xml, .csproj, Dockerfile, docker-compose.yml, .nvmrc, .bun-version, .tool-versions, mise.toml, railpack.json) or a plain list with one item per line as "name version", for example "Debian 12", "nginx 1.24.0", "PHP 8.2.12", "wp-plugin:woocommerce 9.3.3", "npm:lodash 4.17.21". If you can run commands on the server, cat /etc/os-release, nginx -v, php -v and the like give exact versions. Importing the same filename again replaces what it added. Lines that name nothing known are returned as unrecognized. Format and supported files: https://upheron.com/docs/software. Free.
Tool call template
Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.
{
"id": 1,
"jsonrpc": "2.0",
"method": "tools/call",
"params": {
"arguments": {
"id": "<id>",
"content": "<content>"
},
"name": "import_software"
}
}Input Schema
| Name | Required | Description | Default |
|---|---|---|---|
| id | Yes | Monitor ID from list_monitors. | |
| name | No | A label such as frontend/package.json, to keep two files with the same name apart. Importing under the same label again replaces it. Defaults to the filename. | |
| content | Yes | The file's text, or the list. | |
| filename | No | The file's name, such as package-lock.json or Dockerfile; tells the format. Leave out for a plain list. |