AI Analysis
Final verdict: SAFE
The package appears to be safe for use with a low risk score. While there is some uncertainty regarding the maintainer's identity and activity level, the absence of any direct malicious indicators suggests that this package is not a supply-chain attack.
- No network calls detected.
- Subprocess calls seem benign.
- No obfuscation or credential risks identified.
Per-check LLM notes
- Network: No network calls detected, indicating minimal risk of data exfiltration or command and control communication.
- Shell: Subprocess calls appear to be related to the functionality of the lint tool, suggesting it's likely part of its intended operation rather than malicious activity.
- Obfuscation: No obfuscation patterns detected, indicating low risk of malicious intent.
- Credentials: No credential harvesting patterns detected, indicating low risk of secret theft.
- Metadata: The package shows some red flags due to the maintainer's lack of information and activity, but there are no clear signs of typosquatting or other malicious intent.
Heuristic Checks
Outbound Network Calls
No suspicious network call patterns found
Code Obfuscation
No obfuscation patterns detected
Shell / Subprocess Execution
score 8.0
Found 4 shell execution pattern(s)
ml", _CLEAN_XML) result = subprocess.run( [sys.executable, "-m", "acumatica_lint", "--json",KEN_XML_COMMENT) result = subprocess.run( [sys.executable, "-m", "acumatica_lint", "--json",ARNING_ONLY_XML) result = subprocess.run( [sys.executable, "-m", "acumatica_lint", "--json",ml", _CLEAN_XML) result = subprocess.run( # Intentionally omit --no-semantic so run_semantic_
Credential Harvesting
No credential harvesting patterns detected
Typosquatting
No typosquatting candidates detected
Registered Email Domain
Email domain looks legitimate: studiob.ai>
Suspicious Page Links
All external links appear legitimate
Git Repository History
score 2.5
Git history flags: Repository has zero stars and zero forks
Repository has zero stars and zero forks
Maintainer History
score 4.0
2 maintainer concern(s) found
Author name is missing or very shortAuthor "" appears to have only 1 package on PyPI (new or inactive account)
Known CVE Vulnerabilities
No known vulnerabilities found in OSV database.
AI App Starter Prompt
Use this prompt to build a project with acumatica-lint
Create a Python-based utility called 'AcuLintChecker' that leverages the 'acumatica-lint' package to analyze and report on the quality of Acumatica customization code. This utility should serve as a comprehensive tool for developers working on Acumatica projects, providing real-time feedback on potential issues within their customizations. Here are the steps and features you need to implement: 1. **Setup Environment**: Ensure the project is set up using Python 3.8 or higher. Install necessary dependencies including 'acumatica-lint'. 2. **Project Structure**: Design a clean and organized project structure that includes a main module for running the utility, a configuration file for setting up linting rules, and a directory for storing custom extensions if needed. 3. **Integration with 'acumatica-lint'**: Integrate 'acumatica-lint' into your project to scan through specified Acumatica customization files and directories. Use the package's API to apply predefined linting rules and configurations. 4. **Customization Support**: Allow users to customize linting rules and configurations via a simple configuration file. Users should be able to define their own rules, modify existing ones, and specify directories for scanning. 5. **Reporting Mechanism**: Implement a reporting mechanism that summarizes the results of the linting process. This should include a list of all detected issues, categorized by severity, along with suggestions for fixes. 6. **Interactive Mode**: Develop an interactive mode where users can input paths to files or directories directly from the command line interface, receive immediate linting results, and make adjustments based on feedback. 7. **Batch Processing**: Enable batch processing for large-scale projects, allowing users to scan multiple directories and files simultaneously and generate comprehensive reports. 8. **Documentation and Help**: Provide thorough documentation explaining how to use the utility, configure linting rules, and interpret the output. Include examples and best practices. 9. **Testing and Validation**: Write tests to validate that the utility correctly identifies and categorizes different types of issues according to the linting rules. Test both default configurations and user-defined settings. 10. **User Interface**: Optionally, create a basic GUI using a Python library like Tkinter or PyQt, to provide a more user-friendly way to interact with the utility. By completing these steps, 'AcuLintChecker' will become a valuable tool for any developer working with Acumatica customizations, ensuring high-quality code and adherence to best practices.