airflow-provider-cian

v0.1.3 safe
2.0
Low Risk

Apache Airflow provider for Cian.ru Builder API — collect calls and chats statistics

🤖 AI Analysis

Final verdict: SAFE

The package appears to be a legitimate provider for interfacing with the Cian.ru Builder API. It has a low network risk score and no evidence of shell risk.

  • Low network risk
  • No shell risk detected
Per-check LLM notes
  • Network: Making GET requests is common for packages that interact with APIs or fetch external data.
  • Shell: No shell execution patterns detected.

📦 Package Quality Overall: Medium (5.4/10)

✦ High Test Suite 9.0

Test suite present — 4 test file(s) found

  • Test runner config found: pyproject.toml
  • 4 test file(s) detected (e.g. test_cian.py)
◈ Medium Documentation 7.0

Some documentation present

  • Documentation URL: "Documentation" -> https://github.com/mkozhin/airflow-provider-cian#readme
  • Detailed PyPI description (3826 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

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

Single-author or unverifiable project

  • 1 unique contributor(s) across 15 commits in mkozhin/airflow-provider-cian
  • Single author with few commits — possibly a personal or throwaway project

🔬 Heuristic Checks

⚠ Outbound Network Calls score 1.5

Found 1 network call pattern(s)

  • try: resp = requests.get(url, params=params, headers=headers, timeout=30)
✓ 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: kozhin.cc>

✓ Suspicious Page Links

All external links appear legitimate

⚠ Git Repository History score 5.0

Git history flags: Repository created very recently: 3 day(s) ago (2026-06-03T11:16:41Z)

  • Repository created very recently: 3 day(s) ago (2026-06-03T11:16:41Z)
  • Repository has zero stars and zero forks
⚠ Maintainer History score 6.0

3 maintainer concern(s) found

  • Package is very new: uploaded 2 day(s) ago
  • 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 airflow-provider-cian 
Create a real estate data analysis tool using the 'airflow-provider-cian' package, which interfaces with the Cian.ru Builder API to gather call and chat statistics. This tool will allow users to schedule periodic data collection tasks, process the collected data, and generate insightful reports about the performance of real estate listings on Cian.ru.

Steps to develop the project:
1. Set up a local development environment with Docker containers for Apache Airflow and PostgreSQL.
2. Install the 'airflow-provider-cian' package within your Airflow environment.
3. Create a DAG (Directed Acyclic Graph) in Airflow to schedule data collection from the Cian.ru Builder API at regular intervals (e.g., daily).
4. Develop a data processing pipeline that cleans and aggregates the collected call and chat statistics.
5. Implement functionality to store processed data into a database (PostgreSQL).
6. Design a simple web interface using Flask or Django to display the aggregated statistics and enable users to generate custom reports.
7. Integrate the web interface with Airflow to trigger data collection and processing tasks manually or automatically based on user preferences.

Suggested Features:
- Real-time monitoring of data collection status through Airflow UI.
- Customizable report generation based on user-defined criteria.
- Data visualization tools to display trends over time.
- Email notifications for significant changes in call/chat statistics.
- User authentication and role-based access control for different levels of data access.

💬 Discussion Feed

Leave a comment

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