/librariesio/packages

POST /api/librariesio/packages

Price: 10 credits

Get cross-registry package details by platform and package name

How to use it

Get cross-registry open-source package details from Libraries.io by registry platform (npm, pypi, maven, cargo, go, nuget, packagist, rubygems and 20+ more) and package name. Returns the unified package model with SourceRank, stars/forks, dependent package and repository counts, contribution count, homepage/repository/registry links, language, keywords, license info (raw + SPDX-normalized), repository status, deprecation status, latest and latest-stable release numbers with publish dates, and the full release/version history (each with publish date and license).

Parameters

• access-token string required

Request body

• timeout integer — Max scrapping execution timeout (in seconds) (default: 300; min: 20; max: 1500)
• platform string required — Package manager / registry the package belongs to (one of: "npm", "pypi", "maven", "go", "nuget", "packagist", "cargo", "rubygems", "cocoapods", "pub", "bower", "cpan", "cran", "clojars", "hex", "conda", "hackage", "meteor", "homebrew", "puppet", "carthage", "swiftpm", "elm", "dub", "racket", "julia", "nimble", "haxelib", "purescript", "alcatraz", "inqlude"; examples: "npm", "pypi", "maven", "cargo", "go")
• name string required — Package name within the registry (e.g. 'react', '@types/node', 'group:artifact' for maven) (examples: "react", "@types/node", "requests", "org.apache.commons:commons-lang3"; minLength: 1)

Response

• @type string (default: "LibrariesioPackage")
• name string required
• platform string required
• description string nullable
• homepage string nullable
• repository_url string nullable
• package_manager_url string nullable
• funding_urls array (default: [])
• language string nullable
• keywords array (default: [])
• licenses string nullable
• normalized_licenses array (default: [])
• is_license_normalized boolean (default: false)
• repository_license string nullable
• repository_status string nullable
• status string nullable
• rank integer (default: 0)
• star_count integer (default: 0)
• fork_count integer (default: 0)
• dependent_count integer (default: 0)
• dependent_repo_count integer (default: 0)
• contribution_count integer (default: 0)
• code_of_conduct_url string nullable
• contribution_guidelines_url string nullable
• security_policy_url string nullable
• is_deprecated boolean (default: false)
• deprecation_reason string nullable
• latest_release_number string nullable
• latest_release_published_at string nullable
• latest_stable_release_number string nullable
• latest_stable_release_published_at string nullable
• latest_download_url string nullable
• version_count integer (default: 0)
• versions array (default: [])
  • @type string (default: "LibrariesioPackageVersion")
  • number string required
  • published_at string nullable
  • spdx_expression string nullable
  • original_license string nullable
  • researched_at string nullable
  • repository_sources array (default: [])
• web_url string (default: "")

Errors

• 422 — The request body did not validate Check the fields against this schema. A URN with the wrong prefix is the most common cause.
• 408 — The request ran past its time limit Raise `timeout` in the request body, up to the maximum this endpoint documents. Lowering `count` or turning off the `with_*` flags also helps, because less work finishes sooner.
• 412 — Package not found Retrying will not help: either the entity does not exist, or the input points at a different one.
• 429 — Too many requests: a rate limit or a usage window is exhausted When the response carries an X-Retry-After header, wait that many seconds and retry: the same number is in the body as `detail.retry_after`, and the limit clears once that window passes. The message in the body names the limit that was hit.
• 500 — Something broke on our side Retrying will not help. If it keeps happening, send us the X-Request-ID from the response headers.
• 529 — Rate limit reached, or the endpoint is overloaded Wait at least 30 seconds, then retry.

Response headers

• X-Error — Error message text (present only on error)
• X-Request-ID — Unique request identifier
• X-Execution-Time — Execution time in seconds
• X-Result-Count — How many records the body carries. 0 means an empty result, which is a normal answer and not by itself an error. A non-zero count can come back together with X-Error when the failure happened partway through — read this header and X-Error independently.
• X-Total-Available-Results — How many records exist for this query, when the endpoint can say. On a `dry_run` request this is the answer and the body is empty. It saturates: the endpoint's documented maximum means 'at least that many', any smaller number is exact.
• X-Warning — Present when the request body carried keys this endpoint does not document. They were ignored, so any filter you meant to apply through them did not apply. Check the spelling against this schema and retry.
• X-Retry-After — Seconds to wait before retrying. Present only on 429.