🤖 AI Analysis

Final verdict: SAFE

The package shows minimal risk indicators with low scores across all categories except metadata, which has a moderate score due to missing author information and insecure links. There are no signs of malicious activities or supply-chain attacks.

Low network, shell, obfuscation, and credential risks
Moderate metadata risk due to incomplete package details

Per-check LLM notes

Network: The network call patterns are typical for packages that interact with web services or APIs, likely for authentication or data retrieval purposes.
Shell: No shell execution patterns detected.
Obfuscation: No obfuscation patterns detected, indicating low risk of malicious obfuscation.
Credentials: No credential harvesting patterns detected, suggesting no risk of secret theft.
Metadata: The package has potential risks due to missing author information and non-secure links, but no clear signs of typosquatting or malicious intent.

🔬 Heuristic Checks

⚠ Outbound Network Calls score 6.0

Found 4 network call pattern(s)

ion = session if session else requests.Session() self.graphql_url = graphql_url self.gatewa
eClient """ session = requests.Session() session.cookies = requests.cookies.cookiejar_from_dict
cation """ session = requests.Session() post_vars = deepcopy(configuration.static_post_vars)
th is None: session = requests.Session() else: session = authenticate_with_external(con

✓ 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

No author email provided

⚠ Suspicious Page Links score 4.0

Found 2 suspicious link(s) on the package page

Non-HTTPS external link: http://myhostname:8080/v1/graphql
Non-HTTPS external link: http://myhostname:9000

✓ Git Repository History

Repository NASA-AMMOS/aerie-cli appears legitimate

⚠ Maintainer History score 4.0

2 maintainer concern(s) found

Author name is missing or very short
Author "" 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 aerie-cli

Your task is to create a command-line tool called 'MissionScheduler' using the Python package 'aerie-cli'. This tool will allow users to manage their space mission schedules by interacting with PlanDev's scheduling capabilities. The goal is to streamline the process of adding, modifying, and querying mission tasks and their associated constraints and resources.

#### Core Features:
1. **Add Mission Task**: Users should be able to add new mission tasks, specifying details such as start time, end time, duration, and resource requirements.
2. **Modify Mission Task**: Allow users to update existing mission tasks, including changing start/end times, duration, or resource allocations.
3. **Query Mission Schedule**: Provide options for users to query the mission schedule based on various criteria, such as date range, specific resources, or task types.
4. **Visualize Schedule**: Implement a feature that visualizes the mission schedule graphically, showing overlapping tasks and resource usage over time.
5. **Export Schedule**: Enable users to export the mission schedule in different formats (e.g., CSV, JSON).

#### Utilizing 'aerie-cli':
- Use 'aerie-cli' to connect to PlanDev's scheduling system and perform operations like adding, updating, and querying tasks.
- Leverage 'aerie-cli' to handle complex scheduling scenarios, ensuring that all tasks adhere to the defined constraints and resource availability.
- Integrate 'aerie-cli' to facilitate real-time interaction with PlanDev's scheduling backend, allowing for dynamic adjustments and optimizations of the mission schedule.

#### Additional Considerations:
- Ensure the application has a user-friendly CLI interface with clear prompts and help messages.
- Implement error handling to gracefully manage incorrect inputs or failed operations.
- Consider adding logging to track user actions and system responses for debugging and auditing purposes.

Your final deliverable should include a well-documented Python script that integrates 'aerie-cli', along with any necessary configuration files and example usage scenarios.