1 file was added to this release more than 14 days after its initial publication. Inspect the release files before installing.
This release has been yanked by its maintainers, and will be ignored by installers, except when explicitly specified.
Consider using release 0.1.0 instead.
Reason given by maintainers: Missing modernauth package.
# Django Rapyd ModernAuth
This package provides a custom User model where the username is the email address.
## Inspiration
Users today expect to use their email address as the username during authentication. This works well because:
Users already know their email addresses by heart.
Since email addresses are unique, users don’t need to remember yet another item when either signing up or logging into web applications. IMHO this is a significant factor that plays a vital role in user adoption.
This is a time tested model and many web applications today follow this.
However, Django’s default approach for authentication requires a user provide both a username and an email address during sign up and then just use the username during login.
## Usage
Note: Django recommends you do this right at the beginning of the project. Making this change mid-project becomes significantly harder.
Install the package with: ` pip install django-rapyd-modernauth `
Edit Django settings: - Add modernauth to INSTALLED_APPS. - Set AUTH_USER_MODEL = modernauth.User.
Create models with: ` ./manage.py migrate `
Metadata
Release files for django-rapyd-modernauth 0.0.2
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
File added late
1 file was uploaded more than 14 days after the first file in this release.
While project maintainers occasionally add legitimate files to an existing release, late additions can also indicate a security compromise.
We recommend inspecting the release files before installing.
Source distribution (sdist)
| File | Size | Uploaded | Provenance | Actions |
|---|---|---|---|---|
| django-rapyd-modernauth-0.0.2.tar.gz | 5.9 kB | Without provenance | Details for django-rapyd-modernauth-0.0.2.tar.gz |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Actions Reset |
|---|---|---|---|---|
| django_rapyd_modernauth-0.0.2-py3-none-any.whl | Python 3 | none | any | Details for django_rapyd_modernauth-0.0.2-py3-none-any.whl |
Total release size: 14.6 kB
Release files / django-rapyd-modernauth-0.0.2.tar.gz
| Download URL | django-rapyd-modernauth-0.0.2.tar.gz |
|---|---|
| Size | 5.9 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
c144a16d580401040ab176d388d60507599c8a52b3971ec1abb8843bf5667797
|
|
BLAKE2b-256 checksum How to use checksums |
6cae7ba3a895251727457e36670125784fa6b05bbdb801c92bd45f96a93d1768
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
Python-urllib/3.6
|
Release files / django_rapyd_modernauth-0.0.2-py3-none-any.whl
File added late
This file was uploaded more than 14 days after the first file in this release.
While project maintainers occasionally add legitimate files to an existing release, late additions can also indicate a security compromise.
We recommend inspecting the release file before installing.
| Download URL | django_rapyd_modernauth-0.0.2-py3-none-any.whl |
|---|---|
| Size | 8.7 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
c70ee21a6d65b6d3d3e356b8c3fb7d06b8a95f562b34db55cdc51f05e3f0399b
|
|
BLAKE2b-256 checksum How to use checksums |
2ceeeb8ee642d4e4eb941ba4481d3becc682a3e01a319f6196a4b121d62dde0f
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/3.8.0 pkginfo/1.8.3 readme-renderer/34.0 requests/2.27.1 requests-toolbelt/0.9.1 urllib3/1.26.12 tqdm/4.64.0 importlib-metadata/4.8.3 keyring/23.4.1 rfc3986/1.5.0 colorama/0.4.5 CPython/3.6.15
|
Security for django-rapyd-modernauth 0.0.2
Upload timing
Release file added late
1 file was uploaded more than 14 days after the first file in this release.
While project maintainers occasionally add legitimate files to an existing release, late additions can also indicate a security compromise.
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.