ninja-devx 0.0.1__tar.gz

ninja_devx-0.0.1/.dockerignore

@@ -0,0 +1,16 @@
+.git
+.venv
+.agents
+.codex
+**/__pycache__
+**/.pytest_cache
+**/.mypy_cache
+**/.ruff_cache
+**/.hypothesis
+**/node_modules
+**/*.sqlite3
+site
+dist
+artifacts
+.env
+.env.*

ninja_devx-0.0.1/.gitignore

@@ -0,0 +1,90 @@
+# Python bytecode and caches
+__pycache__/
+*.py[cod]
+*$py.class
+.pytest_cache/
+.hypothesis/
+.mypy_cache/
+.dmypy.json
+.pyright/
+.ruff_cache/
+.tox/
+.nox/
+.coverage
+.coverage.*
+coverage.xml
+htmlcov/
+
+# Virtual environments and local Python tooling
+.venv/
+venv/
+env/
+ENV/
+*.egg-info/
+.pdm-build/
+.python-version.local
+.direnv/
+.envrc
+
+# Build and distribution outputs
+/build/
+/dist/
+/wheelhouse/
+*.whl
+*.tar.gz
+*.zip
+
+# Documentation and generated reports
+/site/
+/artifacts/
+/reports/
+/release-evidence/
+benchmarks/results*.json
+*.log
+*.out
+*.pid
+
+# Local databases and application uploads
+*.sqlite3
+*.sqlite3-journal
+*.sqlite3-shm
+*.sqlite3-wal
+/media/
+/uploads/
+/tmp/
+
+# Environment files and local secrets
+.env
+.env.*
+!.env.example
+*.pem
+*.key
+*.p12
+*.secret
+
+# JavaScript tooling and logs
+node_modules/
+npm-debug.log*
+yarn-debug.log*
+yarn-error.log*
+pnpm-debug.log*
+.npm/
+.cache/
+
+# Docker local overrides and runtime state
+docker-compose.override.yml
+compose.override.yaml
+.docker-volumes/
+
+# Editors and operating-system files
+.idea/
+.vscode/*
+!.vscode/extensions.json
+!.vscode/settings.example.json
+*.swp
+*.swo
+*.orig
+*.rej
+*~
+.DS_Store
+Thumbs.db

ninja_devx-0.0.1/CHANGELOG.md

@@ -0,0 +1,195 @@
+# Changelog
+
+All notable changes to this project are documented here. ninja-devx follows
+[semantic versioning](https://semver.org); see the support and stability page for what
+that means before 1.0.
+
+## 0.0.1
+
+First alpha release candidate. The section below is the reviewed release content;
+publication occurs only when the matching tag passes the release workflow.
+
+### Compatibility and operational requirements
+
+- Python 3.11+, Django 4.2+ and django-ninja 1.7.x (`<2`); supported interpreter/framework
+  combinations are listed in the support policy.
+- Core migrations are required for durable idempotency and upload lifecycle records.
+  Contrib apps have their own migrations and optional dependencies.
+- Owner/tenant/parent scope and persisted object permissions apply to built-in writes.
+  Audit history is paginated and staff-protected by default.
+- Idempotency requires independent durable claims; webhook delivery is at-least-once;
+  upload checksum/version enforcement is configurable.
+- Generated clients support JSON, simple multipart and declared text/binary responses.
+  Cookie parameters, SSE and complex encodings fail generation explicitly.
+- Internal modules were reorganized before release. See the
+  [migration notes](https://ctolon.github.io/ninja-devx/migration/review-integration/).
+
+### Foundations
+
+- Class-based controllers compiled into native `ninja.Router`s: `@get/@post/...` with
+  typed options, request and singleton scopes, lifecycle methods, static-first routing,
+  `mount()` with versioned prefixes.
+- Composable permissions (`&`, `|`, `~`, `Also`), object-level and async checks,
+  `DjangoModelPermissions`, `IsOwner`, typed users (`AuthedRequest[User]`,
+  `current_user`).
+- Generic CRUD (`CRUDController[Model, Out, In]` and mixins): `owner_field`,
+  `Instance[Model]`, generated filters and ordering, nested `Parent`, soft delete, bulk
+  operations, `Patch[In]`, `idempotent()`, `atomic=True`.
+- A small typed DI container plus dishka and svcs adapters.
+- Operation hooks, `LoggingHook`, OpenTelemetry.
+- pytest plugin with OpenAPI snapshots, `devx_scaffold` and `devx_openapi` (typed
+  TypeScript and Python clients).
+- mypy strict and pyright strict, with no `typing.Any` in the package.
+
+### APIs and integrations
+
+**Errors and layers**
+
+- `ErrorMap`: typed exception → response rules on operations, controllers, settings
+  (`NINJA_DEVX["ERRORS"]`) and APIs (`install(api)`, using Ninja's exception handlers).
+- Django `ValidationError`, `ObjectDoesNotExist` and `PermissionDenied` map to 422, 404
+  and 403 by default.
+- `raises=` documents errors in OpenAPI and is checked against the rules.
+- `ERROR_FORMAT = "problem+json"` (RFC 9457).
+- `ninja_devx.layers`, HTTP-free: `DomainError` (`NotFound`, `Conflict`,
+  `PermissionDenied`, `ValidationFailed`), `Repository`/`AsyncRepository` protocols,
+  `ModelRepository`, `ModelService`, `dual` (one method for sync and `.a` async callers),
+  `RequestContext`, `TaskQueue` (`OnCommitTaskQueue`, `ImmediateTaskQueue`,
+  `RecordingTaskQueue`), `after_commit`, `Policy`/`require`, `Selector`.
+- `layers.testing`: `InMemoryRepository`, `make_context`.
+- CRUD `service_class` and `selector_class`, resolved from the container.
+- `use_case(decorator, Handler, command=...)` operations.
+- Architecture recipes (HackSoft, Cosmic-lite, dishka interactors) with shared contract
+  tests.
+
+**Dependency injection**
+
+- Operation-level injection: `Inject[T]` and `Annotated[T, Resolve(fn)]`, validated at
+  startup.
+- Container: async and async-generator factories, `aresolve`, `container.scope(values)`
+  for tasks and commands, `close`/`aclose`, captive dependency checks, and
+  `check(key, asynchronous=...)`.
+- `request_context(User, tenant=...)` / `arequest_context`, `aauthenticated_user`,
+  `acurrent_user`, `arequest_user`.
+- dishka: `DishkaResolver(container, async_container=...)` for both modes,
+  `provide_controllers`, startup validation.
+
+**Async and sync**
+
+- `mode = "sync" | "async" | "auto"` (`NINJA_DEVX["ASYNC_MODE"]`) and `async_variant` for
+  reusable bases. The CRUD mixins implement both modes from one class.
+- `run_sync`/`run_atomic`: one thread hop per unit of work. Async CRUD writes take a
+  single hop.
+- `AsyncOperationHook` (`around_async`), blocking sync hooks (`blocking = True`), async
+  lifecycle methods, async permission checks everywhere.
+- Hooks and DI scopes wrap whole streams; permissions are checked before the first item
+  of async streams.
+- Teaching errors: `AsyncLazyAccessError`, `BlockingCallWarning` (`WARN_BLOCKING_MS`),
+  `MixedPathWarning`, `ASYNC_FETCH_MODE = "raise"` (Django 6.1 `FETCH_RAISE`), and the
+  pytest `AsyncDatabaseTestWarning`.
+- `python -m ninja_devx.tooling.unasync` generates sync twins of async code (`--check` for CI).
+
+**Permissions and operations**
+
+- `Also(...)` adds operation permissions to the controller's.
+- `IsReadOnly`, `as_permission(policy, User)`.
+- `owner_field` follows relations (`"project__owner"`).
+- `Locked[Model]` (`select_for_update`).
+- Typed operation metadata: `meta=(...)` and `operation.meta(Kind)`.
+- `atomic="durable"` and `database=`.
+- `ControllerPlugin` protocol (`on_operation`, `bindings`, `checks`), via options or
+  `NINJA_DEVX["PLUGINS"]`.
+
+**Quality and tooling**
+
+- Django system checks (`ninja_devx.E001`–`E004`, `W003`), `Controller.checks()`,
+  `NINJA_DEVX["CHECK_APIS"]`.
+- `manage.py devx_scaffold --check` reports model/schema drift.
+- Query optimizer v2: `Prefetch` querysets join foreign keys inside prefetched relations;
+  `optimize_queries = "only"`; `query_plan()`.
+- Testing: `assert_max_hops`, `capture_commits` / `captured_commits` fixture.
+- Benchmarks v2: interleaved in-process overhead with thread-hop counts and an optional
+  budget check (`benchmarks/budget.json`), plus WSGI/ASGI load tests with p50/p99
+  (`benchmarks/load.py`).
+- Docs: errors, layers, async and sync, system checks, recipes, support policy; every
+  code block in the docs is compiled by the test suite.
+
+### SaaS, HTTP and schemas
+
+- Multi-tenancy: `tenant_field`, tenant resolvers (sync or async, settings, `RequestContext`,
+  `request.tenant`), `Parent(..., tenant_field=...)`, `current_tenant(request)`.
+- Conditional requests: `etag = ETag()` (304 on reads, `If-Match` → 412/428 on writes),
+  `conditional()` for any GET.
+- `CursorPagination` following the request's ordering; `pagination_options`.
+- Throttles: `UserRateThrottle`, `AnonRateThrottle`, `ClientRateThrottle`,
+  `ScopedRateThrottle` (`THROTTLE_RATES`), `TenantRateThrottle`; thread-safe and atomic.
+- Role-based field visibility: `VisibleTo(...)` and the `FieldVisibility` mixin.
+- Contract tests: `ninja_contract` fixture on schemathesis (`[contract]` extra).
+- Nothing hard-coded: `routes` (rename, reconfigure or disable operations), `lookup_param`,
+  `ordering_param`, `SoftDelete(field, deleted=, active=, deleted_at=, deleted_by=)`.
+- Invalid lookup values reach Ninja and return JSON 422 (path converters are opt-in with
+  `lookup_converter`).
+- Schema generation: `devx_scaffold` writes model constraints (`max_length`, `min_length`,
+  patterns, ranges, decimals, `help_text`); `devx_openapi --format python` generates
+  validated pydantic models (default) or TypedDicts; drift checks flag `max_length`
+  mismatches; system check `W005`.
+
+### Security and optional integrations
+
+- Object permissions: `ObjectPermissions()` on any model controller (DRF
+  `DjangoObjectPermissions` semantics: 404 without `view`, 403 without the method's
+  permission, lists filtered in SQL), backends for the new `ninja_devx.contrib.grants`
+  app, django-guardian (`[guardian]`) and `user.has_perm`; `assign_perm`, `remove_perm`,
+  `get_perms`, `get_objects_for_user`, `grants_for`; `ObjectSharingMixin` endpoints;
+  `OBJECT_PERMISSION_BACKEND` setting.
+- Response shaping: `sparse_fields` (`?fields=`) and `Expandable()` relations
+  (`?expand=`), with the query planner joining only what is expanded.
+- `AutoCRUDController[Model]` and `AutoReadOnlyController[Model]`: schemas generated with
+  Ninja's `create_schema` (`schema_fields`, `read_only_fields`, `write_only_fields`).
+- `LimitOffsetPagination`: links that keep query parameters, `count=False`, `max_offset`,
+  stable ordering.
+- `ExportMixin` / `ImportMixin`: streamed CSV and JSON Lines export honoring filters and
+  visibility; all-or-nothing imports with row-level 422 errors and `dry_run`.
+- Middleware for APIs, routers, mounts and controllers (`use_middleware`,
+  `ControllerOptions(middleware=...)`) on Ninja's `add_decorator`: `RequestIDMiddleware`,
+  `ServerTimingMiddleware`, `DeprecationMiddleware` (RFC 9745 / RFC 8594),
+  `RateLimitHeadersMiddleware` (added automatically with ninja-devx throttles).
+- `HealthController` (`/live`, `/ready`) with database, cache and migration checks.
+- `ORJSONRenderer` and `MsgspecRenderer`; `OpenTelemetryMetricsMiddleware`.
+- `contrib.apikeys`: hashed, scoped, expiring API keys (`APIKeyAuth`, `APIKeyBearer`,
+  `HasScopes`, `RequiresScope`), a self-service controller and `devx_apikey`.
+- `contrib.audit`: `AuditMixin` records creates, updates (field diffs) and deletes in the
+  same transaction, with redaction and request ids; `record()`, `AuditLogController`,
+  `AuditHistoryMixin`.
+- `contrib.webhooks`: transactional outbox (`publish`), Standard Webhooks signatures,
+  retries with backoff, endpoint disabling, `SKIP LOCKED` workers (`devx_webhooks
+  deliver`), `WebhookEndpointController`, `verify_signature` for receivers.
+- `contrib.uploads`: presigned direct uploads (`S3Signer` with `[s3]`, `FakeSigner`),
+  upload policies and ownership checks.
+- Webhooks hardening: SSRF protection (`URLPolicy`, `check_url`, `SafeHTTPTransport` checks
+  the connected address, so DNS rebinding is covered too), optional encryption of signing
+  secrets (`WEBHOOK_SECRET_KEYS`, `[crypto]`, `devx_webhooks generate-key` /
+  `encrypt-secrets`), and delivery right after commit through task queues
+  (`publish(queue=...)`, `deliver_event`, `django.tasks` task).
+- API keys: per-key `rate_limit` and `APIKeyRateThrottle`.
+- `sparse_fields` operations document `<Out>Partial` responses (no required properties), so
+  validating generated clients accept `?fields=` responses.
+- Django admin for `ObjectGrant`, `APIKey` (revoke action), `AuditEntry` (read-only) and
+  webhooks (secret shown once, rotate, retry, enable).
+- Translations: client-facing messages use `gettext` (`default_message` on domain errors,
+  `gettext_noop` permission messages), and `tools/messages.py` to extract and compile
+  catalogs without GNU gettext. English defaults ship; add catalogs for other languages.
+- `ObjectSharingMixin.validate_holder()` restricts who objects may be shared with.
+- `devx_startapp`: Django's `startapp` with a ninja-devx template.
+- "Did you mean" suggestions for misspelled fields, routes and settings.
+- Project: `SECURITY.md`, `CONTRIBUTING.md`, versioned documentation with mike, a
+  PostgreSQL test job and SQLite/PostgreSQL load tests in CI.
+
+### Known limitations
+
+- A permission denial on an async streaming operation closes the stream empty (with a
+  logged warning) instead of returning 403: Ninja starts the response before the stream
+  runs.
+- `Container.instance` and `Container.override` validate values at registration rather
+  than in type checkers, because mypy cannot infer the type from abstract or protocol
+  keys.

ninja_devx-0.0.1/CODE_OF_CONDUCT.md

@@ -0,0 +1,49 @@
+# Code of Conduct
+
+This policy applies to issues, pull requests, discussions, reviews and other project
+spaces, and to conduct when representing ninja-devx publicly.
+
+## Expected conduct
+
+Treat people with respect. Discuss code, evidence and tradeoffs without attacking the
+person proposing them. Make criticism specific enough to act on. Respect differing
+experience, backgrounds and communication styles. Accept that maintainers may decline a
+proposal because of scope, maintenance cost or compatibility.
+
+## Unacceptable conduct
+
+Harassment, threats, discriminatory language, sexualized attention, deliberate humiliation,
+impersonation, sustained disruption and publication of another person's private information
+without consent are not permitted. Repeated unwanted contact and retaliation against a
+reporter are also violations. Technical disagreement does not excuse these behaviors.
+
+## Private reporting
+
+Send conduct reports to **[cevatbatuhan.tolon@gmail.com](mailto:cevatbatuhan.tolon@gmail.com)**.
+Include links or dates, a factual description and any immediate safety concern. Do not put
+personal details in a public issue. Share only information needed to assess the incident.
+
+Reports are handled by the project maintainer. Information is shared only as needed to
+investigate and respond; absolute confidentiality cannot be guaranteed where platform
+moderation or immediate safety requires disclosure. There is no guaranteed response-time
+service. For urgent threats, use the platform's abuse reporting or appropriate local
+emergency services.
+
+If the complaint concerns the maintainer, use
+[GitHub's reporting process](https://docs.github.com/en/site-policy/content-removal-policies/github-community-guidelines#reporting-abuse)
+for conduct on GitHub. This project currently has no independent conduct committee.
+
+Report software vulnerabilities through [SECURITY.md](https://github.com/ctolon/ninja-devx/blob/main/SECURITY.md), not through public
+conduct discussions.
+
+## Enforcement
+
+Maintainers may remove or edit content, limit a discussion, issue a warning, temporarily
+restrict participation or permanently exclude a participant. The response depends on
+severity, impact, repetition and immediate risk. A serious threat or disclosure of private
+information may warrant immediate exclusion without a prior warning.
+
+Where doing so does not expose the reporter or create further harm, the affected person
+will receive the reason and duration of an action. They may send relevant additional facts
+to the same private address. Retaliation or attempts to evade a restriction may lead to
+further action. Maintainers are subject to this policy as participants.

ninja_devx-0.0.1/CONTRIBUTING.md

@@ -0,0 +1,77 @@
+# Contributing
+
+Changes should solve a concrete application or maintenance problem. For a substantial API
+change, describe the use case, proposed interface, alternatives and compatibility cost in
+an issue before building it. Security reports belong in [SECURITY.md](https://github.com/ctolon/ninja-devx/blob/main/SECURITY.md); project
+participation follows the [Code of Conduct](https://github.com/ctolon/ninja-devx/blob/main/CODE_OF_CONDUCT.md).
+
+## Development
+
+Use Python 3.11 or later and [uv](https://docs.astral.sh/uv/). The default validation
+interpreter is Python 3.13; supported combinations are listed in the support documentation.
+
+```bash
+uv sync --locked --group docs --group verification
+uv run --no-sync pytest -q
+uv run --no-sync ruff check .
+uv run --no-sync ruff format --check .
+uv run --no-sync mypy
+uv run --no-sync pyright --pythonpath .venv/bin/python
+uv run --no-sync python tools/messages.py --check
+uv run --no-sync python tools/generate_docs.py --check
+uv run --no-sync mkdocs build --strict
+uv run --no-sync python tools/check_docs_links.py site
+```
+
+Run backend-dependent changes in the disposable Docker stack described in the
+[release runbook](https://ctolon.github.io/ninja-devx/project/releasing/). Local SQLite tests
+do not establish PostgreSQL lock behavior, Redis counter atomicity or S3 upload semantics.
+
+Each example is a separate Django project. Run it from its directory, for example:
+
+```bash
+cd examples/blog
+uv run --no-sync --project ../.. pytest -q
+uv run --no-sync --project ../.. mypy blog config clients/blog_client.py
+uv run --no-sync --project ../.. python manage.py makemigrations --check --dry-run
+```
+
+## Design and review
+
+- Keep HTTP adaptation separate from a business rule that has non-HTTP callers. A service
+  or repository interface is useful when it owns a real boundary, not merely another name
+  for every ORM call.
+- Preserve request, object and queryset authorization boundaries. Custom hooks must state
+  their transaction and database ownership. Test rejection paths and side effects.
+- Keep request state out of shared controller/permission objects. Resource dependencies
+  need success, failure and cancellation cleanup tests.
+- Public APIs must pass strict mypy/Pyright checks. Avoid widening a public type to hide a
+  mismatch. Implementation modules are not automatically public extension points.
+- Add a regression test for a bug. Prefer tests of observable behavior over copies of the
+  implementation. Concurrency changes need deterministic coordination and deadlines.
+- Update guides/examples, changelog and migration notes when behavior changes. Explain the
+  trigger, resulting behavior, limitations and operational requirements in plain language.
+  Avoid unsupported performance claims or feature rankings.
+- Wrap user-facing messages in Django gettext and refresh the matching catalogs with
+  `tools/messages.py`. Regenerate option references with `tools/generate_docs.py`.
+
+## Dependencies and generated files
+
+Edit dependency constraints intentionally and regenerate `uv.lock`; do not submit a stale
+lock. CI uses `--locked`. Docker base digests and action commit pins require reviewed updates;
+Dependabot proposals are input to that review, not automatic authorization to merge.
+
+Do not edit generated option tables, sync twins or API clients manually. Run their documented
+generator and review the diff. A generated artifact can still expose an incorrect public
+contract; successful generation is not sufficient review.
+
+## Pull requests
+
+Describe the concrete problem and final behavior for a reviewer who has not followed the
+issue. Include relevant validation and material limits. Keep unrelated refactors separate.
+Contributions are licensed under Apache-2.0; do not include material you cannot license
+under the repository's terms.
+
+Maintainers use the [release runbook](https://ctolon.github.io/ninja-devx/project/releasing/)
+for tag validation, test gates, Trusted Publishing, recovery and repository settings.
+Do not publish a tag or distribution as part of an ordinary contribution.

ninja_devx-0.0.1/LICENSE

@@ -0,0 +1,202 @@
+
+                                 Apache License
+                           Version 2.0, January 2004
+                        http://www.apache.org/licenses/
+
+   TERMS AND CONDITIONS FOR USE, REPRODUCTION, AND DISTRIBUTION
+
+   1. Definitions.
+
+      "License" shall mean the terms and conditions for use, reproduction,
+      and distribution as defined by Sections 1 through 9 of this document.
+
+      "Licensor" shall mean the copyright owner or entity authorized by
+      the copyright owner that is granting the License.
+
+      "Legal Entity" shall mean the union of the acting entity and all
+      other entities that control, are controlled by, or are under common
+      control with that entity. For the purposes of this definition,
+      "control" means (i) the power, direct or indirect, to cause the
+      direction or management of such entity, whether by contract or
+      otherwise, or (ii) ownership of fifty percent (50%) or more of the
+      outstanding shares, or (iii) beneficial ownership of such entity.
+
+      "You" (or "Your") shall mean an individual or Legal Entity
+      exercising permissions granted by this License.
+
+      "Source" form shall mean the preferred form for making modifications,
+      including but not limited to software source code, documentation
+      source, and configuration files.
+
+      "Object" form shall mean any form resulting from mechanical
+      transformation or translation of a Source form, including but
+      not limited to compiled object code, generated documentation,
+      and conversions to other media types.
+
+      "Work" shall mean the work of authorship, whether in Source or
+      Object form, made available under the License, as indicated by a
+      copyright notice that is included in or attached to the work
+      (an example is provided in the Appendix below).
+
+      "Derivative Works" shall mean any work, whether in Source or Object
+      form, that is based on (or derived from) the Work and for which the
+      editorial revisions, annotations, elaborations, or other modifications
+      represent, as a whole, an original work of authorship. For the purposes
+      of this License, Derivative Works shall not include works that remain
+      separable from, or merely link (or bind by name) to the interfaces of,
+      the Work and Derivative Works thereof.
+
+      "Contribution" shall mean any work of authorship, including
+      the original version of the Work and any modifications or additions
+      to that Work or Derivative Works thereof, that is intentionally
+      submitted to Licensor for inclusion in the Work by the copyright owner
+      or by an individual or Legal Entity authorized to submit on behalf of
+      the copyright owner. For the purposes of this definition, "submitted"
+      means any form of electronic, verbal, or written communication sent
+      to the Licensor or its representatives, including but not limited to
+      communication on electronic mailing lists, source code control systems,
+      and issue tracking systems that are managed by, or on behalf of, the
+      Licensor for the purpose of discussing and improving the Work, but
+      excluding communication that is conspicuously marked or otherwise
+      designated in writing by the copyright owner as "Not a Contribution."
+
+      "Contributor" shall mean Licensor and any individual or Legal Entity
+      on behalf of whom a Contribution has been received by Licensor and
+      subsequently incorporated within the Work.
+
+   2. Grant of Copyright License. Subject to the terms and conditions of
+      this License, each Contributor hereby grants to You a perpetual,
+      worldwide, non-exclusive, no-charge, royalty-free, irrevocable
+      copyright license to reproduce, prepare Derivative Works of,
+      publicly display, publicly perform, sublicense, and distribute the
+      Work and such Derivative Works in Source or Object form.
+
+   3. Grant of Patent License. Subject to the terms and conditions of
+      this License, each Contributor hereby grants to You a perpetual,
+      worldwide, non-exclusive, no-charge, royalty-free, irrevocable
+      (except as stated in this section) patent license to make, have made,
+      use, offer to sell, sell, import, and otherwise transfer the Work,
+      where such license applies only to those patent claims licensable
+      by such Contributor that are necessarily infringed by their
+      Contribution(s) alone or by combination of their Contribution(s)
+      with the Work to which such Contribution(s) was submitted. If You
+      institute patent litigation against any entity (including a
+      cross-claim or counterclaim in a lawsuit) alleging that the Work
+      or a Contribution incorporated within the Work constitutes direct
+      or contributory patent infringement, then any patent licenses
+      granted to You under this License for that Work shall terminate
+      as of the date such litigation is filed.
+
+   4. Redistribution. You may reproduce and distribute copies of the
+      Work or Derivative Works thereof in any medium, with or without
+      modifications, and in Source or Object form, provided that You
+      meet the following conditions:
+
+      (a) You must give any other recipients of the Work or
+          Derivative Works a copy of this License; and
+
+      (b) You must cause any modified files to carry prominent notices
+          stating that You changed the files; and
+
+      (c) You must retain, in the Source form of any Derivative Works
+          that You distribute, all copyright, patent, trademark, and
+          attribution notices from the Source form of the Work,
+          excluding those notices that do not pertain to any part of
+          the Derivative Works; and
+
+      (d) If the Work includes a "NOTICE" text file as part of its
+          distribution, then any Derivative Works that You distribute must
+          include a readable copy of the attribution notices contained
+          within such NOTICE file, excluding those notices that do not
+          pertain to any part of the Derivative Works, in at least one
+          of the following places: within a NOTICE text file distributed
+          as part of the Derivative Works; within the Source form or
+          documentation, if provided along with the Derivative Works; or,
+          within a display generated by the Derivative Works, if and
+          wherever such third-party notices normally appear. The contents
+          of the NOTICE file are for informational purposes only and
+          do not modify the License. You may add Your own attribution
+          notices within Derivative Works that You distribute, alongside
+          or as an addendum to the NOTICE text from the Work, provided
+          that such additional attribution notices cannot be construed
+          as modifying the License.
+
+      You may add Your own copyright statement to Your modifications and
+      may provide additional or different license terms and conditions
+      for use, reproduction, or distribution of Your modifications, or
+      for any such Derivative Works as a whole, provided Your use,
+      reproduction, and distribution of the Work otherwise complies with
+      the conditions stated in this License.
+
+   5. Submission of Contributions. Unless You explicitly state otherwise,
+      any Contribution intentionally submitted for inclusion in the Work
+      by You to the Licensor shall be under the terms and conditions of
+      this License, without any additional terms or conditions.
+      Notwithstanding the above, nothing herein shall supersede or modify
+      the terms of any separate license agreement you may have executed
+      with Licensor regarding such Contributions.
+
+   6. Trademarks. This License does not grant permission to use the trade
+      names, trademarks, service marks, or product names of the Licensor,
+      except as required for reasonable and customary use in describing the
+      origin of the Work and reproducing the content of the NOTICE file.
+
+   7. Disclaimer of Warranty. Unless required by applicable law or
+      agreed to in writing, Licensor provides the Work (and each
+      Contributor provides its Contributions) on an "AS IS" BASIS,
+      WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or
+      implied, including, without limitation, any warranties or conditions
+      of TITLE, NON-INFRINGEMENT, MERCHANTABILITY, or FITNESS FOR A
+      PARTICULAR PURPOSE. You are solely responsible for determining the
+      appropriateness of using or redistributing the Work and assume any
+      risks associated with Your exercise of permissions under this License.
+
+   8. Limitation of Liability. In no event and under no legal theory,
+      whether in tort (including negligence), contract, or otherwise,
+      unless required by applicable law (such as deliberate and grossly
+      negligent acts) or agreed to in writing, shall any Contributor be
+      liable to You for damages, including any direct, indirect, special,
+      incidental, or consequential damages of any character arising as a
+      result of this License or out of the use or inability to use the
+      Work (including but not limited to damages for loss of goodwill,
+      work stoppage, computer failure or malfunction, or any and all
+      other commercial damages or losses), even if such Contributor
+      has been advised of the possibility of such damages.
+
+   9. Accepting Warranty or Additional Liability. While redistributing
+      the Work or Derivative Works thereof, You may choose to offer,
+      and charge a fee for, acceptance of support, warranty, indemnity,
+      or other liability obligations and/or rights consistent with this
+      License. However, in accepting such obligations, You may act only
+      on Your own behalf and on Your sole responsibility, not on behalf
+      of any other Contributor, and only if You agree to indemnify,
+      defend, and hold each Contributor harmless for any liability
+      incurred by, or claims asserted against, such Contributor by reason
+      of your accepting any such warranty or additional liability.
+
+   END OF TERMS AND CONDITIONS
+
+   APPENDIX: How to apply the Apache License to your work.
+
+      To apply the Apache License to your work, attach the following
+      boilerplate notice, with the fields enclosed by brackets "[]"
+      replaced with your own identifying information. (Don't include
+      the brackets!)  The text should be enclosed in the appropriate
+      comment syntax for the file format. We also recommend that a
+      file or class name and description of purpose be included on the
+      same "printed page" as the copyright notice for easier
+      identification within third-party archives.
+
+   Copyright [yyyy] [name of copyright owner]
+
+   Licensed under the Apache License, Version 2.0 (the "License");
+   you may not use this file except in compliance with the License.
+   You may obtain a copy of the License at
+
+       http://www.apache.org/licenses/LICENSE-2.0
+
+   Unless required by applicable law or agreed to in writing, software
+   distributed under the License is distributed on an "AS IS" BASIS,
+   WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
+   See the License for the specific language governing permissions and
+   limitations under the License.

ninja_devx-0.0.1/NOTICE

@@ -0,0 +1,4 @@
+ninja-devx
+Copyright 2026 The ninja-devx contributors
+
+This product is licensed under the Apache License, Version 2.0 (see LICENSE).