Hub · Entwicklung & APIs

Sicherwerk

23 veröffentlichte Endpunkt-URLs. Methoden, Preise, Eingaben und Originaldokumentation auf jeder Detailseite.

sicher.halowerk.com · Katalogstand 2026-11-01, 15:19 UTC

Endpunkte

1–23 von 23

Sicherwerk0,005 USDC
container inspect
POSThttps://sicher.halowerk.com/v1/container-inspect
Reads the manifest and config of an OCI or Docker image straight from the registry — a few kilobytes, never the layers, and the image is never run. Returns the digest, the platforms a multi-arch index covers, every layer with its size and t
Sicherwerk0,005 USDC
cve check
POSThttps://sicher.halowerk.com/v1/cve-check
Queries OSV.dev for a list of packages with versions across npm, PyPI, Go, Maven, crates.io, NuGet, RubyGems, Packagist and the Linux distributions. For each package it returns the vulnerabilities found with their identifiers, severity and
Sicherwerk0,005 USDC
hash reputation
POSThttps://sicher.halowerk.com/v1/hash-reputation
Queries three abuse.ch metadata services for an MD5, SHA-1 or SHA-256 value. It reports known malware metadata, associated ThreatFox indicators, and URLhaus payload provenance, then derives a conservative known-malicious or unknown verdict.
Sicherwerk0,002 USDC
jwt verify
POSThttps://sicher.halowerk.com/v1/jwt-verify
Decodes a JWT and checks it in two layers. Structure and claims: expiry, not-before and issued-at against the current time with the clock skew you allow, issuer and audience against the values you expect, and the token lifetime. Signature:
Sicherwerk0,002 USDC
license check
POSThttps://sicher.halowerk.com/v1/license-check
Looks up the declared licence of each package through deps.dev and sorts the result by the only question that matters for a closed, sold product: what does this licence demand. Permissive licences need attribution. Weak copyleft affects cha
Sicherwerk0,005 USDC
log chain verify
POSThttps://sicher.halowerk.com/v1/log-chain-verify
Recomputes every record hash from a canonical JSON representation of id, sequence, timestamp, previous_hash and payload, then checks that each record points to the hash of the record before it. If a root_hash is supplied, the same computed
Sicherwerk0,002 USDC
oss gnupg detached signature verify
POSThttps://sicher.halowerk.com/v1/oss-gnupg-detached-signature-verify
Checks a detached OpenPGP signature against the bytes it claims to cover, using the pinned GnuPG build and nothing else. What comes back is the verdict in GnuPG's own terms, the fingerprint that actually signed, the signature timestamp, the
Sicherwerk0,001 USDC
oss openssl asn1 structure diagnose
POSThttps://sicher.halowerk.com/v1/oss-openssl-asn1-structure-diagnose
Parses a definite-length binary artifact and returns every ASN.1 object it contains with its byte offset, nesting depth, header and content lengths, whether it is constructed, and the type as OpenSSL names it. This is the tool for the momen
Sicherwerk0,002 USDC
oss openssl certificate bundle normalize
POSThttps://sicher.halowerk.com/v1/oss-openssl-certificate-bundle-normalize
API operation: oss openssl certificate bundle normalize. Use the linked input schema for request fields and the hub documentation for response fields, coverage and limitations.
Sicherwerk0,002 USDC
oss openssl cms envelope encrypt
POSThttps://sicher.halowerk.com/v1/oss-openssl-cms-envelope-encrypt
Wraps the supplied bytes in a CMS EnvelopedData envelope using the pinned OpenSSL build, addressed to every recipient certificate you pass in. A single content-encryption key protects the payload and is itself encrypted once per recipient,
Sicherwerk0,002 USDC
oss openssl csr self signature audit
POSThttps://sicher.halowerk.com/v1/oss-openssl-csr-self-signature-audit
Runs the pinned OpenSSL build against a submitted certificate request and answers two questions a registration authority has to settle before it signs anything: does the request carry a valid self-signature over its own body, and what exact
Sicherwerk0,003 USDC
oss openssl dh group check
POSThttps://sicher.halowerk.com/v1/oss-openssl-dh-group-check
Runs the pinned OpenSSL build's parameter checks over a supplied finite-field Diffie-Hellman group and reports whether it passes, along with the detail output that says why. The point is to catch parameters that are syntactically fine but c
Sicherwerk0,002 USDC
oss openssl pkcs12 certificate store build
POSThttps://sicher.halowerk.com/v1/oss-openssl-pkcs12-certificate-store-build
Builds a PKCS#12 container holding certificates only, for the common case where a runtime insists on PKCS#12 as its trust store format. The password is explicitly empty and reported back as such, so nothing depends on an undocumented defaul
Sicherwerk0,002 USDC
oss openssl public key math audit
POSThttps://sicher.halowerk.com/v1/oss-openssl-public-key-math-audit
Takes a public key in SubjectPublicKeyInfo PEM form and runs the pinned OpenSSL build's own consistency checks over it, then reports the algorithm, the key size in bits and the parameters it found. This catches keys that parse but are struc
Sicherwerk0,001 USDC
oss openssl rfc3161 request build
POSThttps://sicher.halowerk.com/v1/oss-openssl-rfc3161-request-build
Produces a ready-to-post RFC 3161 TimeStampReq for a SHA-256 digest you already computed. The pinned OpenSSL build encodes the message imprint, adds a fresh nonce so a replayed response can be detected, and sets the flag that asks the times
Sicherwerk0,001 USDC
oss openssl tls12 cipher policy expand
POSThttps://sicher.halowerk.com/v1/oss-openssl-tls12-cipher-policy-expand
Takes a cipher policy in OpenSSL syntax and resolves it into the concrete list of TLS 1.2 cipher suites that the pinned build would actually offer, in the order it would offer them. This closes the gap between a policy string in a configura
Sicherwerk0,001 USDC
oss openssl x509 purpose evaluate
POSThttps://sicher.halowerk.com/v1/oss-openssl-x509-purpose-evaluate
Reads the constraints inside a single certificate — basic constraints, key usage, extended key usage — and reports, per role, whether the certificate permits being used that way under the pinned OpenSSL build's rules. Roles covered are TLS
Sicherwerk0,0025 USDC
oss sqlite database integrity audit
POSThttps://sicher.halowerk.com/v1/oss-sqlite-database-integrity-audit
Opens a supplied SQLite database read-only with the pinned engine and asks it the two questions it answers about itself: whether the file structure is intact, and whether any row points at a parent that is not there. What comes back is the
Sicherwerk0,002 USDC
oss zip archive inventory audit
POSThttps://sicher.halowerk.com/v1/oss-zip-archive-inventory-audit
Reads the central directory of a supplied ZIP archive with the pinned unzip build and reports what it would do if you unpacked it, without unpacking anything. Every entry is listed with its uncompressed size and method, and three specific h
Sicherwerk0,005 USDC
provenance verify
POSThttps://sicher.halowerk.com/v1/provenance-verify
Searches the Sigstore Rekor log for entries matching an artefact hash and returns what a provenance claim is actually worth: the log index and inclusion time, the signing identity from the certificate, and where available the source reposit
Sicherwerk0,005 USDC
sbom
POSThttps://sicher.halowerk.com/v1/sbom
Parses package-lock.json, package.json, requirements.txt, go.mod and Cargo.lock and emits a bill of materials in CycloneDX 1.5 or SPDX 2.3, with a package URL per component. The distinction that decides whether the document is worth anythin
Sicherwerk0,002 USDC
tls chain
POSThttps://sicher.halowerk.com/v1/tls-chain
Opens a TLS connection and reports the chain the server presents. Per certificate: subject and issuer, validity window with days remaining, serial, SHA-256 fingerprint, key type and size, and the subject alternative names.
Sicherwerk0,002 USDC
webhook signature
POSThttps://sicher.halowerk.com/v1/webhook-signature
Providers each build their signing string differently — some sign only the body, others prepend a timestamp, an id, or a version marker in a fixed order — and getting that order wrong produces a mismatch that looks exactly like an attack. T