Public scan — anyone with this URL can view this analysis. Sign up to track your own repos privately, run scheduled re-scans, and get AI fix prompts via your dashboard.

Code-Craft-Manage/agile-pulse

https://github.com/Code-Craft-Manage/agile-pulse · scanned 2026-06-17 01:23 UTC (1 month, 2 weeks ago)

16 raw signals (0 security + 16 graph)

File as issue Image

UNIFIED Repobility · multi-layer engine · AI coders

Complete repo analysis

Last scanned 1 month, 2 weeks ago · v2 · last Δ +9.5 (diff) · 15 actionable findings from 1 signal source. 1 repeated signal grouped for readability. Security checks, system graph analysis, and verified AI-agent feedback are merged into one review queue.

JSON

77.8% cov · 15 findings

Severity distribution — click a segment to filter

Active filters: excluding tests × Reset all

Severity: Critical 0 High 0 Medium 5 Low 6 9-Layer: Software Security Quality Integrity Frontend Hardware Data Network Cicd Source: Security checks 0 System graph 15 Crowd 0 Layer: Hardware 2 Security 1 Cicd 2 Quality 10

Exclude dismissed / FP Exclude test files

All 101 nodes from the latest scan, grouped by kind. Each node is a unit the engine identified (file, function, endpoint, table…). Most users won't need this view — it's primarily for debugging the engine's graph extraction or for AI agents that want to enumerate the project structure.

Label	Layer	Status	Path
`cmd_fetch`	software	healthy	`cli.py:26`
`_fetch_team`	software	healthy	`cli.py:44`
`_started_statuses`	software	healthy	`cli.py:86`
`_fetch_kanban_flow`	software	healthy	`cli.py:103`
`cmd_show`	software	healthy	`cli.py:135`
`cmd_history`	software	healthy	`cli.py:156`
`_display_snapshot`	software	healthy	`cli.py:196`
`_display_row`	software	healthy	`cli.py:219`
`_print_metrics`	software	healthy	`cli.py:242`
`main`	software	healthy	`cli.py:285`
`_parse_jira_datetime`	software	healthy	`jira_client.py:15`
`get_configured_teams`	software	healthy	`jira_client.py:29`
`__init__`	software	healthy	`jira_client.py:44`
`_team_env`	software	healthy	`jira_client.py:67`
`get_board_config`	software	healthy	`jira_client.py:81`
`get_active_sprint`	software	dead	`jira_client.py:90`
`get_any_sprints`	software	healthy	`jira_client.py:106`
`get_last_closed_sprint`	software	dead	`jira_client.py:123`
`get_last_n_closed_sprints`	software	healthy	`jira_client.py:143`
`_all_sprints`	software	healthy	`jira_client.py:165`
`_fetch_changelog`	software	healthy	`jira_client.py:181`
`get_status_history`	software	healthy	`jira_client.py:240`
`_initial_estimate_from_changelog`	software	healthy	`jira_client.py:267`
`get_sprint_report`	software	healthy	`jira_client.py:326`
`_sum`	software	healthy	`jira_client.py:358`
`_keys`	software	healthy	`jira_client.py:361`
`_issue_pts`	software	healthy	`jira_client.py:364`
`_issue_current_pts`	software	healthy	`jira_client.py:368`
`_issue_initial_pts`	software	healthy	`jira_client.py:378`
`get_sprint_issues`	software	healthy	`jira_client.py:482`
`get_kanban_issues`	software	healthy	`jira_client.py:494`
`get_done_issues`	software	healthy	`jira_client.py:500`
`_search_issues`	software	healthy	`jira_client.py:526`
`_v3_issue_to_object`	software	healthy	`jira_client.py:558`
`_extract_issue`	software	healthy	`jira_client.py:587`
`_agile_get`	software	healthy	`jira_client.py:605`
`calculate_sprint_metrics`	software	healthy	`calculator.py:12`
`calculate_kanban_metrics`	software	healthy	`calculator.py:72`
`_is_done`	software	healthy	`calculator.py:117`
`_sum_points`	software	healthy	`calculator.py:121`
`_count_type`	software	healthy	`calculator.py:125`
`_normalize_status`	software	healthy	`kanban_flow.py:28`
`first_started_at`	software	healthy	`kanban_flow.py:33`
`_days_between`	software	healthy	`kanban_flow.py:49`
`_iso_week_label`	software	healthy	`kanban_flow.py:58`
`build_flow_rows`	software	healthy	`kanban_flow.py:72`
`weekly_throughput`	software	healthy	`kanban_flow.py:105`
`_percentile`	software	healthy	`kanban_flow.py:123`
`lead_time_stats`	software	healthy	`kanban_flow.py:137`
`cycle_time_stats`	software	healthy	`kanban_flow.py:156`

Showing first 50 of this kind. Full payload available via the JSON button at the top of the page.

Label	Layer	Status	Path
`.env.example`	software	healthy	`.env.example`
`cli.py`	software	healthy	`cli.py`
`requirements.txt`	software	healthy	`requirements.txt`
`README.md`	software	healthy	`README.md`
`jira_client.py`	software	healthy	`jira_client.py`
`calculator.py`	software	healthy	`calculator.py`
`kanban_flow.py`	software	healthy	`kanban_flow.py`
`Dockerfile`	software	healthy	`Dockerfile`
`db.py`	software	healthy	`db.py`
`daily-sync.yml`	software	healthy	`.github/workflows/daily-sync.yml`
`app.py`	software	healthy	`web/app.py`
`index.html`	software	healthy	`web/templates/index.html`

Label	Layer	Status	Path
`JIRA_URL`	cicd	healthy	`—`
`JIRA_EMAIL`	cicd	healthy	`—`
`SSM_PROJECT_KEY`	cicd	healthy	`—`
`SAM_STORY_POINTS_FIELD`	cicd	healthy	`—`
`SSM_BOARD_ID`	cicd	healthy	`—`
`SAM_BOARD_ID`	cicd	healthy	`—`
`SAM_PROJECT_KEY`	cicd	healthy	`—`
`SSM_STORY_POINTS_FIELD`	cicd	healthy	`—`
`TEAMS`	cicd	healthy	`—`
`JIRA_API_TOKEN`	cicd	healthy	`—`

Label	Layer	Status	Path
`.github`	software	healthy	`.github`
`workflows`	software	healthy	`.github/workflows`
`web`	software	healthy	`web`
`templates`	software	healthy	`web/templates`

Label	Layer	Status	Path
`JiraClient`	software	healthy	`jira_client.py:43`
`Database`	software	healthy	`db.py:62`

Label	Layer	Status	Path
`GET /`	api	healthy	`web/app.py`
`GET /api/throughput`	api	healthy	`web/app.py`

Label	Layer	Status	Path
`metrics`	data	healthy	`db.py`
`kanban_issue_flow`	data	healthy	`db.py`

Label	Layer	Status	Path
`Code-Craft-Manage__agile-pulse`	software	healthy	`/data/fable5_failed_archive/Code-Craft-Manage__agile-pulse`

Label	Layer	Status	Path
`sqlite`	data	healthy	`.env.example`

Label	Layer	Status	Path
`image::Dockerfile`	hardware	healthy	`Dockerfile`

Label	Layer	Status	Path
`gha::daily-sync`	cicd	healthy	`.github/workflows/daily-sync.yml`

Label	Layer	Status	Path
`sync`	cicd	healthy	`.github/workflows/daily-sync.yml`

For AI agents: Voting guide (TP/FP) MCP manifest Stdio wrapper SARIF Integrate Findings queue Vote TP/FP on findings to calibrate the engine.

For AI agents + API integrations

Email me when this repo regresses

Free. We re-scan periodically; new criticals → your inbox. No signup required for the scan itself.

API access

This page is publicly accessible at: https://repobility.com/scan/ce176a09-aac7-43f1-b44f-5acca9dd40eb/

To check status programmatically (no auth required):

curl -s https://repobility.com/api/v1/public/scan/ce176a09-aac7-43f1-b44f-5acca9dd40eb/

Important — please don't re-submit the same URL repeatedly. The submission endpoint is idempotent: re-submitting the same git URL returns this same scan_token, not a new one. To re-scan this repo, sign up free and use the dashboard.

Code-Craft-Manage/agile-pulse

Complete repo analysis

function 50+

file 12

env_var 10

directory 4

class 2

endpoint 2

table 2

repo 1

database 1

container 1

pipeline 1

job 1