sast-secureai
sast-secureai is a Python package that automates software security analysis and testing (SAST) by leveraging AI-powered language models. It allows users to input code snippets or textual descriptions of software functionality and returns a structured report highlighting potential security vulnerabilities, threats, or risks.
Installation
You can install the package using pip:
pip install sast_secureai
Usage
Here's an example of how to use the package in Python:
from sast_secureai import sast_secureai
user_input = "Your code snippet or description here..."
response = sast_secureai(user_input)
print(response)
Function Parameters
user_input(str): The code snippet or description of functionality to analyze.llm(Optional[BaseChatModel]): An optional LangChain language model instance. If not provided, the defaultChatLLM7will be used.api_key(Optional[str]): An optional API key for LLM7. If not provided, the package attempts to retrieve it from the environment variableLLM7_API_KEY.
Custom LLM Support
You can pass your own language model instance to suit your preferred LLM provider by importing and initializing it accordingly. Supported examples include:
from langchain_openai import ChatOpenAI
from sast_secureai import sast_secureai
llm = ChatOpenAI()
response = sast_secureai(user_input, llm=llm)
or
from langchain_anthropic import ChatAnthropic
from sast_secureai import sast_secureai
llm = ChatAnthropic()
response = sast_secureai(user_input, llm=llm)
or
from langchain_google_genai import ChatGoogleGenerativeAI
from sast_secureai import sast_secureai
llm = ChatGoogleGenerativeAI()
response = sast_secureai(user_input, llm=llm)
The default LLM used is ChatLLM7 from langchain_llm7, which can be configured with an API key. Obtain your free API key at https://token.llm7.io/.
Rate Limits
The included default rate limits for LLM7's free tier are sufficient for most use cases. For higher rate limits, set your API key via the environment variable LLM7_API_KEY or pass it directly:
response = sast_secureai(user_input, api_key="your_api_key")
Support and Issues
For issues or feature requests, please use the GitHub issues page:
https://github.com/chigwell/sast-secureai/issues
Author
Eugene Evstafev
Email: hi@eugene.plus
GitHub: chigwell
Metadata
Release files for sast-secureai 2025.12.21084550
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 |
|---|---|---|---|---|
| sast_secureai-2025.12.21084550.tar.gz | 5.9 kB | Without provenance | Details for sast_secureai-2025.12.21084550.tar.gz |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Actions Reset |
|---|---|---|---|---|
| sast_secureai-2025.12.21084550-py3-none-any.whl | Python 3 | none | any | Details for sast_secureai-2025.12.21084550-py3-none-any.whl |
Total release size: 12.3 kB
Release files / sast_secureai-2025.12.21084550.tar.gz
| Download URL | sast_secureai-2025.12.21084550.tar.gz |
|---|---|
| Size | 5.9 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
ec6ba0e000955e026b2772277803068190b0e8b0aa324d3597f41a8b2a60ddba
|
|
BLAKE2b-256 checksum How to use checksums |
83edd6bf2c7c0a1ae1ecc5023195f438ac6318664902132c35687b64331d2ef6
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/6.2.0 CPython/3.11.11
|
Release files / sast_secureai-2025.12.21084550-py3-none-any.whl
| Download URL | sast_secureai-2025.12.21084550-py3-none-any.whl |
|---|---|
| Size | 6.5 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
dc3f1df1dc0741a24a43a807fe9e8b5302452eadee3cc5b4f9c838975fe5d71e
|
|
BLAKE2b-256 checksum How to use checksums |
968cc26560c40a596f0ee36d8399585ec263c353a656c30992f56d898801db1f
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/6.2.0 CPython/3.11.11
|
Security for sast-secureai 2025.12.21084550
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.