Resources

Versioning & support

SDK compatibility, API stability, and how to reach us.

How Integrity versions its interfaces and where to get help.

SDK versioning#

The SDK packages use semantic versions. Their result parsers read required fields, tolerate additional response fields, and preserve the untouched server payload in raw. Pin the range your dependency policy permits and upgrade deliberately.

  • Python: triage-integrity-sdk on PyPI.
  • TypeScript: @triage-integrity/integrity-sdk on npm.

API stability#

REST classifier endpoints currently use the /v1 prefix. If an SDK receives a response shape that is missing a required field or has the wrong field type, it raises TriageResponseError rather than guessing. Check the installed SDK version and response shape before you change error handling.

Classifier artifacts#

Classifier artifacts are deployment state and do not share the REST /v1 version prefix. The current results do not expose one common artifact-version field, and project policy stores only its current values. After a classifier deployment or source-model change, review score distributions before you change enforcement thresholds. See Thresholds and calibration.

Support#

Product questions or access issues: info@triage-sec.com. Include your project ID, never your API key, so we can look up the relevant telemetry. Report vulnerabilities through the security disclosure process.