FollowMe
A command-line tool to track and report URL redirects. FollowMe helps you understand the complete redirect chain of any URL by following each redirect step-by-step and providing a detailed report.
Features
- Track complete redirect chains for any URL
- Display status codes for each redirect step with color-coded output
- Save reports to files
- Simple command-line interface
- Cross-platform compatibility
- Colorized terminal output (with option to disable)
Installation
From PyPI (recommended)
pip install followme
From source
git clone git@github.com:rapidrabbitsoft/followme.git
cd followme
pip install -e .
Usage
Basic usage
followme https://example.com
This will display the redirect chain for the specified URL.
Save output to file
followme https://example.com -o redirect_report.txt
Disable colors
followme https://example.com --no-color
Examples
# Check a simple redirect
followme https://bit.ly/example
# Check a URL with multiple redirects
followme https://t.co/example
# Save the report to a file
followme https://example.com -o my_report.txt
# Disable colorized output
followme https://example.com --no-color
Output Format
The tool provides a clear, numbered list of each redirect in the chain with color-coded output:
- Bold text: Section headers
- Cyan: Original URL
- Yellow: Step numbers and redirect status codes (301, 302, 307, 308)
- Blue: Source URLs in the redirect chain
- Magenta: Destination URLs in the redirect chain
- Green: Final status codes (200) and "(final)" indicator
- Red: Error status codes
Redirect chain for https://example.com:
1. https://example.com --[301]--> https://www.example.com
2. https://www.example.com --[200]--> (final)
You can disable colors using the --no-color flag.
Requirements
- Python 3.7 or higher
- requests library
- colorama (optional, for Windows color support)
License
This project is licensed under the MIT License - see the LICENSE file for details.
Contributing
Contributions are welcome! Please feel free to submit a Pull Request.
Issues
If you encounter any issues, please report them on the GitHub issue tracker.
Metadata
Release files for followme 1.0.1
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | Provenance | Actions |
|---|---|---|---|---|
| followme-1.0.1.tar.gz | 5.5 kB | Without provenance | Details for followme-1.0.1.tar.gz |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Actions Reset |
|---|---|---|---|---|
| followme-1.0.1-py3-none-any.whl | Python 3 | none | any | Details for followme-1.0.1-py3-none-any.whl |
Total release size: 11.8 kB
Release files / followme-1.0.1.tar.gz
| Download URL | followme-1.0.1.tar.gz |
|---|---|
| Size | 5.5 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
934e4ac909ce33ab54e75dca3b10d61e137009c3af2663a130b14b896150131e
|
|
BLAKE2b-256 checksum How to use checksums |
4b9f48fa4217271ef7785d7211e7bda58cb595077d15bbdde6ec0d36708472c2
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/6.1.0 CPython/3.13.3
|
Release files / followme-1.0.1-py3-none-any.whl
| Download URL | followme-1.0.1-py3-none-any.whl |
|---|---|
| Size | 6.2 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
aff061e035046367fade2f26db6ebb23f08fd6fae06d5c4b639bb4cd681f6e1c
|
|
BLAKE2b-256 checksum How to use checksums |
72fc9e0d7c8cd44b899171927054c50b4ddb0ab2237d42d7dcadfd6935b1453e
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/6.1.0 CPython/3.13.3
|
Security for followme 1.0.1
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
No provenance found
None of the files in this release were uploaded with provenance metadata.
A note on package security
PyPI is a repository for distributing packages, not a service for auditing them. While third-party security researchers and our staff do their best to detect and remove malicious packages, PyPI cannot guarantee the quality, security or suitability of any given package.
To learn more about protecting yourself from malicious actors, visit our package security documentation.