SECFE
Python module to download SEC filings from the EDGAR Database and extract sections of filings to perform keyword searches.
Brief Overview
What each module does
SEFD or SEC EDGAR Filing Downloader is a collection of functions to download filings from EDGAR from a CSV input file.
FSE or Filing Section Extractor is a collection of functions to search filings for a specific section and extract the entire section to an rtf file. Please note that funcionality may be limtied or broken for Mac users due to limited LXML capabilities.
SKiS or Section Keyword Search is a collection of functions to search filings sections for a list of keywords and output relevant paragraphs to an rtf file.
Install
From PyPI with pip:
$ pip install SECFE
Requirements
requests, bs4, lxml
Feedback, Issues, and Features:
Feedback
I'd love to get some feedback from users. I want to know how you are using SECFE, so I can focus on updating it in ways that improve your experience. If you'd like to do so you can email me at aarechiga1 at fordham.edu (NOTE: Email abuse will result in your email address being BLOCKED).
With that said, below are some guidelines for submitting issues on GitHub.
Bugs
If you experience any bugs when running the package please submit an issue with a description of the issue. Bugs will take priority over all other issues.
Bad Data
If you experience any problems with returned data please create an issue and include:
-
Code related to SECFE download or data extraction -
Data Returned -
Day and Approximate Time of Access
This will allow me to better identify what is causing the issue. If you'd rather not post this information on github, please email it to the email listed in the feedback section.
New Features
Please don't hesitate to ask for new features you'd like to see or make suggestions for improvements. You can open an issue here on github and I'll take a look at it as soon as I can.
Metadata
Release files for SECFE 0.3.2
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 |
|---|---|---|---|---|
| SECFE-0.3.2.tar.gz | 14.1 kB | Without provenance | Details for SECFE-0.3.2.tar.gz |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Actions Reset |
|---|---|---|---|---|
| SECFE-0.3.2-py3-none-any.whl | Python 3 | none | any | Details for SECFE-0.3.2-py3-none-any.whl |
Total release size: 27.4 kB
Release files / SECFE-0.3.2.tar.gz
| Download URL | SECFE-0.3.2.tar.gz |
|---|---|
| Size | 14.1 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
cccf4f19c5a8ee9e79959af1da410c2d476aec39f669beb096c7c5f4f82e8217
|
|
BLAKE2b-256 checksum How to use checksums |
9e4f9da79394b87cdda998aaab7d6cb69d33667f2ed130247c95a4d6fd605078
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/3.4.1 importlib_metadata/4.0.1 pkginfo/1.7.0 requests/2.25.1 requests-toolbelt/0.9.1 tqdm/4.60.0 CPython/3.9.5
|
Release files / SECFE-0.3.2-py3-none-any.whl
| Download URL | SECFE-0.3.2-py3-none-any.whl |
|---|---|
| Size | 13.4 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
b8c56743b5230be777a48ccbee01c3025a6837ff045c7978d57f8d675059ae1b
|
|
BLAKE2b-256 checksum How to use checksums |
4d1f3606661a9e151f975faddaaadb8e889af8c73d40d360fb97aa9e2d10e936
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/3.4.1 importlib_metadata/4.0.1 pkginfo/1.7.0 requests/2.25.1 requests-toolbelt/0.9.1 tqdm/4.60.0 CPython/3.9.5
|
Security for SECFE 0.3.2
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.