Eddy

v3.8.1 safe
3.0
Low Risk

Eddy is a graphical editor for the specification and visualization of Graphol ontologies.

⚠ Tarball exceeded 25 MB — source code analysis was limited to package metadata only.

🤖 AI Analysis

Final verdict: SAFE

The package shows low risk indicators across all categories with only metadata presenting a minor concern due to non-secure links and a new maintainer. There is no evidence of malicious activity or supply-chain attack.

  • Low network and shell risk
  • No obfuscation or credential harvesting detected
  • Minor metadata risk due to insecure links and new maintainer
Per-check LLM notes
  • Network: No network calls detected, which is normal unless the package's functionality requires external communications.
  • Shell: No shell execution patterns detected, indicating no immediate signs of malicious activities such as command execution.
  • Obfuscation: No obfuscation patterns detected, indicating low risk of malicious intent.
  • Credentials: No credential harvesting patterns detected, suggesting safe handling of secrets and credentials.
  • Metadata: The package has non-secure links and a new maintainer, but no other suspicious activities are noted.

🔬 Heuristic Checks

✓ Outbound Network Calls

No suspicious network call patterns found

✓ 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: dis.uniroma1.it

⚠ Suspicious Page Links score 10.0

Found 10 suspicious link(s) on the package page

  • Non-HTTPS external link: http://www.dis.uniroma1.it/~lembo/
  • Non-HTTPS external link: http://www.dis.uniroma1.it/~dottoratoii/students/valerio-santarelli
  • Non-HTTPS external link: http://www.dis.uniroma1.it/~savo/
  • Non-HTTPS external link: http://www.dis.uniroma1.it/~dottoratoii/students/marco-console
  • Non-HTTPS external link: http://www.ijcai.org/Proceedings/16/Papers/646.pdf
  • Non-HTTPS external link: http://www.aaai.org/ocs/index.php/KR/KR16/paper/view/12904/12524
✓ Git Repository History

Repository obdasystems/eddy appears legitimate

⚠ Maintainer History score 2.0

1 maintainer concern(s) found

  • Author "Daniele Pantaleone" 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 Eddy 
Your task is to develop a mini-application called 'Ontology Explorer' using the Python package 'Eddy'. This application will allow users to create, edit, and visualize simple ontological structures in a user-friendly manner. The primary goal is to enable users to understand and manipulate basic concepts of ontologies without requiring deep technical knowledge.

**Step 1: Project Setup**
- Install the necessary packages including 'Eddy' and any other dependencies required for your application.
- Set up a virtual environment for your project to ensure clean and isolated development.

**Step 2: User Interface Design**
- Create a simple GUI using a library such as Tkinter or PyQt. The interface should have:
  - A canvas area where users can draw and modify ontology diagrams.
  - Buttons for adding nodes (representing classes or individuals), edges (representing relationships), and labels.
  - Menu options for saving and loading ontology files.
- Ensure the UI is responsive and visually appealing.

**Step 3: Core Functionality Implementation**
- Utilize Eddy's capabilities to allow users to define and edit ontological entities (classes, individuals, etc.).
- Implement functionality to connect these entities via relationships (edges) on the canvas.
- Enable users to add labels and descriptions to each entity and relationship.
- Integrate Eddy's visualization tools to automatically layout the diagram in a readable manner.

**Step 4: Advanced Features**
- Include a feature to validate the ontology against common errors (e.g., circular references).
- Add a query tool that allows users to ask questions about their ontology and get answers based on the defined relationships.
- Provide an option to export the ontology to standard formats like OWL or RDF.

**Step 5: Testing and Documentation**
- Test your application thoroughly to ensure all functionalities work as expected.
- Write comprehensive documentation explaining how to use the application, including screenshots and examples.
- Share your project on GitHub or another code-sharing platform, ensuring it's easy for others to install and run.

💬 Discussion Feed

Leave a comment

No discussion yet. Be the first to share your thoughts!