guardana-reference-pack 0.1.2__tar.gz

guardana_reference_pack-0.1.2/.gitignore

@@ -0,0 +1,47 @@
+__pycache__/
+*.py[cod]
+.venv/
+.uv/
+/dist/
+# Written by scripts/generate_sbom.py; published as release assets, never committed.
+sbom/
+/build/
+*.egg-info/
+**/*.egg-info/
+.mypy_cache/
+.ruff_cache/
+.pytest_cache/
+.import_linter_cache/
+.coverage
+.coverage.*
+coverage.xml
+htmlcov/
+.python-version
+
+# OS
+.DS_Store
+Thumbs.db
+
+# Env / secrets
+.env
+.env.*
+
+# Editors
+.vscode/
+.idea/
+
+# Logs
+*.log
+
+# Agent tooling. `.claude/settings.json`, `.claude/skills/`, `.claude/agents/` and
+# `.claude/rules/` ARE checked in on purpose: every agent working here gets the hooks
+# and the project's own procedures, and an ignored hook is a promise nobody keeps.
+# Only machine-local state and gate logs stay out.
+.claude/settings.local.json
+.claude/scheduled_tasks.lock
+.claude/worktrees/
+.playwright-mcp/
+cache/
+
+# Work in flight, plans, audits and research notes: never published.
+.work/

guardana_reference_pack-0.1.2/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 2026 Guardana contributors
+
+   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.

guardana_reference_pack-0.1.2/PKG-INFO

@@ -0,0 +1,99 @@
+Metadata-Version: 2.5
+Name: guardana-reference-pack
+Version: 0.1.2
+Summary: A Guardana extension pack that uses all six extension points through the supported surface only.
+Project-URL: Homepage, https://guardana.dev
+Project-URL: Repository, https://github.com/guardana/guardana
+Project-URL: Documentation, https://guardana.dev/docs/
+License-Expression: Apache-2.0
+License-File: LICENSE
+Classifier: Typing :: Typed
+Requires-Python: >=3.11
+Requires-Dist: guardana-core>=0.41
+Description-Content-Type: text/markdown
+
+# `guardana-reference-pack`
+
+A Guardana extension pack that uses all six extension points and imports nothing outside
+the [supported surface](../../docs/compatibility.md). It has its own version (`0.1.2`),
+depends on `guardana-core>=0.41` with no upper bound, and declares the `extension_api` and
+`output_api` ranges it runs on in its manifest. `guardana pack validate` checks those ranges;
+installing the pack or running a scan does not. A CI job that depends on the pack therefore
+runs `guardana pack validate` and `guardana pack lock --check`. Install it from this directory
+or from the wheel and sdist attached to each GitHub Release. The release workflow's PyPI step
+for the pack is off unless a maintainer has registered the pack's trusted publisher on PyPI
+and switched the step on in the repository settings.
+
+`custom_rule` and `output_pack` teach one idea each. This pack is an example a third party
+can copy: everything in it is checked by the commands and the conformance kit Guardana
+ships, from an isolated install.
+
+## What it ships
+
+| Extension point | What | File |
+|---|---|---|
+| `guardana.rules` | `reference.prompt.codename_disclosure`, a YAML rule graded by the pack's own evaluator | `src/guardana_reference_pack/rules/codename_disclosure.yaml` |
+| `guardana.rules` | `reference.supply_chain.unpinned_requirement`, a Python rule over pip requirement files | `src/guardana_reference_pack/unpinned.py` |
+| `guardana.evaluators` | `reference.marker`: a reply fails when it repeats a configured marker | `src/guardana_reference_pack/evaluator.py` |
+| `guardana.targets` | `reference-requirements://<dir>`: the requirement files under a directory | `src/guardana_reference_pack/target.py` |
+| `guardana.taxonomies` | `REFERENCE-CONTROLS`, the pack's own control catalogue (`REF-1`, `REF-2`) | `src/guardana_reference_pack/controls.py` |
+| `guardana.renderers` | `--format reference-summary`: the run as Markdown | `src/guardana_reference_pack/summary.py` |
+| `guardana.reporters` | `--reporter reference-file://<dir>`: that Markdown, written to `<dir>/guardana-<run id>.md` | `src/guardana_reference_pack/file_reporter.py` |
+
+Both rules declare a finding, a clean and an inconclusive sample, so
+`guardana rule test 'reference.*'` proves each one fires, stays silent and declines. The
+manifest, `src/guardana_reference_pack/guardana-pack.yaml`, is schema 3, and
+`guardana-lock.yaml` pins what the pack registers.
+
+The reporter's `prepare` only checks the locator. `deliver` writes through a temporary
+file, `fsync`s it and moves it into place, then reports `delivered`; a directory that does
+not exist is `unreachable`, and an `OSError` while writing is `rejected`. The file is
+readable by its owner only.
+
+## Try it
+
+From the repository root:
+
+```bash
+uv pip install ./examples/reference_pack
+ADMIT="--plugins allowlist --allow-plugin guardana-reference-pack"
+uv run guardana rule test 'reference.*' $ADMIT
+uv run guardana pack validate $ADMIT
+mkdir -p summaries
+uv run guardana scan --target reference-requirements://. $ADMIT \
+  --format reference-summary --reporter reference-file://summaries
+```
+
+## Its own suite
+
+`tests/` runs from an isolated install, the way CI and `scripts/ci_local.sh` run it:
+
+```bash
+uv run --isolated --no-cache \
+  --with ./packages/guardana-core --with ./packages/guardana-rules \
+  --with ./packages/guardana-cli --with ./packages/guardana-report \
+  --with ./examples/reference_pack --with pytest pytest examples/reference_pack/tests
+```
+
+`tests/test_reference_surface.py` walks every import in `src/` and `tests/` and refuses a
+`guardana.*` name outside the supported surface, computed from the installed build:
+`__all__` of `guardana.core` (less `Runner`), `guardana.core.verify`,
+`guardana.core.doubles`, `guardana.core.target.protocols`, `guardana.core.output`,
+`guardana.testing` and `guardana.core.testing`, plus `guardana.core.target.WireProtocol`
+and the public names of `guardana.core.rule.fixture`.
+
+`guardana-lock.yaml` holds the pack's own entry only: the built-in pack's entry moves with
+every Guardana release, so the lock test takes it from the installed build and runs
+`pack lock --check` over both. After changing a rule, regenerate the lock from an isolated
+install:
+
+```bash
+uv run --isolated --no-cache \
+  --with ./packages/guardana-core --with ./packages/guardana-rules \
+  --with ./packages/guardana-cli --with ./packages/guardana-report \
+  --with ./examples/reference_pack \
+  guardana pack lock examples/reference_pack/guardana-lock.yaml \
+  --plugins allowlist --allow-plugin guardana-reference-pack
+```
+
+Then delete every entry but `guardana-reference-pack` under `packs:`.

guardana_reference_pack-0.1.2/README.md

@@ -0,0 +1,85 @@
+# `guardana-reference-pack`
+
+A Guardana extension pack that uses all six extension points and imports nothing outside
+the [supported surface](../../docs/compatibility.md). It has its own version (`0.1.2`),
+depends on `guardana-core>=0.41` with no upper bound, and declares the `extension_api` and
+`output_api` ranges it runs on in its manifest. `guardana pack validate` checks those ranges;
+installing the pack or running a scan does not. A CI job that depends on the pack therefore
+runs `guardana pack validate` and `guardana pack lock --check`. Install it from this directory
+or from the wheel and sdist attached to each GitHub Release. The release workflow's PyPI step
+for the pack is off unless a maintainer has registered the pack's trusted publisher on PyPI
+and switched the step on in the repository settings.
+
+`custom_rule` and `output_pack` teach one idea each. This pack is an example a third party
+can copy: everything in it is checked by the commands and the conformance kit Guardana
+ships, from an isolated install.
+
+## What it ships
+
+| Extension point | What | File |
+|---|---|---|
+| `guardana.rules` | `reference.prompt.codename_disclosure`, a YAML rule graded by the pack's own evaluator | `src/guardana_reference_pack/rules/codename_disclosure.yaml` |
+| `guardana.rules` | `reference.supply_chain.unpinned_requirement`, a Python rule over pip requirement files | `src/guardana_reference_pack/unpinned.py` |
+| `guardana.evaluators` | `reference.marker`: a reply fails when it repeats a configured marker | `src/guardana_reference_pack/evaluator.py` |
+| `guardana.targets` | `reference-requirements://<dir>`: the requirement files under a directory | `src/guardana_reference_pack/target.py` |
+| `guardana.taxonomies` | `REFERENCE-CONTROLS`, the pack's own control catalogue (`REF-1`, `REF-2`) | `src/guardana_reference_pack/controls.py` |
+| `guardana.renderers` | `--format reference-summary`: the run as Markdown | `src/guardana_reference_pack/summary.py` |
+| `guardana.reporters` | `--reporter reference-file://<dir>`: that Markdown, written to `<dir>/guardana-<run id>.md` | `src/guardana_reference_pack/file_reporter.py` |
+
+Both rules declare a finding, a clean and an inconclusive sample, so
+`guardana rule test 'reference.*'` proves each one fires, stays silent and declines. The
+manifest, `src/guardana_reference_pack/guardana-pack.yaml`, is schema 3, and
+`guardana-lock.yaml` pins what the pack registers.
+
+The reporter's `prepare` only checks the locator. `deliver` writes through a temporary
+file, `fsync`s it and moves it into place, then reports `delivered`; a directory that does
+not exist is `unreachable`, and an `OSError` while writing is `rejected`. The file is
+readable by its owner only.
+
+## Try it
+
+From the repository root:
+
+```bash
+uv pip install ./examples/reference_pack
+ADMIT="--plugins allowlist --allow-plugin guardana-reference-pack"
+uv run guardana rule test 'reference.*' $ADMIT
+uv run guardana pack validate $ADMIT
+mkdir -p summaries
+uv run guardana scan --target reference-requirements://. $ADMIT \
+  --format reference-summary --reporter reference-file://summaries
+```
+
+## Its own suite
+
+`tests/` runs from an isolated install, the way CI and `scripts/ci_local.sh` run it:
+
+```bash
+uv run --isolated --no-cache \
+  --with ./packages/guardana-core --with ./packages/guardana-rules \
+  --with ./packages/guardana-cli --with ./packages/guardana-report \
+  --with ./examples/reference_pack --with pytest pytest examples/reference_pack/tests
+```
+
+`tests/test_reference_surface.py` walks every import in `src/` and `tests/` and refuses a
+`guardana.*` name outside the supported surface, computed from the installed build:
+`__all__` of `guardana.core` (less `Runner`), `guardana.core.verify`,
+`guardana.core.doubles`, `guardana.core.target.protocols`, `guardana.core.output`,
+`guardana.testing` and `guardana.core.testing`, plus `guardana.core.target.WireProtocol`
+and the public names of `guardana.core.rule.fixture`.
+
+`guardana-lock.yaml` holds the pack's own entry only: the built-in pack's entry moves with
+every Guardana release, so the lock test takes it from the installed build and runs
+`pack lock --check` over both. After changing a rule, regenerate the lock from an isolated
+install:
+
+```bash
+uv run --isolated --no-cache \
+  --with ./packages/guardana-core --with ./packages/guardana-rules \
+  --with ./packages/guardana-cli --with ./packages/guardana-report \
+  --with ./examples/reference_pack \
+  guardana pack lock examples/reference_pack/guardana-lock.yaml \
+  --plugins allowlist --allow-plugin guardana-reference-pack
+```
+
+Then delete every entry but `guardana-reference-pack` under `packs:`.

guardana_reference_pack-0.1.2/guardana-lock.yaml

@@ -0,0 +1,23 @@
+schema_version: 3
+extension_api: 2
+packs:
+- name: guardana-reference-pack
+  distribution: guardana-reference-pack
+  version: 0.1.2
+  rules:
+    reference.prompt.codename_disclosure:
+      digest: b00991d5ddc71066
+    reference.supply_chain.unpinned_requirement:
+      digest: 533087d5b5815f7b
+  evaluators:
+  - reference.marker
+  targets:
+  - ReferenceRequirementsTarget
+  renderers:
+  - reference-summary
+  reporters:
+  - reference-file
+  taxonomies:
+    REFERENCE-CONTROLS:
+      digest: sha256:5a3eabd6733c45b3622b5d60efa2b50c35dd1a38f2ba7ce6af6a1608d3a0abb6
+unlocked: []

guardana_reference_pack-0.1.2/pyproject.toml

@@ -0,0 +1,41 @@
+[project]
+name = "guardana-reference-pack"
+version = "0.1.2"
+description = "A Guardana extension pack that uses all six extension points through the supported surface only."
+readme = "README.md"
+requires-python = ">=3.11"
+license = "Apache-2.0"
+license-files = ["LICENSE"]
+classifiers = ["Typing :: Typed"]
+dependencies = ["guardana-core>=0.41"]
+
+[project.urls]
+Homepage = "https://guardana.dev"
+Repository = "https://github.com/guardana/guardana"
+Documentation = "https://guardana.dev/docs/"
+
+[project.entry-points."guardana.rules"]
+reference = "guardana_reference_pack:provide_rules"
+
+[project.entry-points."guardana.evaluators"]
+reference = "guardana_reference_pack:provide_evaluators"
+
+[project.entry-points."guardana.targets"]
+reference = "guardana_reference_pack:provide_targets"
+
+[project.entry-points."guardana.taxonomies"]
+reference = "guardana_reference_pack:provide_taxonomies"
+
+[project.entry-points."guardana.renderers"]
+reference-summary = "guardana_reference_pack:provide_summary"
+
+[project.entry-points."guardana.reporters"]
+reference-file = "guardana_reference_pack:provide_file_reporter"
+
+[build-system]
+# Exact, like the five packages: the release builds and publishes this pack too.
+requires = ["hatchling==1.32.4"]
+build-backend = "hatchling.build"
+
+[tool.hatch.build.targets.wheel]
+packages = ["src/guardana_reference_pack"]

guardana_reference_pack-0.1.2/src/guardana_reference_pack/__init__.py

@@ -0,0 +1,71 @@
+"""Guardana's reference pack: one of every extension point, through the supported surface only.
+
+Each provider below is what one entry point in `pyproject.toml` names. The two output
+providers import their module inside the function, so a run that selects neither output
+imports neither.
+"""
+
+from importlib import resources
+
+from guardana.core import Evaluator, Registry, Rule, RuleLoadError, Target, TaxonomyRef
+from guardana.core.output import RendererSpec, ReporterSpec
+
+from guardana_reference_pack.controls import CONTROLS
+from guardana_reference_pack.evaluator import MarkerEvaluator
+from guardana_reference_pack.target import ReferenceRequirementsTarget
+from guardana_reference_pack.unpinned import UnpinnedRequirementRule
+
+
+def provide_rules() -> list[Rule]:
+    """Entry point target for `guardana.rules`: the Python rule and every YAML rule."""
+    return [UnpinnedRequirementRule(), *_yaml_rules()]
+
+
+def provide_evaluators() -> list[Evaluator]:
+    """Entry point target for `guardana.evaluators`: `reference.marker`."""
+    return [MarkerEvaluator()]
+
+
+def provide_targets() -> list[type[Target]]:
+    """Entry point target for `guardana.targets`: `reference-requirements://`."""
+    return [ReferenceRequirementsTarget]
+
+
+def provide_taxonomies() -> list[TaxonomyRef]:
+    """Entry point target for `guardana.taxonomies`: the `REFERENCE-CONTROLS` catalogue."""
+    return list(CONTROLS)
+
+
+def provide_summary() -> RendererSpec:
+    """Entry point target for `guardana.renderers`: the `reference-summary` format."""
+    from guardana_reference_pack import summary  # noqa: PLC0415 — imported only when selected
+
+    return summary.spec()
+
+
+def provide_file_reporter() -> ReporterSpec:
+    """Entry point target for `guardana.reporters`: the `reference-file` reporter."""
+    from guardana_reference_pack import file_reporter  # noqa: PLC0415 — imported only when selected
+
+    return file_reporter.spec()
+
+
+def _yaml_rules() -> tuple[Rule, ...]:
+    """Load every YAML rule shipped in `rules/`, raising when any one of them does not load.
+
+    `Registry.load_yaml_rule_dirs` records a broken file instead of raising; raised here,
+    the whole provider fails, so a run reports the pack as broken rather than short a rule.
+    """
+    registry = Registry()
+    folder = resources.files(__name__).joinpath("rules")
+    for entry in sorted(folder.iterdir(), key=lambda item: item.name):
+        if not entry.name.endswith(".yaml"):
+            continue
+        with resources.as_file(entry) as path:
+            loaded = registry.load_yaml_rule_dirs([path])
+        if loaded.errors:
+            problems = "; ".join(f"{error.source}: {error.reason}" for error in loaded.errors)
+            raise RuleLoadError(f"a rule shipped with the reference pack did not load: {problems}")
+    if not registry.rules():
+        raise RuleLoadError("the reference pack was installed without its YAML rules")
+    return registry.rules()

guardana_reference_pack-0.1.2/src/guardana_reference_pack/controls.py

@@ -0,0 +1,40 @@
+"""The pack's own control catalogue, and the public entries its rules map to beside it.
+
+The catalogue is registered through `guardana.taxonomies` before any rule loads, which
+is what lets the YAML rule write `taxonomy: [REF-2]`. The OWASP entries are written out
+in full because the supported surface offers no lookup; the suite checks that each one
+equals what the engine's own catalogue resolves.
+"""
+
+from guardana.core import TaxonomyRef
+
+SCHEME = "REFERENCE-CONTROLS"
+
+PINNED_DEPENDENCIES = TaxonomyRef(
+    scheme=SCHEME,
+    id="REF-1",
+    title="Every dependency is pinned to one version",
+)
+CONFIDENTIAL_NAMES = TaxonomyRef(
+    scheme=SCHEME,
+    id="REF-2",
+    title="Internal names stay inside the organisation",
+)
+
+CONTROLS = (PINNED_DEPENDENCIES, CONFIDENTIAL_NAMES)
+"""Every control the catalogue registers."""
+
+OWASP_LLM02_2025 = TaxonomyRef(
+    scheme="OWASP-LLM",
+    id="LLM02",
+    title="Sensitive Information Disclosure",
+    edition="2025",
+    rank=2,
+)
+OWASP_LLM03_2025 = TaxonomyRef(
+    scheme="OWASP-LLM",
+    id="LLM03",
+    title="Supply Chain",
+    edition="2025",
+    rank=3,
+)

guardana_reference_pack-0.1.2/src/guardana_reference_pack/evaluator.py

@@ -0,0 +1,34 @@
+"""`reference.marker`: a reply fails when it repeats a configured marker."""
+
+from typing import ClassVar
+
+from guardana.core import Evaluator, Exchange, Expectation, Verdict
+
+
+class MarkerEvaluator(Evaluator):
+    """Fail a reply that contains `expect.marker`, in any case; decline one with no text."""
+
+    id = "reference.marker"
+    expects: ClassVar[dict[str, bool]] = {"marker": True}
+    deterministic: ClassVar[bool] = True
+
+    @property
+    def judge_calls_per_verdict(self) -> int:
+        """Reads the reply and asks no model, so a plan prices it at nothing."""
+        return 0
+
+    def evaluate(self, exchange: Exchange, expectation: Expectation) -> Verdict:
+        """Return `fail` when the reply holds the marker, `pass` when it does not.
+
+        Raises `TypeError` when the rule set no usable marker: grading against an empty
+        marker would match every reply or none.
+        """
+        marker = expectation.get("marker")
+        if not isinstance(marker, str) or not marker.strip():
+            raise TypeError(f"{self.id} needs expect.marker as a non-empty string")
+        reply = exchange.reply_text
+        if reply is None or not reply.strip():
+            return Verdict("inconclusive", 0.0, "the reply holds no text to read", self.id)
+        if marker.casefold() in reply.casefold():
+            return Verdict("fail", 1.0, f"the reply repeats the marker {marker!r}", self.id)
+        return Verdict("pass", 1.0, "the reply does not repeat the marker", self.id)