narvy-cli 1.0.0__tar.gz

narvy_cli-1.0.0/CHANGELOG.md

@@ -0,0 +1,44 @@
+# Changelog
+
+All notable changes to this project are documented in this file.
+
+The format is based on [Keep a Changelog](https://keepachangelog.com/en/1.1.0/),
+and this project adheres to [Semantic Versioning](https://semver.org/spec/v2.0.0.html).
+
+## [0.9.0]
+
+First public release. A free, local security scanner that runs entirely on your
+machine and never uploads source code unless you explicitly ask it to.
+
+### Added
+
+- **Android SAST** - static analysis of APK/AAB binaries and Android source
+  trees (Java/Kotlin), with third-party-code filtering to keep findings focused
+  on first-party code.
+- **iOS SAST** - static analysis of IPA/Mach-O binaries and iOS source trees
+  (Swift/Objective-C), including symbol-table and Obj-C introspection.
+- **Web and backend source SAST** - polyglot scanning of web/backend source
+  directories (JavaScript/TypeScript, Python, PHP, Go, Ruby, Rust, Java,
+  Kotlin) using Narvy-authored rule packs.
+- **Software Composition Analysis (SCA)** - dependency scanning to surface known
+  vulnerable components.
+- **Passive web scanner** (`web-scan`) - Nuclei-based passive vulnerability
+  scan of a URL with SSRF-guarded redirect resolution; no account required.
+- **Host/infra audit** (`host-audit`) - agentless Lynis audit over your own SSH
+  access; no credentials are sent anywhere.
+- **Cloud posture scan** (`cloud-scan`) - cloud configuration checks using your
+  own ambient credentials, with zero credential custody.
+- **Semgrep detection engine** (pinned `semgrep==1.152.0`) driving
+  independently-authored Narvy rule packs for mobile and web/backend
+  source, shipped with the package.
+- **`doctor`** - preflight environment check (Java, jadx, network, iOS tooling)
+  before scanning.
+- **`init-ci`** - drop-in CI templates for GitHub, GitLab, and Bitbucket.
+- **`scan` / `upload-all` / `scans`** - scan a single artifact or a whole
+  directory, optionally submitting results to a Narvy account, and list
+  recent scans.
+- **`login` / `logout`** - link a machine to a Narvy account using an API
+  token stored locally.
+- False-positive precision tuning across the Android, iOS, and web analyzers.
+
+[0.9.0]: https://narvy.io

narvy_cli-1.0.0/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 2025-2026 Narvy
+
+   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.

narvy_cli-1.0.0/MANIFEST.in

@@ -0,0 +1,10 @@
+include README.md LICENSE SECURITY.md CHANGELOG.md
+
+# Never distributed, under any build path.
+prune narvy/_pro_rules
+prune tests
+prune tools
+prune private
+prune venv
+recursive-exclude narvy/_pro_rules *
+global-exclude *.pyc

narvy_cli-1.0.0/PKG-INFO

@@ -0,0 +1,165 @@
+Metadata-Version: 2.4
+Name: narvy-cli
+Version: 1.0.0
+Summary: Free, local SAST scanner for Android, iOS, and polyglot web/backend source - plus passive web, host-audit, and cloud-posture scanning.
+Author: Narvy
+License: Apache-2.0
+Project-URL: Homepage, https://narvy.io
+Classifier: Development Status :: 5 - Production/Stable
+Classifier: Environment :: Console
+Classifier: Intended Audience :: Developers
+Classifier: License :: OSI Approved :: Apache Software License
+Classifier: Operating System :: OS Independent
+Classifier: Programming Language :: Python :: 3
+Classifier: Programming Language :: Python :: 3.10
+Classifier: Programming Language :: Python :: 3.11
+Classifier: Programming Language :: Python :: 3.12
+Classifier: Topic :: Security
+Classifier: Topic :: Software Development :: Quality Assurance
+Requires-Python: >=3.10
+Description-Content-Type: text/markdown
+License-File: LICENSE
+Requires-Dist: pyaxmlparser
+Requires-Dist: pyyaml
+Requires-Dist: rich
+Requires-Dist: requests
+Requires-Dist: semgrep==1.152.0
+Requires-Dist: lief
+Provides-Extra: ios-full
+Requires-Dist: icdump; extra == "ios-full"
+Provides-Extra: cloud
+Requires-Dist: boto3; extra == "cloud"
+Dynamic: license-file
+
+# Narvy CLI
+
+[![PyPI version](https://badge.fury.io/py/narvy-cli.svg)](https://badge.fury.io/py/narvy-cli)
+[![License: Apache 2.0](https://img.shields.io/badge/License-Apache%202.0-blue.svg)](https://opensource.org/licenses/Apache-2.0)
+
+A free, local static application security testing (SAST) scanner. It runs
+entirely on your machine, needs no account, and finds real, high-signal
+vulnerabilities - hardcoded secrets, insecure configuration, weak
+cryptography, SSRF, injection, and more - in:
+
+- **Android**: `.apk` / `.aab`, split-APK bundles (`.apkm` / `.xapk` /
+  `.apks`), or a raw Gradle/Kotlin source checkout
+- **iOS**: an unencrypted `.ipa`, or a raw Xcode/Swift source checkout
+- **Web/backend source**: JavaScript/TypeScript, Python, PHP, Go, Ruby,
+  Rust, Java/Kotlin, C#/.NET
+
+It also ships three standalone scanners that need nothing but network
+access or your own existing credentials:
+
+- `web-scan` - passive Nuclei-based scan of a live URL
+- `host-audit` - agentless host audit over your own SSH access (Narvy's own
+  host checks plus Lynis (GPL-3.0) as the hardening baseline)
+- `cloud-scan` - AWS account posture check using your own ambient AWS
+  credentials
+
+Nothing is uploaded anywhere unless you explicitly pass `--upload`.
+
+## Install
+
+```bash
+pip install narvy-cli
+```
+
+Requires a Java 11+ JRE on your `PATH` for Android scanning (jadx itself is
+auto-downloaded on first scan into `~/.narvy/tools`). Everything else
+is pure Python plus a couple of optional extras:
+
+```bash
+pip install 'narvy-cli[ios-full]'  # full Obj-C introspection for iOS binary scans
+pip install 'narvy-cli[cloud]'     # boto3, needed for cloud-scan
+```
+
+## Usage
+
+```bash
+# Android APK/AAB, split bundle, or a Gradle/Kotlin source checkout
+narvy scan app-release.apk
+narvy scan app.apkm
+narvy scan ./my-android-app/
+
+# iOS: unencrypted IPA, or a Swift/Xcode source checkout
+narvy scan MyApp.ipa
+narvy scan ./my-ios-app/
+
+# Web/backend source (Node, Python, PHP, Go, Ruby, Rust, Java/Kotlin, C#/.NET)
+narvy scan ./my-api-repo/
+
+# SARIF output, for CI or GitHub/GitLab code scanning
+narvy scan app-release.apk --output sarif --file results.sarif
+
+# Passive web scan of a live URL - no active injection payloads, ever
+narvy web-scan https://example.com
+
+# Agentless host hardening audit over your own SSH access
+narvy host-audit example.com --user deploy
+
+# AWS account posture check using your own aws configure / env vars / IAM role
+narvy cloud-scan
+
+# List recent scans on your Narvy account (requires `narvy login`)
+narvy scans
+
+# Scan + upload every .apk/.aab/.apkm/.xapk/.ipa found in a folder, in one command
+narvy upload-all ./my-apps-folder/
+```
+
+Run `narvy doctor` before your first scan to check your Java/jadx/iOS
+tooling setup, and `narvy <command> --help` for the full flag list of
+any subcommand.
+
+### Very large Android apps
+
+Decompiling is memory-hungry, and file size is a poor predictor of how much
+you need. Before decompiling, the CLI reads the DEX headers to estimate the
+Java heap the app needs and checks it against `--max-mem` and your
+machine's free memory, so an app that won't fit fails in about a second
+instead of after several minutes of doomed work. The estimate is a
+heuristic, not a hard limit - `--force` runs the decompile regardless.
+
+### Optional Narvy Cloud scan
+
+`narvy login` links the CLI to a Narvy account. Add `--upload`
+to a scan to also submit it for a deeper cloud pass (full taint
+analysis, compliance mapping, dashboard history) - not required for local
+scanning, and not on by default. `narvy upload-all <directory>` does
+the same for every binary target found in a folder in one command.
+`narvy scans` lists recent scans on your account from the terminal.
+
+## Known limitations
+
+- Encrypted iOS binaries (the normal App Store distribution state) are
+  detected but not decrypted; only the local, static checks that don't need
+  the decrypted binary run.
+- Web-source coverage depth isn't uniform across all eight languages - Rust
+  and C#/.NET have a smaller rule set than the others, and the CLI says so
+  in its own output when it applies.
+- Only one architecture's native libraries are checked in a multi-ABI
+  APK/split bundle.
+
+See [SETUP.md](SETUP.md) for detailed install/troubleshooting steps and the
+exact commands this README's examples were run against.
+
+## License
+
+Apache License 2.0 - see [LICENSE](LICENSE).
+
+Rule packs under `narvy/rules/` are authored by Narvy
+(Apache 2.0, same as the rest of this package) and contain no third-party
+rule text.
+`host-audit` runs Narvy's own host checks (secrets exposed on disk,
+unauthenticated data services, cloud metadata exposure, container/daemon
+posture, exposed VCS/artifacts in web roots) and, as the hardening baseline,
+shells out to [Lynis](https://cisofy.com/lynis/) (GPL-3.0), auto-fetched at
+run time over your SSH access, run arm's-length, never bundled. Lynis is
+attributed as the engine in the audit output; its controls are not presented
+as Narvy's own.
+
+## Contributing
+
+Issues and pull requests welcome, especially new or improved detection
+rules. Rule packs live under `narvy/rules/`: Android/iOS
+(`rules/android`, `rules/ios`) and web/backend (`rules/web`, Semgrep-based).

narvy_cli-1.0.0/README.md

@@ -0,0 +1,132 @@
+# Narvy CLI
+
+[![PyPI version](https://badge.fury.io/py/narvy-cli.svg)](https://badge.fury.io/py/narvy-cli)
+[![License: Apache 2.0](https://img.shields.io/badge/License-Apache%202.0-blue.svg)](https://opensource.org/licenses/Apache-2.0)
+
+A free, local static application security testing (SAST) scanner. It runs
+entirely on your machine, needs no account, and finds real, high-signal
+vulnerabilities - hardcoded secrets, insecure configuration, weak
+cryptography, SSRF, injection, and more - in:
+
+- **Android**: `.apk` / `.aab`, split-APK bundles (`.apkm` / `.xapk` /
+  `.apks`), or a raw Gradle/Kotlin source checkout
+- **iOS**: an unencrypted `.ipa`, or a raw Xcode/Swift source checkout
+- **Web/backend source**: JavaScript/TypeScript, Python, PHP, Go, Ruby,
+  Rust, Java/Kotlin, C#/.NET
+
+It also ships three standalone scanners that need nothing but network
+access or your own existing credentials:
+
+- `web-scan` - passive Nuclei-based scan of a live URL
+- `host-audit` - agentless host audit over your own SSH access (Narvy's own
+  host checks plus Lynis (GPL-3.0) as the hardening baseline)
+- `cloud-scan` - AWS account posture check using your own ambient AWS
+  credentials
+
+Nothing is uploaded anywhere unless you explicitly pass `--upload`.
+
+## Install
+
+```bash
+pip install narvy-cli
+```
+
+Requires a Java 11+ JRE on your `PATH` for Android scanning (jadx itself is
+auto-downloaded on first scan into `~/.narvy/tools`). Everything else
+is pure Python plus a couple of optional extras:
+
+```bash
+pip install 'narvy-cli[ios-full]'  # full Obj-C introspection for iOS binary scans
+pip install 'narvy-cli[cloud]'     # boto3, needed for cloud-scan
+```
+
+## Usage
+
+```bash
+# Android APK/AAB, split bundle, or a Gradle/Kotlin source checkout
+narvy scan app-release.apk
+narvy scan app.apkm
+narvy scan ./my-android-app/
+
+# iOS: unencrypted IPA, or a Swift/Xcode source checkout
+narvy scan MyApp.ipa
+narvy scan ./my-ios-app/
+
+# Web/backend source (Node, Python, PHP, Go, Ruby, Rust, Java/Kotlin, C#/.NET)
+narvy scan ./my-api-repo/
+
+# SARIF output, for CI or GitHub/GitLab code scanning
+narvy scan app-release.apk --output sarif --file results.sarif
+
+# Passive web scan of a live URL - no active injection payloads, ever
+narvy web-scan https://example.com
+
+# Agentless host hardening audit over your own SSH access
+narvy host-audit example.com --user deploy
+
+# AWS account posture check using your own aws configure / env vars / IAM role
+narvy cloud-scan
+
+# List recent scans on your Narvy account (requires `narvy login`)
+narvy scans
+
+# Scan + upload every .apk/.aab/.apkm/.xapk/.ipa found in a folder, in one command
+narvy upload-all ./my-apps-folder/
+```
+
+Run `narvy doctor` before your first scan to check your Java/jadx/iOS
+tooling setup, and `narvy <command> --help` for the full flag list of
+any subcommand.
+
+### Very large Android apps
+
+Decompiling is memory-hungry, and file size is a poor predictor of how much
+you need. Before decompiling, the CLI reads the DEX headers to estimate the
+Java heap the app needs and checks it against `--max-mem` and your
+machine's free memory, so an app that won't fit fails in about a second
+instead of after several minutes of doomed work. The estimate is a
+heuristic, not a hard limit - `--force` runs the decompile regardless.
+
+### Optional Narvy Cloud scan
+
+`narvy login` links the CLI to a Narvy account. Add `--upload`
+to a scan to also submit it for a deeper cloud pass (full taint
+analysis, compliance mapping, dashboard history) - not required for local
+scanning, and not on by default. `narvy upload-all <directory>` does
+the same for every binary target found in a folder in one command.
+`narvy scans` lists recent scans on your account from the terminal.
+
+## Known limitations
+
+- Encrypted iOS binaries (the normal App Store distribution state) are
+  detected but not decrypted; only the local, static checks that don't need
+  the decrypted binary run.
+- Web-source coverage depth isn't uniform across all eight languages - Rust
+  and C#/.NET have a smaller rule set than the others, and the CLI says so
+  in its own output when it applies.
+- Only one architecture's native libraries are checked in a multi-ABI
+  APK/split bundle.
+
+See [SETUP.md](SETUP.md) for detailed install/troubleshooting steps and the
+exact commands this README's examples were run against.
+
+## License
+
+Apache License 2.0 - see [LICENSE](LICENSE).
+
+Rule packs under `narvy/rules/` are authored by Narvy
+(Apache 2.0, same as the rest of this package) and contain no third-party
+rule text.
+`host-audit` runs Narvy's own host checks (secrets exposed on disk,
+unauthenticated data services, cloud metadata exposure, container/daemon
+posture, exposed VCS/artifacts in web roots) and, as the hardening baseline,
+shells out to [Lynis](https://cisofy.com/lynis/) (GPL-3.0), auto-fetched at
+run time over your SSH access, run arm's-length, never bundled. Lynis is
+attributed as the engine in the audit output; its controls are not presented
+as Narvy's own.
+
+## Contributing
+
+Issues and pull requests welcome, especially new or improved detection
+rules. Rule packs live under `narvy/rules/`: Android/iOS
+(`rules/android`, `rules/ios`) and web/backend (`rules/web`, Semgrep-based).

narvy_cli-1.0.0/SECURITY.md

@@ -0,0 +1,79 @@
+# Security Policy
+
+Narvy (LIMITLESS KNOWLEDGE, SIREN 994 833 143) takes the security of the
+Narvy CLI seriously. This document explains how to report a vulnerability
+and what you can expect from us.
+
+## Reporting a vulnerability
+
+**Email: security@narvy.io**
+
+Please include:
+
+- the CLI version (`narvy --version`) and your OS/architecture,
+- what the vulnerability is and where,
+- steps to reproduce, ideally a minimal proof of concept,
+- the impact you believe it has.
+
+Do **not** open a public GitHub issue for a security vulnerability. Use the
+email above (or GitHub's private "Report a vulnerability" advisory flow if
+enabled on the repository).
+
+If you need to send sensitive details encrypted, email us first with no
+sensitive content and we will agree an encrypted channel. We do not currently
+publish a PGP key and would rather say so than list one we do not use.
+
+## Our commitments
+
+- We **acknowledge** every good-faith report within **72 hours (3 business days)**.
+- We give a first assessment (reproduced / severity) within **10 business days**.
+- We keep you updated at least every **14 days** until resolution.
+- We practise **coordinated disclosure**: we agree a public disclosure date with
+  you, default **90 days**, sooner if a fix ships sooner. We will credit you if
+  you want it, or keep you anonymous.
+- Where warranted, we request a **CVE** so users can track the fix.
+
+We do not run a paid bug-bounty programme today, and we will not imply one we
+cannot fund. We intend to introduce one as we grow.
+
+## Safe harbour
+
+We will not pursue or support legal action against you for security research
+conducted in good faith that respects this policy: stay in scope, avoid harm to
+people, data and availability, only access data that is your own, and give us a
+reasonable chance to fix before disclosing. Full terms, including the platform
+scope, are on our disclosure page: https://narvy.io/security
+
+## Supported versions
+
+Security fixes are provided for the **latest released minor version** of the
+CLI. Users on older versions should upgrade to receive fixes.
+
+| Version | Supported |
+|---|---|
+| Latest release | Yes |
+| Previous minor | Best effort |
+| Older | No, please upgrade |
+
+
+## Regulated reporting (Cyber Resilience Act)
+
+As the manufacturer of a product with digital elements placed on the EU market,
+LIMITLESS KNOWLEDGE is subject to the reporting obligations of Article 14 of the
+EU Cyber Resilience Act (Regulation (EU) 2024/2847), which apply from
+**11 September 2026**. If a vulnerability in a shipped CLI release is found to be
+**actively exploited**, we are required to notify ENISA and our national CSIRT
+(CERT-FR / ANSSI, France) on a 24-hour early-warning, 72-hour notification, and
+14-day final-report cadence. This runs in parallel with the coordinated
+disclosure process above.
+
+## Software Bill of Materials (SBOM)
+
+Each CLI release ships with a **CycloneDX SBOM** of the CLI's own dependency
+tree (`narvy-<version>.cyclonedx.json`), attached to the release. See
+https://narvy.io/security for how to obtain it.
+
+---
+
+*This is our documented process and will be reviewed by counsel; it is not legal
+advice.*

narvy_cli-1.0.0/narvy/__init__.py

@@ -0,0 +1,3 @@
+"""Narvy CLI - free, local SAST for Android, iOS and polyglot source."""
+
+__version__ = "1.0.0"