sec-ai
Essentials ➔
Health ➔
Quality ➔
Distribution ➔
Community ➔
Overview
sec-ai is an open-source project designed to provide a comprehensive toolset for analyzing and interpreting data from SEC filings. Utilizing advanced AI technologies, this project aims to serve a wide range of users, from individual investors to researchers and regulatory bodies.
The project leverages alphanome-ai/sec-parser for its data extraction needs, an essential component that simplifies the parsing of SEC EDGAR HTML documents into a structured and analyzable format.
- Explore the Demo
- Read the Documentation
- Join the Discussions to get help, propose ideas, or chat with the community
- Report bugs in Issues
- Stay updated and contribute to our project's direction in Announcements and Roadmap
- Learn How to Contribute
Disclaimer
Warning This project,
sec-ai, is an independent, open-source initiative and has no affiliation, endorsement, or verification by the United States Securities and Exchange Commission (SEC). It utilizes public APIs and data provided by the SEC solely for research, informational, and educational objectives. This tool is not intended for financial advisement or as a substitute for professional investment advice or compliance with securities regulations. The creators and maintainers make no warranties, expressed or implied, about the accuracy, completeness, or reliability of the data and analyses presented. Use this software at your own risk. For accurate and comprehensive financial analysis, consult with qualified financial professionals and comply with all relevant legal requirements. The project maintainers and contributors are not liable for any financial or legal consequences arising from the use of this tool.
Getting Started
To get started, first install the sec-ai package:
pip install sec-ai
Warning We're thrilled to inform you that the
sec-parserproject is the final prerequisite for launching our eagerly anticipated feature, sec-ai. We're diligently working to ensure that it meets all the necessary standards and functionalities.
Stay Informed: For detailed information and updates specific tosec-parserand to be the first to know when sec-ai is launched, please follow our Announcements page.
Contribute to sec-parser: If you're as excited aboutsec-parserand the upcoming sec-ai feature as we are, we warmly invite you to get involved!
- Please visit our Contribution Guide for sec-parser.
- Explore current Issues or propose new enhancements tosec-parser.
Our targeted launch for sec-ai is approaching, and we're grateful for your continued anticipation and interest, which are invaluable to our endeavors.
Best Practices
How to Import Modules In Your Code
To ensure your code remains functional even when we update sec-ai, it's recommended to avoid complex imports. Don't use intricate import statements that go deep into the package, like this:
from sec_ai.some_package.internal_utils import SomeInternalClass
Here are the suggested ways to import modules from sec-ai:
Basic Import
- Standard Way: Use
import sec_ai as sai
This imports the main package assai. You can then access its functionalities usingsai.prefix.
Specific Import
- Package-Level Import: Use
from sec_ai import SomeClass
This allows you to directly useSomeClasswithout any prefix.
Submodule Import
- Submodule: Use
from sec_ai import some_package
This imports thesome_packagesubmodule, and you can access its classes and functions usingsome_package.prefix.
More Specific Submodule Import
- Submodule-Level: Use
from sec_ai.some_package import SomeClass
This imports a specific classSomeClassfrom thesome_packagesubmodule.
Note The main package
sec_aicontains only the most common functionalities. For specialized tasks, please use submodule or submodule-level imports.
Contributing
For information about setting up the development environment, coding standards, and contribution workflows, please refer to our CONTRIBUTING.md guide.
License
This project is licensed under the MIT License - see the LICENSE file for details.
Metadata
Release files for sec-ai 0.7.0.post17
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 |
|---|---|---|---|---|
| sec_ai-0.7.0.post17.tar.gz | 6.2 kB | Without provenance | Details for sec_ai-0.7.0.post17.tar.gz |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Actions Reset |
|---|---|---|---|---|
| sec_ai-0.7.0.post17-py3-none-any.whl | Python 3 | none | any | Details for sec_ai-0.7.0.post17-py3-none-any.whl |
Total release size: 11.9 kB
Release files / sec_ai-0.7.0.post17.tar.gz
| Download URL | sec_ai-0.7.0.post17.tar.gz |
|---|---|
| Size | 6.2 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
0db689e56d5b514a1c1622909f170ac54dcee5e4a7ee555e91783a48eab5c8be
|
|
BLAKE2b-256 checksum How to use checksums |
245233c770a00552fad32c5fb6b33fd4c62e3d8c3c26c29c8b72d638ff3cd531
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
poetry/1.6.1 CPython/3.11.5 Linux/6.2.0-1012-azure
|
Release files / sec_ai-0.7.0.post17-py3-none-any.whl
| Download URL | sec_ai-0.7.0.post17-py3-none-any.whl |
|---|---|
| Size | 5.7 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
02017fd220ab520e633c6ea050494a32756131f91bb3f83c2b10474e9307b83f
|
|
BLAKE2b-256 checksum How to use checksums |
1c5fe6f622ad237286649aaee077f4356632d0bd6ce2e69459420f0e95395970
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
poetry/1.6.1 CPython/3.11.5 Linux/6.2.0-1012-azure
|
Security for sec-ai 0.7.0.post17
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.