Dashboard / Repos / Reqord

Reqord

C+ 77 completed
Cli Tool
monorepo / typescript · medium
690
Files
70,443
LOC
2
Frameworks
7
Languages
OverviewFiles & MetricsGit ActivityCall GraphSecurityReports

Pipeline State

completed
Run ID
#30731
Phase
done
Progress
0%
Started
2026-03-06 10:38:43
Finished
2026-03-06 10:38:43
LLM tokens
0

Pipeline Metadata

Stage
Cataloged
Decision
proceed
Novelty
70.00
Framework unique
—
Isolation
—
Last stage change
2026-05-10 03:34:29
Deduplication group #54534
Member of a group with 5 similar repo(s) — this repo is canonical view group →
Top concepts (1)
Full Stack
Repobility analyzer · published findings · https://repobility.com

🧪 Code Distillation

Browse all specs →
Function bodies →
330
Real LLM specs →
324
98.2% coverage
All specs →
324
LLM insights →
0
Sample distilled functions (click for full spec)
main
Executes a migration process that checks for and updates YAML files within a local .reqord directory. It accepts no explicit arguments but reads command-line flags to determine if it should run in a dry-run mode. The function outputs status messages detailing the files found and how many were proces
findYamlFiles
Collects all file paths ending with .yaml located within the "requirements" and "specifications" subdirectories of a given input directory. It returns an array of these absolute file paths, sorted alphabetically. This function reads the contents of the specified directories and has no observable sid
processYamlFileWithRegex
Reads the content of a specified file path, modifies version strings found in two specific patterns within the YAML content, and returns a boolean indicating success. It accepts a file path string and a dry run boolean flag as inputs. The function's primary side-effect is logging messages to the con

AI Prompt

Create a tool called Reqord that allows teams to store project requirements as structured data directly within a Git repository. I need it to manage a 3-layer traceability model connecting the "Requirement" (what to build), the "Specification" (how to build it), and "GitHub Issue" tasks. The system should enforce a lifecycle for requirements, moving them through states like draft, pending\_approval, approved, implemented, and deprecated. The core functionality should involve storing this structured data using YAML and Markdown files alongside the code, ensuring version control for the entire requirements history.
typescript next.js monorepo git requirements documentation structured-data yaml markdown version-control
Generated by gemma4:latest

Catalog Information

Reqord is a tool that stores requirements as structured data in your Git repository, allowing for version-controlled tracking of project requirements and their implementation.

Description

Reqord solves the problem of scattered requirements by making them structured, versioned, and traceable. It enforces a 3-layer traceability model that connects intent to implementation: Requirements (What), Specifications (How), and GitHub Issues (Tasks). This allows for clear lifecycle management of requirements from draft to implementation.

الوصف

يحل Reqord مشكلة متفرقة المتطلبات عن طريق جعلها موصوفة، مرئية، ومتتبعة. يفرض نموذج متابعة ثلاثي الطبقات يربط بين الغرض والتنفيذ: المتطلبات (ماذا)، التوصيات (كيف)، ومشاريع غيت هاب (التasks). هذا يسمح بمراقبة دورة الحياة للمتطلبات من المخطوط إلى التنفيذ.

Novelty

7/10

Tags

requirement-management version-control git structured-data traceability ai-inputs

Technologies

vitest

Claude Models

claude-opus-4.6 claude-sonnet-4.6 claude-haiku-4.5

Quality Score

C+
77.1/100
Structure
77
Code Quality
99
Documentation
53
Testing
85
Practices
57
Security
75
Dependencies
90

Strengths

  • CI/CD pipeline configured (github_actions)
  • Good test coverage (58% test-to-source ratio)
  • Code linting configured (eslint)
  • Properly licensed project

Weaknesses

  • 1 files with critical complexity need refactoring
  • 1169 duplicate lines detected \u2014 consider DRY refactoring

Security & Health

1
Vulnerabilities
0
Critical CVEs
12.8h
Tech Debt (A)
Repobility — same analyzer, your code, free for public repos · /scan/
High
DORA Rating
A
OWASP (100%)
PASS
Quality Gate
A
Risk (0)
AGPL-3.0
License
5.9%
Duplication
Full Security Report AI Fix Prompts SARIF SBOM

Languages

typescript
44.7%
markdown
33.6%
yaml
11.4%
json
10.1%
javascript
0.1%
shell
0.1%
css
0.0%

Frameworks

Next.js Vitest

Symbols

variable1,244
function424
interface112
type_alias77
constant77
method14
class4
enum1
Powered by Repobility — scan your code at https://repobility.com

API Endpoints (24)

Analysis by Repobility (https://repobility.com) · MCP-ready
MethodPathHandlerFramework
Provenance: Repobility (https://repobility.com) — every score reproducible from /scan/
GETblockedByformData.getExpress
GETblocksformData.getExpress
GETdescriptionformData.getExpress
GETearsActionformData.getExpress
GETearsConditionformData.getExpress
GETearsResponseformData.getExpress
GETearsTriggerformData.getExpress
GETearsTypeformData.getExpress
GETestimatedComplexityformData.getExpress
GETestimatedHoursformData.getExpress
GETformatTypeformData.getExpress
GETidformData.getExpress
GETP0taskGroups.getExpress
GETP1taskGroups.getExpress
GETP2taskGroups.getExpress
GETpriorityformData.getExpress
GETrelatedToformData.getExpress
GETreqsearchParams.getExpress
GETstatusformData.getExpress
GETsuccessCriteriaformData.getExpress
GETtitleformData.getExpress
GETuserStoryAsformData.getExpress
GETuserStoryIWantformData.getExpress
GETuserStorySoThatformData.getExpress

Concepts (1)

Repobility · the analyzer behind every row · https://repobility.com
CategoryNameDescriptionConfidence
Repobility · MCP-ready · https://repobility.com
auto_categoryFull Stackfull-stack70%

Threat Findings

1
Total Threats
0
Critical
0
High
View Threat Intel

Quality Timeline

1 quality score recorded.

View File Metrics

Embed Badge

Add to your README:

![Quality](https://repos.aljefra.com/badge/30680.svg)
Quality BadgeSecurity Badge
Export Quality CSVDownload SBOMExport Findings CSV