🚨 Project Renamed: jailed-path → strict-path

⚠️ IMPORTANT NOTICE: This crate has been renamed and moved

The jailed-path crate has been renamed to strict-path and is no longer maintained under this name.

🔄 Migration Instructions

1. Update your Cargo.toml

# ❌ Old (deprecated)
[dependencies]
jailed-path = "0.x.x"

# ✅ New (actively maintained)
[dependencies]
strict-path = "*"

2. Update your imports

// ❌ Old
use jailed_path::*;

// ✅ New  
use strict_path::*;

3. API is identical - only the crate name changed

The API remains the same, so your existing code will work with just the dependency and import changes above.

🎯 Why the rename?

• strict-path better reflects the crate's purpose: strict path validation and security
• Clearer naming helps users understand this is about path restriction rather than sandboxing
• Better alignment with Rust naming conventions and the security domain

🚀 New Location & Resources

✨ What's New in strict-path

The renamed crate includes significant improvements:

• 🏠 OS Directory Support: Native constructors for standard directories (home, temp, config, etc.)
• 📚 Complete Documentation: Comprehensive mdBook guide with examples and best practices
• 🛡️ Enhanced Security: Protection against 19+ real-world CVEs including recent Windows vulnerabilities
• 🔧 Better API: Improved function signatures and error handling
• ⚡ Performance: Zero-allocation interop with existing std::path code

🚨 Action Required

This jailed-path crate will not receive further updates. Please migrate to strict-path to receive:

• ✅ Security updates and CVE protections
• ✅ New features and improvements
• ✅ Bug fixes and performance optimizations
• ✅ Community support and documentation

📞 Need Help?

• Issues & Questions: GitHub Issues
• Complete Migration Guide: Documentation
• Examples & Tutorials: Guide Website

🔗 Migrate to strict-path now →