Join us in London for Infosecurity Europe June 2 – 4, 2026 | Booth C69 | Excel London | Get a FREE ticket
Components
Encryption
- GETGet cryptographic algorithms associated with a single software component.
- POSTGet cryptographic algorithms associated with multiple software components in a single request.
- GETGet cryptographic algorithms used by a component across specified version ranges.
- POSTGet cryptographic algorithms used by multiple components across specified version ranges.
- GETGet component versions that contain or don't contain cryptographic algorithms within specified ranges.
- POSTGet multiple component versions that contain or don't contain cryptographic algorithms within specified ranges.
- POSTReturns the same message that was sent, used for health checks and connectivity testing
- GETGet cryptographic hints for a single component.
- POSTGet cryptographic hints for multiple components in a single request.
- GETGet cryptographic hints across version ranges - legacy endpoint.
- POSTGet cryptographic hints across version ranges - legacy endpoint.
- GETDownload cryptography detection ruleset as a tarball.
Dependencies
Geoprovenance
Licenses
Scanning
Semgrep
Vulnerabilities
curl --request GET \
--url http://api.scanoss.com/v2/cryptography/rulesets/{ruleset_name}/{version}/download{
"content_type": "<string>",
"data": "aSDinaTvuI8gbWludGxpZnk=",
"extensions": [
{
"@type": "<string>"
}
]
}Download cryptography detection ruleset as a tarball.
Downloads a compressed tarball containing cryptographic detection rules for various programming languages. Rulesets can be used with tools like SCANOSS Crypto Finder for cryptographic algorithm detection in source code.
Supported ruleset types:
- dca: Deep Code Analysis rules (for SCANOSS Crypto Finder)
- keywords: Keyword-based detection rules
Version can be:
- “latest”: Most recent version
- Specific version: e.g., “v1.2.3”
Response headers (via grpc-gateway):
- Content-Type: application/gzip
- Content-Disposition: attachment; filename=“scanoss-crypto--.tar.gz”
- SCANOSS-Ruleset-Name: Name of the ruleset
- SCANOSS-Ruleset-Version: Resolved version number
- X-Checksum-SHA256: SHA256 checksum of the tarball
curl --request GET \
--url http://api.scanoss.com/v2/cryptography/rulesets/{ruleset_name}/{version}/download{
"content_type": "<string>",
"data": "aSDinaTvuI8gbWludGxpZnk=",
"extensions": [
{
"@type": "<string>"
}
]
}Documentation Index
Fetch the complete documentation index at: https://docs.scanoss.com/llms.txt
Use this file to discover all available pages before exploring further.
Path Parameters
Name of ruleset to download (e.g., "dca", "keywords")
- "dca": Deep Code Analysis rules for using with SCANOSS Crypto Finder
- "keywords": Keyword-based detection rules
Version of the ruleset to download Use "latest" for the most recent version, or specify a version like "v1.2.3"
Response
A successful response.
Message that represents an arbitrary HTTP body. It should only be used for payload formats that can't be represented as JSON, such as raw binary or an HTML page.
This message can be used both in streaming and non-streaming API methods in the request as well as the response.
It can be used as a top-level request field, which is convenient if one wants to extract parameters from either the URL or HTTP template into the request fields and also want access to the raw HTTP body.
Example:
message GetResourceRequest {
// A unique request id.
string request_id = 1;
// The raw HTTP body is bound to this field.
google.api.HttpBody http_body = 2;
}
service ResourceService {
rpc GetResource(GetResourceRequest)
returns (google.api.HttpBody);
rpc UpdateResource(google.api.HttpBody)
returns (google.protobuf.Empty);
}Example with streaming methods:
service CaldavService {
rpc GetCalendar(stream google.api.HttpBody)
returns (stream google.api.HttpBody);
rpc UpdateCalendar(stream google.api.HttpBody)
returns (stream google.api.HttpBody);
}Use of this type only changes how the request and response bodies are handled, all other features will continue to work unchanged.