How AI is applied across API Evangelist and APIs.io. Read my AI disclosure →
API Evangelist API Evangelist
Discovery
Learnings
Guidance
Toolbox
Alignment
API Evangelist LLC

Mend Vulnerable Libraries API

The Vulnerable Libraries API from Mend — 1 operation(s) for vulnerable libraries.

Mend Vulnerable Libraries API is one of 47 APIs that Mend publishes on the APIs.io network, described by a machine-readable OpenAPI specification.

Tagged areas include Vulnerable Libraries. The published artifact set on APIs.io includes an OpenAPI specification and an API reference.

This API exposes 1 operation across 1 path, and defines 12 schemas. It is described by OpenAPI 3.0.1, at version 3.0.

Requests are made against a single base URL, https://baseUrl.

1 operations 1 paths 12 schemas 1 GET

Metadata

The identity and technical contract details declared by the specification.

Specification
OpenAPI 3.0.1
API Version
3.0
Base URL
https://api-saas.mend.io
Authentication
HTTP Bearer
Resource Areas
1

Authentication & Security 1

Mend Vulnerable Libraries API declares 1 security scheme for authenticating requests. It accepts HTTP bearer tokens (JWT) (bearer-key). By default, every request must be authenticated.

  • bearer-key — JWT token Bearer

Paths & Operations 1

Across 1 path, the API surfaces 1 operation — 1 GET. Each is listed below with its method, path, parameters, and response codes.

Vulnerable Libraries 1
GET
/api/v2.0/orgs/{orgToken}/vulnerabilities/{vulnerabilityName}/libraries
Get Vulnerable Libraries By CVE
getVulnerableLibrariesByCVE 2 params → 200400403

Schemas 12

The contract defines 12 schemas that model the data the API accepts and returns. The most detailed are LightLibraryDTO (27 properties), TrackedIssueDTO (17 properties), LibraryExtraInfoDTO (7 properties), ProprietaryInfoDTO (5 properties). Each schema is shown below with its type and property counts.

UserInfoDTO
object
5 properties 1 required
LibraryLocationDTO
object
2 properties
NoticeDTO
object
2 properties 1 required
ProprietaryInfoDTO
object
5 properties
SecurityRiskDTO
object
2 properties
AttributionReportLibrarySettingRuleDTO
object
1 property
TrackedIssueDTO
object
17 properties
LibraryExtraInfoDTO
object
7 properties
DWRResponseBase
object
1 property
DWRResponseListLightLibraryDTO
object
2 properties
LightLibraryDTO
object
27 properties
EntityDTO
object
2 properties

Specification

The full machine-readable OpenAPI contract behind this narrative.

Source

mend-vulnerable-libraries-api-openapi.yml Raw ↑

Other APIs Mend publishes across the network.

Mend Access Management API
Mend Access Management - Organizations API
Mend Administration - Groups API
Mend Administration - Labels API
Mend Administration - Users API
Mend AI API
Mend Alerts - Product API
Mend Alerts - Project API
Mend Applications API
Mend Asynchronous Process Control API
Mend CustomAttribute - Organization API
Mend CustomAttribute - Product API
Where this information came from

This is an independent, third-party profile of Mend Vulnerable Libraries API, published by API Evangelist. We do not operate, host, resell, or support these APIs, and we are not affiliated with or endorsed by the company unless stated above. Everything here is built from publicly available information — the company's own site, developer portal, documentation, public repositories, and the specifications it publishes for public use. Nothing is obtained by breaching a system, defeating an access control, or using credentials.

The Kin Score and Agent Readiness rating are independently calculated assessments of a company's public API artifacts, scored against a published rubric. They are not certifications, endorsements, security assessments, or audits.

Corrections, re-scores, and removal are free — no partnership or purchase required, and you do not need to justify the request. A removed company is recorded as unrated, never scored zero for having asked. Acknowledgement within one business day; removal within two.

info@apievangelist.com · Read the full data-sourcing policy →
On a security or compliance team? Put security in the subject line and you will get a person, not a form — we will tell you exactly which public URLs this profile was built from.