Download the PHP package dwenzel/reporter without Composer
On this page you can find all versions of the php package dwenzel/reporter. It is possible to download/install these versions without Composer. Possible dependencies are resolved automatically.
Informations about the package reporter
Reporter
Reporting extension for the TYPO3 CMS that provides additional reporting and auditing capabilities for TYPO3 instances.
Requirements
- TYPO3 CMS >= 12.4 or >= 13.4
- PHP >= 8.1
- Instance in Composer Mode
cpsit/auditorpackage for auditing functionalitycpsit/api-tokenpackage for API authenticationdwenzel/reporter-apipackage for API endpoints
What does it do
Reporter provides comprehensive reporting and auditing capabilities for your TYPO3 instance:
- System Information Toolbar: Displays bundle name and version in the TYPO3 backend toolbar
- Backend Reports Module: Detailed reports including:
- Composer bundle information
- Package dependency analysis
- Security and compliance auditing
- REST API Endpoints: External system integration capabilities
- Package Analysis: Extensive reflection system for composer package metadata
Features
Backend Integration
- System Information Toolbar integration showing current bundle status
- Dedicated Reports module with comprehensive package information
- Real-time dependency analysis and version tracking
API Capabilities
- REST API middleware for external integrations
- Custom route compilation and enhancement
- Standardized endpoints for system reporting
Package Analysis
The extension includes an extensive property reflection system that analyzes:
- Package properties (Name, Version, Description, License, Keywords, etc.)
- Distribution information (URL, Type, Reference)
- Source information (URL, Type, Reference)
- Configuration details (Scripts, Repositories, Extra data)
Installation
Install via Composer:
Activate the extension in the TYPO3 Extension Manager or via CLI:
API Configuration
The Reporter extension provides REST API endpoints for external system integration. Follow these steps to configure and use the API:
1. Import API Routes
Add the Reporter API route enhancers to your TYPO3 site configuration file (config/sites/{site-identifier}/config.yaml):
2. Generate API Token
The Reporter API uses token-based authentication via the cpsit/api-token package. Generate tokens using the CLI:
Interactive Mode:
Non-Interactive Mode:
JSON Output for Automation:
Backend Module:
- Navigate to System > API Token Management
- Click Create New Token
- Fill in name, description, and expiration
- Important: Copy the secret immediately - it won't be shown again!
3. API Usage
Available Endpoints
GET /api/reporter/v1/application/report- Retrieve application report data
Authentication Headers
All API requests require the following headers:
Example Requests
cURL:
HTTP File (for IDE testing):
Response Format
The API returns JSON responses with application report data including:
- Bundle information
- Package versions
- Dependency analysis
- System configuration details
4. Security Considerations
- Token Management: API tokens should be stored securely and rotated regularly
- Access Control: Limit API access to authorized systems only
- HTTPS: Always use HTTPS in production environments
- Expiration: Set appropriate expiration dates for tokens
Dependencies
-
Core Dependencies:
typo3/cms-core: ^12.4 || ^13.4typo3/cms-reports: ^12.4 || ^13.4cpsit/auditor: ^1.0.0cpsit/api-token: For API authenticationdwenzel/reporter-api: For API endpoints
- Development Dependencies:
- PHPUnit for testing
- PHP-CS-Fixer for code standards
- PHPStan for static analysis
- TYPO3 Rector for code migrations
All versions of reporter with dependencies
typo3/cms-reports Version ^12.4 || ^13.4
cpsit/auditor Version ^1.0.0
cpsit/api-token Version ^1.0.0
dwenzel/reporter-api Version ^1.0.0