🤖 AI Analysis

Final verdict: SUSPICIOUS

The package has low risks in terms of network, shell, obfuscation, and credential activities. However, its metadata suggests potential low activity and lack of maintainer information, which raises some suspicion.

Low activity and lack of maintainer information
Potential lack of community support or maintenance

Per-check LLM notes

Network: No network calls suggest normal behavior for a watermarking tool.
Shell: No shell executions indicate the package does not attempt to execute system commands.
Obfuscation: No obfuscation patterns detected, indicating low risk.
Credentials: No credential harvesting patterns detected, indicating low risk.
Metadata: The package shows signs of potential low activity and lack of maintainer information, raising suspicion.

🔬 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: meok.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 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 agent-content-watermark-mcp

Develop a fully-functional mini-app that utilizes the 'agent-content-watermark-mcp' Python package to apply watermarks to digital content as per the EU AI Act Article 50(2) guidelines. Your application should allow users to upload various types of media files (images, videos, etc.) and choose from different watermarking options including visible, invisible, and perceptual watermarks. Additionally, the app should generate a C2PA manifest envelope for each watermarked file, ensuring compliance with the upcoming 2 November 2026 deadline set by the Code of Practice. Here are the steps to follow:

1. Set up a basic user interface where users can select the type of media file they wish to watermark.
2. Implement functionality to allow users to choose between visible, invisible, and perceptual watermarking methods.
3. Integrate the 'agent-content-watermark-mcp' package to handle the watermarking process based on user selections.
4. Ensure that the application generates a C2PA manifest for each watermarked file, detailing the type of watermark applied, timestamp, and other relevant metadata.
5. Provide an option for users to preview the watermarked content before finalizing the process.
6. Include a feature to download the watermarked files along with their respective C2PA manifests.
7. Ensure that the application is user-friendly, with clear instructions and error messages where necessary.
8. Test the application thoroughly with different types of media files to ensure compatibility and effectiveness of the watermarking process.