Download the PHP package litepie/otp without Composer
On this page you can find all versions of the php package litepie/otp. It is possible to download/install these versions without Composer. Possible dependencies are resolved automatically.
Package otp
Short Description A comprehensive Laravel package for generating, signing and managing OTP codes with multiple channels support
License MIT
Homepage https://github.com/litepie/otp
FAQ
Example:
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 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.
Informations about the package otp
Laravel OTP Package
A comprehensive Laravel package for generating, signing and managing OTP (One-Time Password) codes with multiple channels support.
📋 Requirements
- PHP 8.2 or higher
- Laravel 10.0, 11.0, or 12.0
🚀 Features
- ✅ Secure OTP Generation - Generate cryptographically secure OTP codes
- ✅ Digital Signing - Sign OTP codes for enhanced security and verification
- ✅ Multiple Delivery Channels - Email, SMS, Database, and custom channels
- ✅ Flexible Configuration - Customizable length, format, and expiration
- ✅ Rate Limiting - Built-in protection against abuse
- ✅ Multiple OTP Types - Login, email verification, password reset, 2FA, etc.
- ✅ Event System - Complete lifecycle events for monitoring and logging
- ✅ Queue Support - Background processing for sending OTPs
- ✅ Auto-cleanup - Automatic removal of expired OTPs
- ✅ Laravel 12 Ready - Full compatibility with the latest Laravel versions
- ✅ Production Ready - Thoroughly tested and optimized for production use
📦 Installation
You can install the package via Composer:
Publish Configuration
Publish the configuration file:
Run Migrations
Run the migrations to create the OTPs table:
Set Up Automatic Cleanup (Optional)
Add the following to your app/Console/Kernel.php file to automatically clean up expired OTPs:
🔧 Configuration
The configuration file config/otp.php allows you to customize:
- Default OTP Settings - Length, format, expiration, channels
- OTP Types - Specific settings for different use cases
- Rate Limiting - Prevent abuse with configurable limits
- Digital Signing - Secure OTP verification
- Channel Configuration - Email, SMS, and custom channel settings
- Automatic Cleanup - Keep your database clean
Environment Variables
Add these to your .env file:
📖 Usage
Quick Start
Advanced Usage
Exception Handling
🎯 OTP Types
The package supports multiple OTP types with individual configurations:
Built-in Types
| Type | Use Case | Default Length | Default Expiry |
|---|---|---|---|
login |
User authentication | 6 digits | 5 minutes |
email_verification |
Email verification | 6 digits | 10 minutes |
password_reset |
Password reset | 8 characters | 15 minutes |
two_factor |
2FA authentication | 6 digits | 3 minutes |
phone_verification |
Phone verification | 6 digits | 5 minutes |
Custom Types
Define custom OTP types in your configuration:
📡 Delivery Channels
Email Channel
Sends OTP via email using Laravel's notification system or traditional mail.
SMS Channel
Send OTPs via SMS using various providers:
Supported SMS Providers:
- Log (for testing)
- Nexmo/Vonage
- Twilio
- Custom providers (extensible)
Database Channel
Store OTP in database for manual retrieval:
Multiple Channels
Send via multiple channels simultaneously:
Custom Channels
Create custom delivery channels:
📊 Events
The package fires comprehensive events for monitoring and logging:
Available Events
OtpGenerated- When an OTP is generatedOtpSent- When an OTP is sent via a channelOtpVerified- When an OTP is successfully verifiedOtpFailed- When OTP verification fails
Event Listeners
Example Listener
🛠️ Artisan Commands
Cleanup Expired OTPs
🔒 Security Features
- Digital Signing - All OTPs are digitally signed using HMAC-SHA256
- Rate Limiting - Configurable rate limiting per identifier and type
- Secure Generation - Cryptographically secure random code generation
- Attempt Tracking - Track and limit verification attempts
- Automatic Cleanup - Remove expired OTPs automatically
- Timing Attack Protection - Use
hash_equals()for secure comparisons
🧪 Testing
Running Tests
Test Example
📚 Documentation
- Examples - Comprehensive usage examples
- Contributing - How to contribute
- Security - Security policy
- Changelog - Version history
🤝 Contributing
We welcome contributions! Please see CONTRIBUTING.md for details.
Development Setup
🔐 Security
If you discover a security vulnerability, please send an email to [email protected]. All security vulnerabilities will be promptly addressed.
📄 License
The MIT License (MIT). Please see License File for more information.
💖 Support
- ⭐ Star this repo if you find it helpful
- 🐛 Report issues on GitHub Issues
- 💡 Request features via GitHub Discussions
- 📧 Contact us at [email protected]
Made with ❤️ by Litepie
All versions of otp with dependencies
illuminate/support Version ^10.0|^11.0|^12.0
illuminate/database Version ^10.0|^11.0|^12.0
illuminate/mail Version ^10.0|^11.0|^12.0
illuminate/notifications Version ^10.0|^11.0|^12.0
illuminate/console Version ^10.0|^11.0|^12.0
illuminate/cache Version ^10.0|^11.0|^12.0