v0.10.0
Highlights
Specialized AI services now authenticate through nr-vault — the DALL-E, FAL, Whisper, TTS, and DeepL single-task services previously read a plaintext API key from extension configuration and assembled their own Authorization header over a plain HTTP client. They now store an nr-vault secret identifier and authenticate through the audited secure HTTP client, exactly as the database-backed LLM providers have since ADR-012. The secret is resolved, injected, audited, and memory-scrubbed inside the vault and never surfaces in this extension's code.
FAL (Authorization: Key …) and DeepL (Authorization: DeepL-Auth-Key …) use the non-Bearer prefix option added in nr-vault 0.8.0. DeepL's Free/Pro endpoint routing stays automatic: the key is retrieved once, lazily, only to test the :fx suffix, then scrubbed — auth itself always flows through the secure client.
Breaking changes:
- Requires
netresearch/nr-vault ^0.8.0(theprefixoption). The composer floor is raised from^0.6.0 || ^0.7.0. - The specialized-service configuration keys are now vault identifiers:
providers.openai.apiKeyIdentifier,image.fal.apiKeyIdentifier, andtranslators.deepl.apiKeyIdentifier. Host applications that wrote plaintext keys into these settings must store a vault secret and write its identifier instead.
See ADR-030 for the design rationale. Full details in the changelog.
Installation
composer require netresearch/nr-llmPublication status
- TER: extensions.typo3.org/extension/nr_llm — 0.10.0 verified
- Packagist: packagist.org/packages/netresearch/nr-llm — 0.10.0 verified
- Documentation: docs.typo3.org/p/netresearch/nr-llm/0.10/en-us/ — render verified
Security
All release artifacts are signed with Sigstore keyless signing.
Verify signatures
cosign verify-blob \
--bundle nr-llm-0.10.0.zip.bundle \
--certificate-identity-regexp "https://github.com/netresearch/.*" \
--certificate-oidc-issuer "https://token.actions.githubusercontent.com" \
nr-llm-0.10.0.zipVerify checksums
sha256sum -c checksums.txtSoftware Bill of Materials (SBOM)
SBOMs are provided in both SPDX and CycloneDX formats for supply chain transparency.