AI Analysis
Final verdict: SAFE
The package has been assessed with minimal risks across all categories. It does not engage in any network calls, shell executions, or credential manipulations, and shows no signs of obfuscation.
- No network risk
- No shell risk
- No obfuscation risk
- No credential risk
Per-check LLM notes
- Network: No network calls detected, which is normal for most packages not requiring external services.
- Shell: No shell execution patterns detected, indicating no direct system command execution.
- Obfuscation: No obfuscation patterns detected, indicating low risk.
- Credentials: No credential harvesting patterns detected, indicating low risk.
- Metadata: Low risk with minor concerns regarding non-secure links and a single-package author.
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: lists.sourceforge.net
Suspicious Page Links
score 6.0
Found 3 suspicious link(s) on the package page
Non-HTTPS external link: http://plone.org/products/plone/roadmap/52Non-HTTPS external link: http://dev.plone.org/plone/ticket/9864Non-HTTPS external link: http://dev.plone.org/plone/ticket/8101
Git Repository History
Repository plone/Products.CMFPlacefulWorkflow appears legitimate
Maintainer History
score 2.0
1 maintainer concern(s) found
Author "Encolpe DEGOUTE" 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 Products.CMFPlacefulWorkflow
Your task is to develop a mini-application using the Plone CMS framework that integrates the 'Products.CMFPlacefulWorkflow' package to manage content workflow policies effectively. This application will serve as a demonstration of how to apply customizable workflows to different parts of a website, ensuring that content goes through appropriate stages before being published or modified. The application should include the following core functionalities: 1. **Content Creation**: Users should be able to create new pieces of content such as articles, blog posts, or any other type of document. 2. **Workflow Assignment**: Different sections of the site should have different workflows assigned to them. For example, a 'News' section might require a review process before publishing, while a 'Blogs' section might allow direct publication by registered users. 3. **Workflow States Management**: The application should support at least three states per workflow: Draft, Review, and Published. Additional states can be added based on your creativity. 4. **User Roles Integration**: Integrate user roles such that only specific roles can transition content between states (e.g., editors can move content from Draft to Review, but only managers can publish). 5. **Audit Trail**: Implement an audit trail feature that logs all changes made to content and its state transitions. 6. **Custom Workflow Policies**: Allow administrators to define custom workflow policies for different parts of the site, including assigning specific workflows to specific folders or paths. To achieve these functionalities, you will need to utilize the 'Products.CMFPlacefulWorkflow' package to set up place-specific workflows. This involves configuring workflows, assigning them to different sections of the site, and managing transitions based on user roles and permissions. Additionally, consider how you can extend the package's capabilities to meet the requirements of your application, possibly by adding custom scripts or modifying existing ones to fit your needs. This project aims not only to demonstrate the use of 'Products.CMFPlacefulWorkflow' but also to explore advanced customization options within the Plone CMS environment.