asterisk-cdr-api

v1.0.5 suspicious
6.0
Medium Risk

REST API для CDR Asterisk — список звонков, фильтры, скачивание записей

🤖 AI Analysis

Final verdict: SUSPICIOUS

The package shows signs of potential tampering due to its rapid commit history and a new maintainer account, raising concerns about its authenticity.

  • Unusual rapid commit history
  • New maintainer account
Per-check LLM notes
  • Network: No network calls detected, which is normal if the package does not require external communications.
  • Shell: No shell execution patterns detected, indicating the package likely does not execute system commands.
  • Obfuscation: No obfuscation patterns detected, indicating low risk.
  • Credentials: No credential harvesting patterns detected, indicating low risk.
  • Metadata: The package shows unusual activity with rapid commit history, a new maintainer account, and non-secure links which raise suspicion.

📦 Package Quality Overall: Low (3.8/10)

○ Low Test Suite 1.0

No test suite detected

  • No test files or test-runner configuration detected
◈ Medium Documentation 7.0

Some documentation present

  • Documentation URL: "Documentation" -> https://github.com/it-healer/asterisk-cdr-api#readme
  • Detailed PyPI description (7482 chars)
○ Low Contributing Guide 4.0

No contributing guide or governance files found

  • Development Status classifier >= Beta
◈ Medium Type Annotations 5.0

Partial type annotation coverage

  • 10 type-annotated function signatures detected in source
○ Low Multiple Contributors 2.0

Single-author or unverifiable project

  • 1 unique contributor(s) across 10 commits in it-healer/asterisk-cdr-api
  • Single author with few commits — possibly a personal or throwaway project

🔬 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: it-healer.com>

⚠ Suspicious Page Links score 10.0

Found 6 suspicious link(s) on the package page

  • Non-HTTPS external link: http://SERVER:8000/docs
  • Non-HTTPS external link: http://SERVER:8000/calls?disposition=ANSWERED&date_from=2026-05-01
  • Non-HTTPS external link: http://SERVER:8000/calls?src=613610&has_recording=true
  • Non-HTTPS external link: http://SERVER:8000/calls/42/download
  • Non-HTTPS external link: http://SERVER:8000/stats?date_from=2026-05-13
  • Non-HTTPS external link: http://SERVER:8000/config
⚠ Git Repository History score 5.0

Git history flags: Repository has zero stars and zero forks

  • Repository has zero stars and zero forks
  • All 10 commits happened within 24 hours
⚠ 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 asterisk-cdr-api 
Create a web-based dashboard application using Python Flask framework that integrates with the 'asterisk-cdr-api' package to manage and analyze call detail records (CDRs) from an Asterisk server. The application should provide users with the ability to view, filter, and export CDR data. Additionally, implement real-time monitoring of active calls and generate reports based on user-defined criteria. Here’s a step-by-step guide to building this application:

1. **Setup Environment**: Begin by setting up your development environment. Install Python, Flask, and the 'asterisk-cdr-api' package. Ensure you have access to an Asterisk server that you can connect to.

2. **Design Database Schema**: Design a simple database schema to store metadata about the calls if needed. This could include fields like call start time, duration, caller ID, and call status.

3. **Integrate 'asterisk-cdr-api'**: Use 'asterisk-cdr-api' to fetch call detail records from the Asterisk server. Implement functions to retrieve all calls, filter calls based on specific parameters such as date range, caller ID, etc., and download call recordings if available.

4. **Develop Web Interface**: Using Flask, develop a clean and intuitive web interface. Include pages for viewing call logs, filtering calls, downloading call recordings, and monitoring active calls in real-time.

5. **Implement Real-Time Monitoring**: Extend the application to support real-time updates on active calls. This could involve setting up websockets or long-polling mechanisms to push updates to the client.

6. **Generate Reports**: Allow users to generate custom reports based on their preferences. These reports could summarize call statistics over a certain period, highlight high-value calls, or identify trends.

7. **Security Considerations**: Ensure that sensitive data is handled securely. Implement authentication and authorization mechanisms to restrict access to the application and its data.

8. **Testing and Deployment**: Thoroughly test the application for functionality and performance. Deploy the application on a suitable hosting platform.

Suggested Features:
- User-friendly interface for easy navigation.
- Advanced filtering options for call logs.
- Ability to download call recordings directly from the web interface.
- Real-time notifications for new incoming calls.
- Customizable report generation with downloadable formats (PDF, CSV).
- Detailed analytics dashboard for call metrics.

💬 Discussion Feed

Leave a comment

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