modwire 1.0.0__tar.gz → 1.1.1__tar.gz

modwire-1.1.1/.github/ISSUE_TEMPLATE/bug_report.yml

@@ -0,0 +1,106 @@
+name: Bug report
+description: Report incorrect extraction, graph output, architecture analysis, packaging, or runtime behavior.
+title: "Bug: "
+labels:
+  - bug
+body:
+  - type: markdown
+    attributes:
+      value: |
+        Thanks for reporting a bug. Clear reproduction details make it much easier to fix issues in extractors and graph analysis.
+
+  - type: textarea
+    id: summary
+    attributes:
+      label: What happened?
+      description: Describe the bug and the behavior you expected instead.
+      placeholder: Modwire returned...
+    validations:
+      required: true
+
+  - type: dropdown
+    id: area
+    attributes:
+      label: Affected area
+      options:
+        - Python extractor
+        - TypeScript/JavaScript extractor
+        - PHP extractor
+        - Dependency graph
+        - Architecture policy API
+        - Packaging or installation
+        - Documentation
+        - Other
+    validations:
+      required: true
+
+  - type: textarea
+    id: reproduce
+    attributes:
+      label: How can we reproduce it?
+      description: Include the smallest source tree, snippet, command, or test case that shows the problem.
+      placeholder: |
+        1. Create this file...
+        2. Run this code...
+        3. Observe...
+    validations:
+      required: true
+
+  - type: textarea
+    id: actual
+    attributes:
+      label: Actual output
+      description: Paste the returned objects, graph edges, violation output, traceback, or command output.
+      render: text
+    validations:
+      required: false
+
+  - type: textarea
+    id: expected
+    attributes:
+      label: Expected output
+      description: Describe the graph, source IDs, symbols, imports, or violations you expected.
+    validations:
+      required: false
+
+  - type: input
+    id: modwire-version
+    attributes:
+      label: Modwire version
+      description: Run `python -m pip show modwire` or identify the commit SHA if installed from source.
+      placeholder: 0.0.0 or commit SHA
+    validations:
+      required: false
+
+  - type: input
+    id: python-version
+    attributes:
+      label: Python version
+      placeholder: "3.11, 3.12, or 3.13"
+    validations:
+      required: true
+
+  - type: input
+    id: runtime-versions
+    attributes:
+      label: Node.js or PHP version, if relevant
+      description: TypeScript/JavaScript extraction requires Node.js. PHP extraction requires PHP.
+      placeholder: "Node.js 20.x, PHP 8.3, or not applicable"
+    validations:
+      required: false
+
+  - type: input
+    id: os
+    attributes:
+      label: Operating system
+      placeholder: "macOS 15, Ubuntu 24.04, Windows 11, etc."
+    validations:
+      required: false
+
+  - type: textarea
+    id: context
+    attributes:
+      label: Additional context
+      description: Add anything else that may help explain the problem.
+    validations:
+      required: false

modwire-1.1.1/.github/ISSUE_TEMPLATE/config.yml

@@ -0,0 +1 @@
+blank_issues_enabled: false

modwire-1.1.1/.github/ISSUE_TEMPLATE/feature_request.yml

@@ -0,0 +1,70 @@
+name: Feature request
+description: Suggest a new capability, supported language, extractor improvement, graph API, or architecture rule.
+title: "Feature: "
+labels:
+  - enhancement
+body:
+  - type: markdown
+    attributes:
+      value: |
+        Use this form for new capabilities or behavior changes. For incorrect current behavior, please open a bug report instead.
+
+  - type: textarea
+    id: problem
+    attributes:
+      label: What problem should this solve?
+      description: Describe the workflow, codebase shape, or analysis gap that motivates the request.
+      placeholder: I want to use Modwire to...
+    validations:
+      required: true
+
+  - type: dropdown
+    id: area
+    attributes:
+      label: Feature area
+      options:
+        - New language support
+        - Python extractor
+        - TypeScript/JavaScript extractor
+        - PHP extractor
+        - Dependency graph
+        - Architecture policy API
+        - Exports or integrations
+        - Documentation
+        - Other
+    validations:
+      required: true
+
+  - type: textarea
+    id: proposal
+    attributes:
+      label: Proposed behavior
+      description: Explain the API, CLI, output shape, analyzer, or documentation you would like to see.
+      placeholder: Modwire should...
+    validations:
+      required: true
+
+  - type: textarea
+    id: example
+    attributes:
+      label: Example usage or input
+      description: Include a short source snippet, desired graph shape, policy example, or Python API sketch if useful.
+      render: python
+    validations:
+      required: false
+
+  - type: textarea
+    id: alternatives
+    attributes:
+      label: Alternatives considered
+      description: Mention any workaround or different API shape you have considered.
+    validations:
+      required: false
+
+  - type: checkboxes
+    id: contribution
+    attributes:
+      label: Contribution
+      options:
+        - label: I would be interested in working on this.
+          required: false

modwire-1.1.1/.github/PULL_REQUEST_TEMPLATE.md

@@ -0,0 +1,14 @@
+## Summary
+
+- 
+
+## Validation
+
+- [ ] `uv run ruff check`
+- [ ] `uv run pytest`
+- [ ] `uv run python -m build --outdir dist`
+- [ ] `uv run twine check dist/*`
+
+## Notes
+
+- 

{modwire-1.0.0 → modwire-1.1.1}/.github/workflows/ci.yml

@@ -5,6 +5,7 @@ on:
     branches:
       - main
   pull_request:
+  workflow_dispatch:
 
 jobs:
   test:

modwire-1.1.1/CONTRIBUTING.md

@@ -0,0 +1,48 @@
+# Contributing to Modwire
+
+Modwire is a Python package for extracting source-code dependencies and
+evaluating architecture rules across Python, TypeScript/JavaScript, and PHP
+projects.
+
+## Requesting Features
+
+Use the `Feature request` issue form for new capabilities, such as:
+
+- support for another language or framework convention
+- richer symbol, import, or graph metadata
+- new architecture analyzers or policy matching behavior
+- export formats or integrations with other tools
+- documentation examples for common workflows
+
+Feature requests are easiest to evaluate when they include the problem being
+solved, a small example input, and the desired API or output shape.
+
+## Reporting Bugs
+
+Use the `Bug report` issue form for incorrect current behavior, such as:
+
+- missing or incorrect imports, symbols, source IDs, or graph edges
+- incorrect architecture-policy violations
+- extractor crashes or runtime failures
+- packaging, installation, or compatibility problems
+- documentation that contradicts the implemented behavior
+
+Bug reports should include a minimal reproduction, the expected output, the
+actual output, and relevant versions for Python, Modwire, Node.js, or PHP.
+
+## Pull Requests
+
+Before opening a pull request, run the local checks:
+
+```bash
+uv run ruff check
+uv run pytest
+uv run python -m build --outdir dist
+uv run twine check dist/*
+```
+
+Extractor changes should include focused tests under `tests/` and, when
+relevant, a small fixture under `tests/apps/`.
+
+Keep pull requests scoped to one behavior change. If an issue exists, link it in
+the pull request description.

{modwire-1.0.0 → modwire-1.1.1}/PKG-INFO

@@ -1,12 +1,12 @@
 Metadata-Version: 2.4
 Name: modwire
-Version: 1.0.0
+Version: 1.1.1
 Summary: Extract source-code dependencies and build dependency graphs.
 Author: Tomasz Szpak
 License-Expression: MIT
-Project-URL: Homepage, https://github.com/9orky/codemap
-Project-URL: Repository, https://github.com/9orky/codemap
-Project-URL: Issues, https://github.com/9orky/codemap/issues
+Project-URL: Homepage, https://github.com/9orky/modwire
+Project-URL: Repository, https://github.com/9orky/modwire
+Project-URL: Issues, https://github.com/9orky/modwire/issues
 Keywords: architecture,code-analysis,dependency-graph,static-analysis
 Classifier: Development Status :: 3 - Alpha
 Classifier: Intended Audience :: Developers
@@ -70,6 +70,7 @@ TypeScript, and PHP projects can be compared through the same graph shape.
 
 ## Supported Languages
 
+
 ```python
 from modwire import supported_languages
 
@@ -109,3 +110,18 @@ uv run pytest
 uv run python -m build --outdir dist
 uv run twine check dist/*
 ```
+
+## Contributing
+
+Feature requests and bug reports are tracked through GitHub Issues:
+
+- Open a feature request for new language support, graph metadata, architecture
+  rules, export formats, or documentation examples.
+- Open a bug report for incorrect extraction results, graph edges, architecture
+  violations, packaging problems, or runtime failures.
+
+See [CONTRIBUTING.md](CONTRIBUTING.md) for the information to include and the
+checks to run before opening a pull request.
+
+Starter wiki pages are tracked under [docs/wiki](docs/wiki) so the GitHub Wiki
+can be initialized with the same guidance.

{modwire-1.0.0 → modwire-1.1.1}/README.md

@@ -37,6 +37,7 @@ TypeScript, and PHP projects can be compared through the same graph shape.
 
 ## Supported Languages
 
+
 ```python
 from modwire import supported_languages
 
@@ -76,3 +77,18 @@ uv run pytest
 uv run python -m build --outdir dist
 uv run twine check dist/*
 ```
+
+## Contributing
+
+Feature requests and bug reports are tracked through GitHub Issues:
+
+- Open a feature request for new language support, graph metadata, architecture
+  rules, export formats, or documentation examples.
+- Open a bug report for incorrect extraction results, graph edges, architecture
+  violations, packaging problems, or runtime failures.
+
+See [CONTRIBUTING.md](CONTRIBUTING.md) for the information to include and the
+checks to run before opening a pull request.
+
+Starter wiki pages are tracked under [docs/wiki](docs/wiki) so the GitHub Wiki
+can be initialized with the same guidance.

modwire-1.1.1/docs/wiki/Development-checks.md

@@ -0,0 +1,20 @@
+# Development Checks
+
+Run these checks before opening a pull request:
+
+```bash
+uv run ruff check
+uv run pytest
+uv run python -m build --outdir dist
+uv run twine check dist/*
+```
+
+Extractor changes should include focused tests under `tests/` and, when useful,
+small source fixtures under `tests/apps/`.
+
+The CI workflow currently validates:
+
+- Python 3.11, 3.12, and 3.13
+- Node.js syntax for the TypeScript/JavaScript extractor helper
+- PHP syntax for the PHP extractor helper
+- package build and distribution metadata

modwire-1.1.1/docs/wiki/Home.md

@@ -0,0 +1,28 @@
+# Modwire Wiki
+
+Modwire extracts source-code structure and import dependencies from Python,
+TypeScript/JavaScript, and PHP projects. It returns typed Python objects for
+building dependency graphs, inspecting symbols, and evaluating architecture
+rules.
+
+## Start Here
+
+- [Reporting bugs](Reporting-bugs.md)
+- [Requesting features](Requesting-features.md)
+- [Development checks](Development-checks.md)
+
+## Useful Project Links
+
+- Repository: https://github.com/9orky/modwire
+- Issues: https://github.com/9orky/modwire/issues
+- Bug report form: https://github.com/9orky/modwire/issues/new?template=bug_report.yml
+- Feature request form: https://github.com/9orky/modwire/issues/new?template=feature_request.yml
+
+## Supported Languages
+
+- Python
+- TypeScript and JavaScript
+- PHP
+
+The Python extractor works with Python alone. TypeScript/JavaScript extraction
+requires Node.js at runtime, and PHP extraction requires PHP at runtime.

modwire-1.1.1/docs/wiki/Reporting-bugs.md

@@ -0,0 +1,26 @@
+# Reporting Bugs
+
+Use the GitHub `Bug report` issue form when Modwire behaves incorrectly.
+
+## Good Bug Reports Include
+
+- a short summary of what went wrong
+- the affected area, such as an extractor, dependency graph, or architecture
+  analyzer
+- the smallest source snippet or fixture that reproduces the problem
+- the actual output, traceback, graph edges, or violations
+- the expected output
+- Modwire, Python, Node.js, PHP, and operating-system versions where relevant
+
+## Examples of Bugs
+
+- an import is missed or linked to the wrong source ID
+- a symbol is extracted with incorrect metadata
+- graph edges are missing, duplicated, or pointed at the wrong node
+- an architecture policy reports the wrong violation
+- extraction crashes on valid Python, TypeScript/JavaScript, or PHP source
+- package installation or distribution metadata is broken
+
+Open a bug report at:
+
+https://github.com/9orky/modwire/issues/new?template=bug_report.yml

modwire-1.1.1/docs/wiki/Requesting-features.md

@@ -0,0 +1,26 @@
+# Requesting Features
+
+Use the GitHub `Feature request` issue form for new capabilities or behavior
+changes.
+
+## Good Feature Requests Include
+
+- the problem or workflow the feature would support
+- the affected area, such as language support, graph APIs, exports, or
+  architecture policies
+- a small source-code example when possible
+- the desired API, output shape, analyzer behavior, or documentation example
+- alternatives or workarounds you have considered
+
+## Examples of Feature Requests
+
+- add support for another language or framework convention
+- expose richer graph, import, or symbol metadata
+- add a new architecture analyzer
+- improve policy matching for layered architectures
+- export graphs in another format
+- add documentation for a common integration workflow
+
+Open a feature request at:
+
+https://github.com/9orky/modwire/issues/new?template=feature_request.yml

{modwire-1.0.0 → modwire-1.1.1}/pyproject.toml

@@ -37,9 +37,9 @@ dependencies = [
 ]
 
 [project.urls]
-Homepage = "https://github.com/9orky/codemap"
-Repository = "https://github.com/9orky/codemap"
-Issues = "https://github.com/9orky/codemap/issues"
+Homepage = "https://github.com/9orky/modwire"
+Repository = "https://github.com/9orky/modwire"
+Issues = "https://github.com/9orky/modwire/issues"
 
 [project.optional-dependencies]
 dev = [

{modwire-1.0.0 → modwire-1.1.1}/src/modwire/__init__.py

@@ -1,5 +1,6 @@
 from .extraction import CodeMap, extract_code
 from .extractors.loader import normalize_source_id, supported_languages
+from .exports import UnusedExport, find_unused_exports
 from .graph import DependencyGraph, Edge, Node, build_dependency_graph
 
 
@@ -8,8 +9,10 @@ __all__ = [
     "DependencyGraph",
     "Edge",
     "Node",
+    "UnusedExport",
     "build_dependency_graph",
     "extract_code",
+    "find_unused_exports",
     "normalize_source_id",
     "supported_languages",
 ]

{modwire-1.0.0 → modwire-1.1.1}/src/modwire/_version.py

@@ -18,7 +18,7 @@ version_tuple: tuple[int | str, ...]
 commit_id: str | None
 __commit_id__: str | None
 
-__version__ = version = '1.0.0'
-__version_tuple__ = version_tuple = (1, 0, 0)
+__version__ = version = '1.1.1'
+__version_tuple__ = version_tuple = (1, 1, 1)
 
-__commit_id__ = commit_id = 'gb2874aa61'
+__commit_id__ = commit_id = 'gbfbd18f94'

{modwire-1.0.0 → modwire-1.1.1}/src/modwire/definitions.py

@@ -6,6 +6,25 @@ from pydantic import BaseModel, Field
 ImportCrossingType = Literal["module", "symbol"]
 SourceVisibility = Literal["public", "protected", "private"]
 SourceSignatureKind = Literal["call", "construct", "index"]
+SourceExportKind = Literal[
+    "module",
+    "class",
+    "interface",
+    "type",
+    "abstract_class",
+    "function",
+    "value",
+    "unknown",
+]
+
+
+class SourceImportedSymbol(BaseModel):
+    name: str
+    alias: str
+    is_aliased: bool
+    is_default: bool
+    is_namespace: bool
+    is_star: bool
 
 
 class SourceImport(BaseModel):
@@ -19,6 +38,21 @@ class SourceImport(BaseModel):
     statement_id: int
     join_key: str
     uses_joined_import: bool
+    imported_symbols: list[SourceImportedSymbol] = Field(default_factory=list)
+
+
+class SourceExport(BaseModel):
+    name: str
+    local_name: str
+    kind: SourceExportKind
+    crossing_type: ImportCrossingType
+    path: str
+    is_relative: bool
+    normalized_path: str
+    is_reexport: bool
+    is_default: bool
+    is_aliased: bool
+    statement_id: int
 
 
 class SourceFunction(BaseModel):
@@ -91,6 +125,7 @@ class SourceAbstractClass(BaseModel):
 
 class SourceFile(BaseModel):
     imports: list[SourceImport]
+    exports: list[SourceExport] = Field(default_factory=list)
     classes: list[SourceClass]
     interfaces: list[SourceInterface] = Field(default_factory=list)
     types: list[SourceType] = Field(default_factory=list)