Repowise · Codebase intelligence
ibuilder / massing
Open, self-hosted, IFC-native AEC platform: web BIM viewer + modeling, a ~100-module GC portal (RFIs, pay apps, CPM, construction accounting — double-entry GL/WIP → QuickBooks, e-sign), AI assist, IDS authoring, estimating + embodied carbon, a development proforma, and operate/dispose (CMMS, facility condition, rent roll, waterfall).
Does the health score find the bugs?
Repowise ranks every file by predicted defect risk. Of the 20 files it flags as riskiest, 15 (75%) actually needed a bug fix in the last 6 months — 6.2× better than picking files at random.
Languages
- python66.1%
- json15.0%
- typescript10.9%
- markdown4.7%
- yaml1.2%
- javascript0.9%
- dockerfile
Key modules2
- typescript
web
apps/web
- javascript
converter
services/converter
Code health
Full reportHow ibuilder/massing works
Open, self-hosted, IFC-native AEC platform: web BIM viewer + modeling, a ~100-module GC portal (RFIs, pay apps, CPM, construction accounting — double-entry GL/WIP → QuickBooks, e-sign), AI assist, IDS authoring, estimating + embodied carbon, a development proforma, and operate/dispose (CMMS, facility condition, rent roll, waterfall). This page is an auto-generated, always-fresh map of the ibuilder/massing repository, written primarily in Python. Repowise indexes the source, parses every symbol, computes a dependency graph, scores per-file code health from complexity, duplication, test coverage and churn, mines git history for hotspots and ownership, and lifts the resulting architectural decisions into a wiki you can read or query through MCP.
The codebase has 881 source files, 6,587 symbols, and 10 languages, structured as a monorepo with 2 packages. Git churn analysis flags 118 high-frequency files as hotspots — places where bugs, rewrites, and code review tend to concentrate. The dependency graph clusters into 236 tightly-coupled module communities.
Use the panels above to open the interactive dashboards, or connect this repo to your editor via the Repowise MCP server for grounded answers inside Claude, Cursor, or VS Code.