skyveda 0.4.1__tar.gz

skyveda-0.4.1/.gitattributes

@@ -0,0 +1,2 @@
+* text=auto eol=lf
+*.png binary

skyveda-0.4.1/.github/workflows/ci.yml

@@ -0,0 +1,33 @@
+name: ci
+
+on:
+  push:
+    branches: [main]
+  pull_request:
+
+permissions:
+  contents: read
+
+jobs:
+  check:
+    strategy:
+      fail-fast: false
+      matrix:
+        os: [ubuntu-latest, windows-latest]
+    runs-on: ${{ matrix.os }}
+    steps:
+      - uses: actions/checkout@v4
+      - uses: astral-sh/setup-uv@v6
+        with:
+          python-version: "3.12"
+          enable-cache: true
+      - name: Install
+        run: uv sync --all-extras --locked
+      - name: Lint
+        run: uv run ruff check
+      - name: Format
+        run: uv run ruff format --check
+      - name: Type-check
+        run: uv run mypy
+      - name: Test
+        run: uv run pytest

skyveda-0.4.1/.gitignore

@@ -0,0 +1,30 @@
+# Python
+__pycache__/
+*.py[cod]
+.venv/
+dist/
+build/
+*.egg-info/
+.mypy_cache/
+.pytest_cache/
+.ruff_cache/
+.coverage
+
+# Scan output and live recordings may contain client data: never commit them.
+out/
+recordings/
+
+# Terraform (lab)
+.terraform/
+*.tfstate
+*.tfstate.*
+*.tfvars
+.terraform.lock.hcl
+
+# Editors / OS
+.vscode/
+.idea/
+.DS_Store
+.ops/
+lab/azure/expected.json
+lab/azure/flagged.json

skyveda-0.4.1/.python-version

@@ -0,0 +1 @@
+3.12

skyveda-0.4.1/CONTRIBUTING.md

@@ -0,0 +1,37 @@
+# Contributing
+
+Thank you for helping. Contributions are accepted under the Apache License 2.0, the same licence
+as the project (inbound = outbound).
+
+## Sign off every commit
+
+Every commit must carry a Developer Certificate of Origin sign-off
+(https://developercertificate.org):
+
+```bash
+git commit -s
+```
+
+This adds `Signed-off-by: Your Name <you@example.com>` and confirms you have the right to submit
+the change under the project's licence. Pull requests with unsigned commits are not merged.
+
+## Rules the code must keep
+
+- **Read-only.** Only read, list and get APIs. No call that creates, changes or deletes anything.
+- **Real fields only.** Every property path in a check must exist in the provider's API or
+  Resource Graph schema, with a fixture that shows it.
+- **No real data.** Never put real subscription or tenant IDs, resource names, keys or customer
+  data in code, fixtures, issues or pull requests. Use the placeholders in `tests/fixtures`.
+- **Tests never touch the cloud.** Sockets are disabled in the test run.
+
+## Before opening a pull request
+
+```bash
+uv sync --all-extras
+uv run ruff check && uv run ruff format --check
+uv run mypy
+uv run pytest
+```
+
+Security problems go by email, not in an issue: see [SECURITY.md](SECURITY.md).
+The Skyveda name is not covered by the code licence: see [TRADEMARKS.md](TRADEMARKS.md).

skyveda-0.4.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.

skyveda-0.4.1/NOTICE

@@ -0,0 +1,10 @@
+Skyveda Scan
+Copyright 2026 Skyveda
+
+This product is licensed under the Apache License, Version 2.0 (see LICENSE).
+
+"Skyveda" is a trademark of Skyveda. The Apache
+License does not grant permission to use it (section 6). See TRADEMARKS.md.
+
+Microsoft and Azure are trademarks of the Microsoft group of companies.
+Skyveda is not affiliated with or endorsed by Microsoft.

skyveda-0.4.1/PKG-INFO

@@ -0,0 +1,162 @@
+Metadata-Version: 2.5
+Name: skyveda
+Version: 0.4.1
+Summary: Read-only cloud platform health scanner that produces a scored HTML report.
+Author-email: Skyveda <skyvedahq@gmail.com>
+License-Expression: Apache-2.0
+License-File: LICENSE
+License-File: NOTICE
+Classifier: Environment :: Console
+Classifier: Programming Language :: Python :: 3.12
+Classifier: Topic :: System :: Systems Administration
+Requires-Python: >=3.12
+Requires-Dist: jinja2>=3.1
+Requires-Dist: pydantic>=2.7
+Requires-Dist: pyyaml>=6.0
+Requires-Dist: reportlab>=4.2
+Requires-Dist: rich>=13.7
+Requires-Dist: typer>=0.12
+Provides-Extra: azure
+Requires-Dist: azure-identity>=1.17; extra == 'azure'
+Requires-Dist: azure-mgmt-resourcegraph>=8.0; extra == 'azure'
+Description-Content-Type: text/markdown
+
+# Skyveda Scan
+
+Read-only command-line scanner that checks a cloud environment against a catalogue of
+best-practice checks and produces a scored HTML report with prioritised findings, estimated
+monthly waste in ₹ (INR) and fix guidance.
+
+* **Read-only.** Only read/list/get APIs. On Azure it works with the built-in **Reader** role
+  (plus **Cost Management Reader** for cost checks).
+* **Local only.** No telemetry; nothing leaves your machine except the output files you write.
+* **Checks are data.** Each check is one YAML file.
+
+> Status: early development (v0.4: 60 Azure checks mapped to MCSB and Well-Architected, billed cost, fix pack). Azure first; AWS and GCP later.
+
+## Install
+
+From PyPI (Python 3.12+):
+
+```bash
+pip install "skyveda[azure]"
+```
+
+Or:
+
+* **Azure Cloud Shell (recommended for customers):** build the bundle with
+  `uv run python packaging/build_cloudshell_bundle.py`, upload
+  `dist/skyveda-cloudshell-<version>.zip` to Cloud Shell, then run
+  `unzip -o skyveda-cloudshell-*.zip && bash skyveda-cloudshell/install.sh`.
+  See [packaging/cloudshell/README.txt](packaging/cloudshell/README.txt).
+* **From the wheel:** `pip install "skyveda-<version>-py3-none-any.whl[azure]"` (Python 3.12+).
+
+On an Azure VM, the default credential uses the VM's managed identity before `az login`;
+pass `--auth cli` to scan as your `az login` account, and `--tenant <id>` to refuse any other
+tenant.
+
+## Usage
+
+```bash
+az login                                   # or service principal env vars / managed identity
+skyveda scopes                              # which subscriptions can I read?
+skyveda scan --provider azure --subscription <id> --out ./out
+skyveda scan --offline tests/fixtures/azure # run on recorded data, no cloud access
+skyveda list-checks                         # the check catalogue
+skyveda validate-checks                     # check YAML files are valid
+```
+
+Options: `--subscription` (repeat or comma-separate), `--management-group`, `--tenant`,
+`--label` (a line under the report title), `--waivers`, `--pdf` (also write report.pdf).
+
+### Config file
+
+Save options in a `skyveda.toml` and pass `--config skyveda.toml` to `scan` or `scopes`. Options
+typed on the command line override the file. Paths in the file are relative to the file. Never put
+credentials in it: sign-in uses `az login`, managed identity or environment variables as usual.
+
+```toml
+schema_version = 1
+
+[scan]
+subscriptions = ["<subscription-id>"]
+tenant = "<tenant-id>"
+auth = "cli"
+out = "skyveda-out"
+fail_on = "high"
+label = "Prepared for cust-001"
+waivers = "waivers.yaml"
+pdf = true
+```
+
+### Waivers
+
+A `waivers.yaml` takes accepted risks and wrong findings out of the findings, the ₹ total and the
+scores. The report lists every waiver in Appendix D, so nothing disappears silently.
+
+```yaml
+schema_version: 1
+waivers:
+  - check: AZ-NET-001
+    resource: /subscriptions/<id>/resourceGroups/<rg>/providers/Microsoft.Network/networkSecurityGroups/<nsg>
+    kind: accepted_risk        # or false_positive
+    reason: Vendor access, limited by the upstream firewall
+    approver: Head of Platform
+    expires: 2027-03-31        # applies up to and including this date
+```
+
+Omit `resource` to waive every resource the check flags. Expired waivers, and waivers that match
+nothing, are not applied and are listed as warnings. To apply waivers to a findings.json someone
+sent you, use `skyveda report findings.json --waivers waivers.yaml --out <new dir>`; the original
+file is never changed.
+
+### Fix pack
+
+`skyveda fixes` turns findings into reviewable work. It only **writes files**: it runs no command,
+calls no cloud and needs no credentials.
+
+```bash
+skyveda fixes out/findings.json --out ./fixes [--waivers waivers.yaml]
+```
+
+* `fixes/README.md`: the plan, ordered by severity and then ₹ a month, with risk, downtime and the
+  script for each item, plus a "Manual fix: see report" list for checks with no fix template.
+* `fixes/<check-id>/<resource-name>.sh`: one script per resource, with risk, downtime, before-steps,
+  rollback and verify lines in the header. **Every command is commented out**: a reviewer removes
+  the `# ` on purpose, after reading it.
+* `fixes/PULL_REQUEST.md`: text to paste into your pull request.
+
+Waived resources are skipped. A non-empty `--out` is refused unless you add `--force`, which first
+removes only the old pack's `<check-id>/*.sh`, `README.md` and `PULL_REQUEST.md`. Fix templates (az CLI) exist for AZ-COST-001 to 004, AZ-NET-001 and
+AZ-STG-001. A check adds one with an optional `remedy:` block in its YAML, and `{placeholders}` may
+only use columns the check's query projects (plus `id`, `name` and `subscriptionId`).
+
+Exit codes: `0` ran fine · `2` findings at or above `--fail-on` (default `critical`) · `1` error.
+
+### Framework mapping
+
+Every check carries a `frameworks:` block that maps it to the Microsoft cloud security benchmark (MCSB) and to Well-Architected pillars and recommendations. Each finding shows a "Maps to" line, and the HTML and PDF reports add a per-control and per-pillar pass and fail summary. MCSB control IDs are from the Microsoft cloud security benchmark v2 (preview); the same IDs exist in v1, the default in Microsoft Defender for Cloud. Well-Architected IDs are Skyveda's mapping to Microsoft's published checklists. Skyveda maps to these frameworks; it does not certify compliance. `skyveda validate-checks` rejects malformed IDs.
+
+## Development
+
+Requires [uv](https://docs.astral.sh/uv/). Python 3.12 is installed automatically.
+
+```bash
+uv sync --all-extras
+uv run ruff check && uv run ruff format --check
+uv run mypy
+uv run pytest            # sockets are disabled: tests can never reach the cloud
+```
+
+## Contributing and security
+
+See [CONTRIBUTING.md](CONTRIBUTING.md); every commit needs a `git commit -s` sign-off. Report
+vulnerabilities by email, not in an issue: see [SECURITY.md](SECURITY.md).
+
+## Licence
+
+Apache-2.0. See [LICENSE](LICENSE) and [NOTICE](NOTICE). The Skyveda™ name is not licensed with
+the code: see [TRADEMARKS.md](TRADEMARKS.md).
+
+Microsoft and Azure are trademarks of the Microsoft group of companies. Skyveda is not affiliated
+with or endorsed by Microsoft.

skyveda-0.4.1/README.md

@@ -0,0 +1,139 @@
+# Skyveda Scan
+
+Read-only command-line scanner that checks a cloud environment against a catalogue of
+best-practice checks and produces a scored HTML report with prioritised findings, estimated
+monthly waste in ₹ (INR) and fix guidance.
+
+* **Read-only.** Only read/list/get APIs. On Azure it works with the built-in **Reader** role
+  (plus **Cost Management Reader** for cost checks).
+* **Local only.** No telemetry; nothing leaves your machine except the output files you write.
+* **Checks are data.** Each check is one YAML file.
+
+> Status: early development (v0.4: 60 Azure checks mapped to MCSB and Well-Architected, billed cost, fix pack). Azure first; AWS and GCP later.
+
+## Install
+
+From PyPI (Python 3.12+):
+
+```bash
+pip install "skyveda[azure]"
+```
+
+Or:
+
+* **Azure Cloud Shell (recommended for customers):** build the bundle with
+  `uv run python packaging/build_cloudshell_bundle.py`, upload
+  `dist/skyveda-cloudshell-<version>.zip` to Cloud Shell, then run
+  `unzip -o skyveda-cloudshell-*.zip && bash skyveda-cloudshell/install.sh`.
+  See [packaging/cloudshell/README.txt](packaging/cloudshell/README.txt).
+* **From the wheel:** `pip install "skyveda-<version>-py3-none-any.whl[azure]"` (Python 3.12+).
+
+On an Azure VM, the default credential uses the VM's managed identity before `az login`;
+pass `--auth cli` to scan as your `az login` account, and `--tenant <id>` to refuse any other
+tenant.
+
+## Usage
+
+```bash
+az login                                   # or service principal env vars / managed identity
+skyveda scopes                              # which subscriptions can I read?
+skyveda scan --provider azure --subscription <id> --out ./out
+skyveda scan --offline tests/fixtures/azure # run on recorded data, no cloud access
+skyveda list-checks                         # the check catalogue
+skyveda validate-checks                     # check YAML files are valid
+```
+
+Options: `--subscription` (repeat or comma-separate), `--management-group`, `--tenant`,
+`--label` (a line under the report title), `--waivers`, `--pdf` (also write report.pdf).
+
+### Config file
+
+Save options in a `skyveda.toml` and pass `--config skyveda.toml` to `scan` or `scopes`. Options
+typed on the command line override the file. Paths in the file are relative to the file. Never put
+credentials in it: sign-in uses `az login`, managed identity or environment variables as usual.
+
+```toml
+schema_version = 1
+
+[scan]
+subscriptions = ["<subscription-id>"]
+tenant = "<tenant-id>"
+auth = "cli"
+out = "skyveda-out"
+fail_on = "high"
+label = "Prepared for cust-001"
+waivers = "waivers.yaml"
+pdf = true
+```
+
+### Waivers
+
+A `waivers.yaml` takes accepted risks and wrong findings out of the findings, the ₹ total and the
+scores. The report lists every waiver in Appendix D, so nothing disappears silently.
+
+```yaml
+schema_version: 1
+waivers:
+  - check: AZ-NET-001
+    resource: /subscriptions/<id>/resourceGroups/<rg>/providers/Microsoft.Network/networkSecurityGroups/<nsg>
+    kind: accepted_risk        # or false_positive
+    reason: Vendor access, limited by the upstream firewall
+    approver: Head of Platform
+    expires: 2027-03-31        # applies up to and including this date
+```
+
+Omit `resource` to waive every resource the check flags. Expired waivers, and waivers that match
+nothing, are not applied and are listed as warnings. To apply waivers to a findings.json someone
+sent you, use `skyveda report findings.json --waivers waivers.yaml --out <new dir>`; the original
+file is never changed.
+
+### Fix pack
+
+`skyveda fixes` turns findings into reviewable work. It only **writes files**: it runs no command,
+calls no cloud and needs no credentials.
+
+```bash
+skyveda fixes out/findings.json --out ./fixes [--waivers waivers.yaml]
+```
+
+* `fixes/README.md`: the plan, ordered by severity and then ₹ a month, with risk, downtime and the
+  script for each item, plus a "Manual fix: see report" list for checks with no fix template.
+* `fixes/<check-id>/<resource-name>.sh`: one script per resource, with risk, downtime, before-steps,
+  rollback and verify lines in the header. **Every command is commented out**: a reviewer removes
+  the `# ` on purpose, after reading it.
+* `fixes/PULL_REQUEST.md`: text to paste into your pull request.
+
+Waived resources are skipped. A non-empty `--out` is refused unless you add `--force`, which first
+removes only the old pack's `<check-id>/*.sh`, `README.md` and `PULL_REQUEST.md`. Fix templates (az CLI) exist for AZ-COST-001 to 004, AZ-NET-001 and
+AZ-STG-001. A check adds one with an optional `remedy:` block in its YAML, and `{placeholders}` may
+only use columns the check's query projects (plus `id`, `name` and `subscriptionId`).
+
+Exit codes: `0` ran fine · `2` findings at or above `--fail-on` (default `critical`) · `1` error.
+
+### Framework mapping
+
+Every check carries a `frameworks:` block that maps it to the Microsoft cloud security benchmark (MCSB) and to Well-Architected pillars and recommendations. Each finding shows a "Maps to" line, and the HTML and PDF reports add a per-control and per-pillar pass and fail summary. MCSB control IDs are from the Microsoft cloud security benchmark v2 (preview); the same IDs exist in v1, the default in Microsoft Defender for Cloud. Well-Architected IDs are Skyveda's mapping to Microsoft's published checklists. Skyveda maps to these frameworks; it does not certify compliance. `skyveda validate-checks` rejects malformed IDs.
+
+## Development
+
+Requires [uv](https://docs.astral.sh/uv/). Python 3.12 is installed automatically.
+
+```bash
+uv sync --all-extras
+uv run ruff check && uv run ruff format --check
+uv run mypy
+uv run pytest            # sockets are disabled: tests can never reach the cloud
+```
+
+## Contributing and security
+
+See [CONTRIBUTING.md](CONTRIBUTING.md); every commit needs a `git commit -s` sign-off. Report
+vulnerabilities by email, not in an issue: see [SECURITY.md](SECURITY.md).
+
+## Licence
+
+Apache-2.0. See [LICENSE](LICENSE) and [NOTICE](NOTICE). The Skyveda™ name is not licensed with
+the code: see [TRADEMARKS.md](TRADEMARKS.md).
+
+Microsoft and Azure are trademarks of the Microsoft group of companies. Skyveda is not affiliated
+with or endorsed by Microsoft.

skyveda-0.4.1/SECURITY.md

@@ -0,0 +1,27 @@
+# Security
+
+Skyveda Scan is built to be read-only: it calls only read, list and get APIs, and runs with the
+built-in Reader role. A way to make it change, create or delete anything in a cloud account is
+the most serious kind of report we can receive.
+
+## Reporting a vulnerability
+
+Email **skyvedahq@gmail.com** with "Security" in the subject. Please do not open a public issue.
+
+Include the version (`skyveda --version`), what you did, and what happened. Do not send real
+subscription IDs, tenant IDs, resource names, keys or customer data; describe them or replace
+them with placeholders.
+
+You will get a reply within 5 working days. We will agree a fix and a disclosure date with you,
+and credit you in the release notes unless you prefer not to be named.
+
+## In scope
+
+- any path by which the scanner writes to, or calls a non-read API on, a cloud account
+- leaks of credentials, tokens or scan output
+- the Cloud Shell bundle and its install script
+- injection through scan data into the HTML or PDF report
+
+## Supported versions
+
+Only the latest release receives fixes.

skyveda-0.4.1/TRADEMARKS.md

@@ -0,0 +1,22 @@
+# Trademarks
+
+The code in this repository is licensed under Apache 2.0. The name **Skyveda™** and any Skyveda
+logo are not. Section 6 of the licence grants no right to use them.
+
+You may:
+
+- say that your work is based on, or works with, Skyveda Scan, in plain text;
+- keep the name in the copyright and NOTICE lines, as the licence requires.
+
+You may not, without written permission:
+
+- call a fork, a product, a service, a domain or an account "Skyveda", or a name that could be
+  mistaken for it;
+- suggest that Skyveda made, reviewed or endorses your work.
+
+If you publish a modified version, give it a different name.
+
+Microsoft and Azure are trademarks of the Microsoft group of companies. Skyveda is not affiliated
+with or endorsed by Microsoft.
+
+Questions: skyvedahq@gmail.com