AI Analysis
Final verdict: SUSPICIOUS
The package interacts with an external authentication service, raising concerns about potential unauthorized access or data exfiltration. However, it lacks other malicious indicators such as obfuscation, shell execution, or credential harvesting.
- Network risk due to interaction with an external authentication service
- Low activity of the maintainer's account
Per-check LLM notes
- Network: The network call suggests interaction with an authentication service, which could be legitimate but requires further investigation to confirm its purpose and destination.
- Shell: No shell execution patterns were detected.
- Obfuscation: No obfuscation patterns detected, indicating low risk.
- Credentials: No credential harvesting patterns detected, indicating low risk.
- Metadata: The maintainer has only one package, which could indicate a new or less active account, but there are no clear red flags.
Package Quality Overall: Low (2.0/10)
○ Low
Test Suite
1.0
No test suite detected
No test files or test-runner configuration detected
◈ Medium
Documentation
5.0
Some documentation present
Detailed PyPI description (2255 chars)
○ Low
Contributing Guide
2.0
No contributing guide or governance files found
No CONTRIBUTING, CODE_OF_CONDUCT, or governance files found
○ Low
Type Annotations
1.0
No type annotations detected
No type annotations, py.typed marker, or stub files detected
○ Low
Multiple Contributors
1.0
Unable to verify contributor count: no GitHub repository found
No GitHub repository linked — contributor count unavailable
Heuristic Checks
Outbound Network Calls
score 1.5
Found 1 network call pattern(s)
ccess_token}" resp = requests.get( context.get_api(self.ctx) + "/v1/tokens/introsp
Code Obfuscation
No obfuscation patterns detected
Shell / Subprocess Execution
No shell execution patterns detected
Credential Harvesting
No credential harvesting patterns detected
Typosquatting
No typosquatting candidates detected
Registered Email Domain
Email domain looks legitimate: agilicus.com
Suspicious Page Links
All external links appear legitimate
Git Repository History
No GitHub repository linked
No GitHub repository link found
Maintainer History
score 2.0
1 maintainer concern(s) found
Author "Agilicus Devs" 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 agilicus
Create a fully-functional mini-application using the Agilicus SDK, which is designed to streamline Agile project management processes. Your application will serve as a simple Agile board tool for managing tasks across different stages of development (To Do, In Progress, Done). Here’s a detailed breakdown of what your application should achieve and how it leverages the Agilicus SDK: 1. **Project Setup**: Start by setting up a new Python environment and installing the Agilicus SDK via pip. Ensure you have a basic understanding of the SDK’s documentation. 2. **Application Structure**: Design your application with clear separation of concerns. Use classes for different components like Task, Board, and User. Each class should encapsulate functionalities related to their responsibilities. 3. **Task Management**: Implement features to create, read, update, and delete tasks (CRUD operations). Tasks should include fields such as title, description, assigned user, and current status (e.g., To Do, In Progress, Done). 4. **Agile Board Functionality**: Utilize the Agilicus SDK to manage tasks across different stages of an Agile board. The board should allow tasks to be moved from one stage to another with appropriate validation checks. 5. **User Interface**: Although not a requirement, consider implementing a simple command-line interface (CLI) for users to interact with the application. This CLI should allow users to perform CRUD operations on tasks and move tasks between stages of the Agile board. 6. **Data Persistence**: Explore Agilicus SDK features for data persistence. Ensure that task data is saved and retrieved correctly when the application is restarted. 7. **Testing**: Write unit tests for critical functions to ensure reliability. Pay special attention to edge cases and error handling. 8. **Documentation**: Provide clear documentation on how to set up and use the application, including any necessary setup steps and usage examples. By the end of this project, you should have a robust, user-friendly mini-application that effectively demonstrates the capabilities of the Agilicus SDK in managing Agile projects.