apicore
Set of core libraries usefull for building REST API and Microservices based on Flask.
The code is open source, release under MIT and written in Python 3.
pip install apicoreFeatures
Cross-origin resource sharing (CORS) ready
Data caching with redis server or in-memory
Configuration file loader
A simple Logger
Raise exception conform to HTTP status codes
Authorization using JSON Web Token(JWT) issued from an OpenID Connect provider.
Links
1 maintainer
Metadata
1 maintainer
Release files for apicore 1.2.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 |
|---|---|---|---|---|
| apicore-1.2.1.tar.gz | 4.2 MB | Without provenance | Details for apicore-1.2.1.tar.gz |
Release files / apicore-1.2.1.tar.gz
| Download URL | apicore-1.2.1.tar.gz |
|---|---|
| Size | 4.2 MB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
0894390ea504cd35a204e7e42ddadd6c68fac5ffbe4f37fc7aade7ba87665b2e
|
|
BLAKE2b-256 checksum How to use checksums |
e88e036ac799d2bacff3e43119003f1f49a5067a9b4474e0de64beac4a357fdb
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
Security for apicore 1.2.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.
