> ## 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. # Get component versions that contain or don't contain cryptographic algorithms within specified ranges. > Returns lists of versions that either contain cryptographic algorithms or don't, helping assess cryptographic presence across component evolution. See: https://github.com/scanoss/papi/blob/main/protobuf/scanoss/api/cryptography/v2/README.md#componentversionsinrange ## OpenAPI ````yaml /api-reference/cryptography-openapi.json get /v2/cryptography/algorithms/versions/range/component openapi: 3.0.0 info: title: SCANOSS Cryptography Service description: >- Cryptography service provides cryptographic intelligence for software components including algorithm detection and encryption analysis. version: '2.0' contact: name: scanoss-cryptography url: https://github.com/scanoss/cryptography email: support@scanoss.com servers: - url: http://api.scanoss.com - url: https://api.scanoss.com security: [] tags: - name: Cryptography paths: /v2/cryptography/algorithms/versions/range/component: get: tags: - Cryptography summary: >- Get component versions that contain or don't contain cryptographic algorithms within specified ranges. description: >- Returns lists of versions that either contain cryptographic algorithms or don't, helping assess cryptographic presence across component evolution. See: https://github.com/scanoss/papi/blob/main/protobuf/scanoss/api/cryptography/v2/README.md#componentversionsinrange operationId: Cryptography_GetComponentVersionsInRange parameters: - name: purl description: Package URL identifying the component to analyze. in: query required: true schema: type: string - name: requirement description: >- Version constraint for component resolution when PURL lacks explicit version. in: query required: false schema: type: string responses: '200': description: A successful response. content: application/json: schema: $ref: '#/components/schemas/v2ComponentVersionsInRangeResponse' '404': description: Returned when the resource does not exist. content: application/json: schema: type: string format: string default: description: An unexpected error response. content: application/json: schema: $ref: '#/components/schemas/rpcStatus' components: schemas: v2ComponentVersionsInRangeResponse: type: object example: component: purl: pkg:github/scanoss/engine versions_with: - 2.0.0 - 3.0.0 - 4.0.0 versions_without: - 1.0.0 - 1.5.0 status: status: SUCCESS message: Version ranges Successfully retrieved properties: component: $ref: '#/components/schemas/v2ComponentVersionsInRangeResponseComponent' status: $ref: '#/components/schemas/v2StatusResponse' description: >- Response message for ComponentVersionsInRange method. Contains version lists for a single component categorized by cryptographic algorithm presence, helping assess cryptographic adoption across component evolution. rpcStatus: type: object properties: code: type: integer format: int32 message: type: string details: type: array items: $ref: '#/components/schemas/protobufAny' v2ComponentVersionsInRangeResponseComponent: type: object properties: purl: type: string title: Package URL (PURL) uniquely identifying the component versions_with: type: array items: type: string title: >- List of versions in the specified range that contain cryptographic algorithms versions_without: type: array items: type: string title: >- List of versions in the specified range that do not contain cryptographic algorithms info_message: type: string description: Status message describing the outcome of processing this component. info_code: type: string description: |- Status code identifying the outcome of processing this component. Possible values: - "INVALID_PURL": The provided Package URL (PURL) is invalid or malformed. - "COMPONENT_NOT_FOUND": The requested component could not be found in the database. - "NO_INFO": No cryptography information is available for the requested component. description: >- Version information for a specific component categorized by cryptographic presence. v2StatusResponse: type: object properties: status: $ref: '#/components/schemas/v2StatusCode' message: type: string title: Status message db: $ref: '#/components/schemas/StatusResponseDB' server: $ref: '#/components/schemas/StatusResponseServer' description: Detailed response details. protobufAny: type: object properties: '@type': type: string description: >- A URL/resource name that uniquely identifies the type of the serialized protocol buffer message. This string must contain at least one "/" character. The last segment of the URL's path must represent the fully qualified name of the type (as in `path/google.protobuf.Duration`). The name should be in a canonical form (e.g., leading "." is not accepted). In practice, teams usually precompile into the binary all types that they expect it to use in the context of Any. However, for URLs which use the scheme `http`, `https`, or no scheme, one can optionally set up a type server that maps type URLs to message definitions as follows: * If no scheme is provided, `https` is assumed. * An HTTP GET on the URL must yield a [google.protobuf.Type][] value in binary format, or produce an error. * Applications are allowed to cache lookup results based on the URL, or have them precompiled into a binary to avoid any lookup. Therefore, binary compatibility needs to be preserved on changes to types. (Use versioned type names to manage breaking changes.) Note: this functionality is not currently available in the official protobuf release, and it is not used for type URLs beginning with type.googleapis.com. As of May 2023, there are no widely used type server implementations and no plans to implement one. Schemes other than `http`, `https` (or the empty scheme) might be used with implementation specific semantics. additionalProperties: {} description: >- `Any` contains an arbitrary serialized protocol buffer message along with a URL that describes the type of the serialized message. Protobuf library provides support to pack/unpack Any values in the form of utility functions or additional generated methods of the Any type. Example 1: Pack and unpack a message in C++. Foo foo = ...; Any any; any.PackFrom(foo); ... if (any.UnpackTo(&foo)) { ... } Example 2: Pack and unpack a message in Java. Foo foo = ...; Any any = Any.pack(foo); ... if (any.is(Foo.class)) { foo = any.unpack(Foo.class); } // or ... if (any.isSameTypeAs(Foo.getDefaultInstance())) { foo = any.unpack(Foo.getDefaultInstance()); } Example 3: Pack and unpack a message in Python. foo = Foo(...) any = Any() any.Pack(foo) ... if any.Is(Foo.DESCRIPTOR): any.Unpack(foo) ... Example 4: Pack and unpack a message in Go foo := &pb.Foo{...} any, err := anypb.New(foo) if err != nil { ... } ... foo := &pb.Foo{} if err := any.UnmarshalTo(foo); err != nil { ... } The pack methods provided by protobuf library will by default use 'type.googleapis.com/full.type.name' as the type URL and the unpack methods only use the fully qualified type name after the last '/' in the type URL, for example "foo.bar.com/x/y.z" will yield type name "y.z". JSON ==== The JSON representation of an `Any` value uses the regular representation of the deserialized, embedded message, with an additional field `@type` which contains the type URL. Example: package google.profile; message Person { string first_name = 1; string last_name = 2; } { "@type": "type.googleapis.com/google.profile.Person", "firstName": , "lastName": } If the embedded message type is well-known and has a custom JSON representation, that representation will be embedded adding a field `value` which holds the custom JSON in addition to the `@type` field. Example (for message [google.protobuf.Duration][]): { "@type": "type.googleapis.com/google.protobuf.Duration", "value": "1.212s" } v2StatusCode: type: string enum: - UNSPECIFIED - SUCCESS - SUCCEEDED_WITH_WARNINGS - WARNING - FAILED default: UNSPECIFIED description: Status code Enum. StatusResponseDB: type: object properties: schema_version: type: string title: Semantic schema version (e.g., 'v1.0.0') created_at: type: string title: When this DB was built (ISO 8601 format) description: Database version information. StatusResponseServer: type: object properties: version: type: string title: Semantic version (e.g., 'v1.0.0') description: Server information. ````