Download the PHP package netresearch/nr-vault without Composer

On this page you can find all versions of the php package netresearch/nr-vault. It is possible to download/install these versions without Composer. Possible dependencies are resolved automatically.

FAQ

After the download, you have to make one include require_once('vendor/autoload.php');. After that you have to import the classes with use statements.

Example:
If you use only one package a project is not needed. But if you use more then one package, without a project it is not possible to import the classes with use statements.

In general, it is recommended to use always a project to download your libraries. In an application normally there is more than one library needed.
Some PHP packages are not free to download and because of that hosted in private repositories. In this case some credentials are needed to access such packages. Please use the auth.json textarea to insert credentials, if a package is coming from a private repository. You can look here for more information.

  • Some hosting areas are not accessible by a terminal or SSH. Then it is not possible to use Composer.
  • To use Composer is sometimes complicated. Especially for beginners.
  • Composer needs much resources. Sometimes they are not available on a simple webspace.
  • If you are using private repositories you don't need to share your credentials. You can set up everything on our site and then you provide a simple download link to your team member.
  • Simplify your Composer build process. Use our own command line tool to download the vendor folder as binary. This makes your build process faster and you don't need to expose your credentials for private repositories.
Please rate this library. Is it a good library?

Example code of netresearch/nr-vault

Informations about the package nr-vault

nr-vault: Secure Secrets Management for TYPO3

CI codecov OpenSSF Scorecard OpenSSF Best Practices TYPO3 PHP PHPStan Latest Release SLSA 3

Enterprise-grade secret management without enterprise-grade complexity.

The Problem

Your TYPO3 site integrates with Stripe, SendGrid, Google Maps, and a dozen other services. Where are those API keys right now?

Probably in plain text in LocalConfiguration.php, unencrypted in a database field, or hardcoded somewhere accessible to every backend user.

If your database leaks, your secrets leak. If you need to rotate a compromised key, you're editing config files and redeploying.

How Secrets Are Typically Stored

Method Security Operational Reality
External Services (HashiCorp Vault, AWS SM) ⭐⭐⭐⭐⭐ Infrastructure cost, network access, auth to service
Environment Variables ⭐⭐⭐ Deployment/host access required, restart to change, no rotation UI, no audit trail
Files outside webroot ⭐⭐⭐ Deployment/host access required, hard to rotate, no management interface
nr-vault (encrypted DB) ⭐⭐⭐⭐ Runtime manageable via TYPO3 backend, rotate anytime, full audit trail
Plain text in config/DB ⭐ ❌ No protection

Why nr-vault?

All "more secure" methods require either external infrastructure, deployment pipelines, or server access. And they all lack a management UI and audit trail.

Challenge Env Vars / Files nr-vault
Rotate a compromised API key Call DevOps, redeploy, restart Click in backend, done
See who accessed a secret Check deploy logs (if any) Full audit log with timestamps
Emergency credential revocation Wait for deployment pipeline Immediate via backend module
Non-technical editor updates SMTP password Create support ticket Self-service in backend
Compliance audit: prove access history Manually correlate logs Export tamper-evident audit trail

Solution

nr-vault provides:

Architecture

Encryption Model

Uses envelope encryption (same pattern as AWS KMS, Google Cloud KMS):

Benefits:

Quick Start

Store and Retrieve Secrets

Vault HTTP Client

Make authenticated API calls without exposing secrets to your code:

Secret placement options: Bearer, BasicAuth, Header, QueryParam, BodyField, ApiKey, OAuth2.

TCA Integration

CLI Commands

All 12 vault:* commands (full options and examples in Documentation/Developer/Commands.rst):

Requirements

Documentation

Full documentation is available in the Documentation/ folder and can be rendered with the TYPO3 documentation tools.

Render locally

Planning documents

Internal development documents are available in docs/:

Feature Comparison

Feature nr-vault Drupal Key Laravel Secrets Symfony Secrets
Envelope encryption Yes No No No
Per-secret DEKs Yes No No No
External vault support Planned Pluggable Limited HashiCorp
Access control BE groups + context By key N/A N/A
Audit logging Full + hash chain Limited None None
TCA/Form integration Native Form API N/A N/A
Key rotation CLI Yes Manual Yes Yes
HTTP client Yes No No No
OAuth auto-refresh Yes No No No

Roadmap

Installation

Or in DDEV:

License

GPL-2.0-or-later

[n] Developed by Netresearch DTT GmbH - Enterprise TYPO3 Solutions

All versions of nr-vault with dependencies

PHP Build Version
Package Version
Requires php Version ^8.2
ext-sodium Version *
ext-json Version *
typo3/cms-core Version ^13.4 || ^14.3
typo3/cms-backend Version ^13.4 || ^14.3
typo3/cms-install Version ^13.4 || ^14.3
psr/http-client Version ^1.0
psr/http-factory Version ^1.0
Composer command for our command line client (download client) This client runs in each environment. You don't need a specific PHP version etc. The first 20 API calls are free. Standard composer command

The package netresearch/nr-vault contains the following files

Loading the files please wait ...