Package Version Vulnerability Check | Strale

The final charge is based on confirmed usage. Unused reserved credits return to your available balance.

Strale

Check a software package version for known vulnerabilities

Use a package name and version to request vulnerability information for that release. You may also include the package ecosystem in your query.

You receive

Review the vulnerability information returned for the package release you name. When CVE numbers, severity assessments or versions containing a fix are supplied, your Agent can group those details by finding, alongside any provided advisory references. This gives you the reported issues to examine before deciding on an upgrade.

Start with your task

Check [Lodash] version [4.17.21] for known security issues. If the name or version is missing, ask me simply; do not guess. Summarize only returned details. Mention an issue number, how serious it is, or a suggested update only if provided.

What to know

Available findings and their details depend on the response. A missing severity or fix version should remain unknown; no returned findings is not a safety guarantee. Information about a fixed version does not establish that your own installation has been updated.

Inputs & outputs

Inspect the current inputs, availability, and maximum charge before starting.

Input schema

Input schema
Field / Path	Type	Requirement	Meaning
queryParams`queryParams`	`object`	Required	Required fields `package_name, version`
Version to look up`queryParams.version`	`string`	Required	Required text specifying that package’s version. Use the release you want reviewed; the definition sets no version format and does not automatically choose the newest release.
Software package ecosystem`queryParams.ecosystem`	`string`	Optional	Optional text describing the ecosystem for this package. The native description names npm, pypi, maven, go, cargo and nuget; these labels are not an enum. No default is specified for omission.
Software package name`queryParams.package_name`	`string`	Required	Required text naming the package whose version you are checking. Supply its actual package name together with version. The definition does not set a naming syntax.

View raw JSON

{
  "type": "object",
  "required": [
    "queryParams"
  ],
  "properties": {
    "queryParams": {
      "type": "object",
      "required": [
        "package_name",
        "version"
      ],
      "properties": {
        "version": {
          "type": "string"
        },
        "ecosystem": {
          "type": "string",
          "description": "Package ecosystem: npm, pypi, maven, go, cargo or nuget."
        },
        "package_name": {
          "type": "string"
        }
      }
    }
  },
  "additionalProperties": false
}

Result schema

Output fields have not been documented yet.

Additional notes

Preparing the lookup

The owning input definition requires package_name and version as text. ecosystem is optional text; its description names npm, pypi, maven, go, cargo and nuget without defining an enum or an omitted-value default. It supplies no naming or version-format rule. This definition identifies a package release rather than taking a project dependency file or a CVE number. Replace the brackets in the example request with your real values before using it.

Find the software name and version
Use the name and version number shown for the software you want to check. For example, [Lodash] and [4.17.21]. If you do not know the version, tell the assistant and ask what to look for.
Get connected
Ask the assistant to check
Paste both details into the task box above. If you do not know one, say so; the assistant should ask in simple words before checking.
Check [Lodash] version [4.17.21] for known security issues. If the name or version is missing, ask me simply; do not guess. Summarize only returned details. Mention an issue number, how serious it is, or a suggested update only if provided.
Review the result
Review any security issues and suggested update version the lookup actually returns. No issues returned does not prove the software is safe, and a suggested version does not mean it has already been installed.