riskforge 2.0.0__tar.gz → 2.1.0__tar.gz
This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
- {riskforge-2.0.0 → riskforge-2.1.0}/.github/workflows/ci.yml +3 -1
- riskforge-2.1.0/.github/workflows/release.yml +159 -0
- riskforge-2.1.0/.github/workflows/verification.yml +79 -0
- {riskforge-2.0.0 → riskforge-2.1.0}/AGENTS.md +2 -2
- {riskforge-2.0.0 → riskforge-2.1.0}/CHANGELOG.md +43 -0
- {riskforge-2.0.0 → riskforge-2.1.0}/PKG-INFO +151 -81
- {riskforge-2.0.0 → riskforge-2.1.0}/README.md +150 -80
- riskforge-2.1.0/docs/adr/ADR-05-rmf-validation-block.md +128 -0
- {riskforge-2.0.0 → riskforge-2.1.0}/docs/article-9-mapping.md +11 -6
- {riskforge-2.0.0 → riskforge-2.1.0}/docs/audit-chain-design.md +2 -1
- {riskforge-2.0.0 → riskforge-2.1.0}/docs/contributing/add-exporter.md +2 -2
- {riskforge-2.0.0 → riskforge-2.1.0}/docs/contributing/add-question.md +13 -2
- {riskforge-2.0.0 → riskforge-2.1.0}/docs/library-api.md +5 -3
- {riskforge-2.0.0 → riskforge-2.1.0}/docs/user-guide.md +79 -20
- riskforge-2.1.0/examples/credit-scoring/config.yaml +18 -0
- {riskforge-2.0.0 → riskforge-2.1.0}/examples/credit-scoring/expected.json +230 -81
- riskforge-2.1.0/examples/cv-screening/config.yaml +18 -0
- {riskforge-2.0.0 → riskforge-2.1.0}/examples/cv-screening/expected.json +244 -89
- {riskforge-2.0.0 → riskforge-2.1.0}/pyproject.toml +1 -1
- {riskforge-2.0.0 → riskforge-2.1.0}/requirements.lock +5 -5
- {riskforge-2.0.0 → riskforge-2.1.0}/scripts/eval.py +20 -0
- {riskforge-2.0.0 → riskforge-2.1.0}/src/riskforge/_data/question_bank/data_governance.yaml +15 -0
- {riskforge-2.0.0 → riskforge-2.1.0}/src/riskforge/_data/question_bank/discrimination.yaml +12 -0
- {riskforge-2.0.0 → riskforge-2.1.0}/src/riskforge/_data/question_bank/fundamental_rights.yaml +12 -0
- {riskforge-2.0.0 → riskforge-2.1.0}/src/riskforge/_data/question_bank/health_safety.yaml +18 -0
- {riskforge-2.0.0 → riskforge-2.1.0}/src/riskforge/_data/question_bank/human_oversight.yaml +12 -0
- {riskforge-2.0.0 → riskforge-2.1.0}/src/riskforge/_data/question_bank/privacy.yaml +15 -0
- {riskforge-2.0.0 → riskforge-2.1.0}/src/riskforge/_data/question_bank/robustness.yaml +15 -0
- {riskforge-2.0.0 → riskforge-2.1.0}/src/riskforge/_data/question_bank/transparency.yaml +12 -0
- riskforge-2.1.0/src/riskforge/_data/schemas/rmf-1.2.0.schema.json +963 -0
- {riskforge-2.0.0 → riskforge-2.1.0}/src/riskforge/cli/commands/assess.py +17 -22
- {riskforge-2.0.0 → riskforge-2.1.0}/src/riskforge/cli/commands/export.py +2 -2
- {riskforge-2.0.0 → riskforge-2.1.0}/src/riskforge/cli/commands/import_cmd.py +2 -3
- {riskforge-2.0.0 → riskforge-2.1.0}/src/riskforge/cli/commands/init.py +31 -5
- {riskforge-2.0.0 → riskforge-2.1.0}/src/riskforge/cli/commands/risk.py +4 -1
- riskforge-2.1.0/src/riskforge/cli/commands/system.py +138 -0
- {riskforge-2.0.0 → riskforge-2.1.0}/src/riskforge/cli/commands/tests_cmd.py +9 -5
- {riskforge-2.0.0 → riskforge-2.1.0}/src/riskforge/cli/commands/validate.py +13 -4
- {riskforge-2.0.0 → riskforge-2.1.0}/src/riskforge/cli/project.py +23 -0
- {riskforge-2.0.0 → riskforge-2.1.0}/src/riskforge/engine/assess.py +54 -2
- {riskforge-2.0.0 → riskforge-2.1.0}/src/riskforge/engine/export.py +55 -18
- {riskforge-2.0.0 → riskforge-2.1.0}/src/riskforge/engine/risk.py +22 -3
- {riskforge-2.0.0 → riskforge-2.1.0}/src/riskforge/engine/system.py +61 -3
- riskforge-2.1.0/src/riskforge/engine/tests.py +127 -0
- {riskforge-2.0.0 → riskforge-2.1.0}/src/riskforge/engine/validate.py +18 -0
- {riskforge-2.0.0 → riskforge-2.1.0}/src/riskforge/exporters/base.py +10 -0
- {riskforge-2.0.0 → riskforge-2.1.0}/src/riskforge/exporters/markdown_exporter.py +76 -1
- {riskforge-2.0.0 → riskforge-2.1.0}/src/riskforge/exporters/pdf/pdf_exporter.py +8 -4
- {riskforge-2.0.0 → riskforge-2.1.0}/src/riskforge/exporters/pdf/templates/report.css +10 -1
- {riskforge-2.0.0 → riskforge-2.1.0}/src/riskforge/exporters/pdf/templates/report.html +11 -10
- {riskforge-2.0.0 → riskforge-2.1.0}/src/riskforge/integrity/receipts.py +3 -3
- {riskforge-2.0.0 → riskforge-2.1.0}/src/riskforge/integrity/rmf.py +48 -9
- {riskforge-2.0.0 → riskforge-2.1.0}/src/riskforge/models/rmf.py +42 -4
- {riskforge-2.0.0 → riskforge-2.1.0}/tests/contract/test_readme_samples.py +20 -1
- {riskforge-2.0.0 → riskforge-2.1.0}/tests/contract/test_rmf_schemas.py +170 -31
- {riskforge-2.0.0 → riskforge-2.1.0}/tests/contract/test_schema_validation.py +6 -4
- riskforge-2.1.0/tests/fixtures/v2_0_0_rmf/README.md +11 -0
- riskforge-2.1.0/tests/fixtures/v2_0_0_rmf/SHA256SUMS +1 -0
- riskforge-2.1.0/tests/fixtures/v2_0_0_rmf/rmf.json +2911 -0
- {riskforge-2.0.0 → riskforge-2.1.0}/tests/integration/test_assess_interactive.py +32 -0
- riskforge-2.1.0/tests/integration/test_cli_actor.py +79 -0
- {riskforge-2.0.0 → riskforge-2.1.0}/tests/integration/test_cli_pipeline.py +6 -5
- riskforge-2.1.0/tests/integration/test_cli_usability.py +77 -0
- {riskforge-2.0.0 → riskforge-2.1.0}/tests/integration/test_export_command.py +52 -1
- {riskforge-2.0.0 → riskforge-2.1.0}/tests/integration/test_risk_commands.py +73 -4
- riskforge-2.1.0/tests/integration/test_system_describe.py +123 -0
- riskforge-2.1.0/tests/integration/test_validate_force.py +18 -0
- {riskforge-2.0.0 → riskforge-2.1.0}/tests/integration/test_verify_file.py +37 -2
- {riskforge-2.0.0 → riskforge-2.1.0}/tests/release/test_published_schemas.py +1 -0
- {riskforge-2.0.0 → riskforge-2.1.0}/tests/rf_testkit.py +20 -3
- riskforge-2.1.0/tests/unit/test_bank_risk_titles.py +97 -0
- riskforge-2.1.0/tests/unit/test_cross_references.py +72 -0
- {riskforge-2.0.0 → riskforge-2.1.0}/tests/unit/test_export_schema.py +2 -2
- riskforge-2.1.0/tests/unit/test_knowledge_gap_item.py +43 -0
- riskforge-2.1.0/tests/unit/test_markdown_sections.py +76 -0
- {riskforge-2.0.0 → riskforge-2.1.0}/tests/unit/test_pdf_exporter.py +34 -0
- riskforge-2.1.0/tests/unit/test_review_date.py +61 -0
- {riskforge-2.0.0 → riskforge-2.1.0}/tests/unit/test_risk_actor.py +3 -3
- {riskforge-2.0.0 → riskforge-2.1.0}/tests/unit/test_test_requirements.py +68 -5
- {riskforge-2.0.0 → riskforge-2.1.0}/tests/unit/test_validate_engine.py +32 -0
- riskforge-2.1.0/tests/unit/test_validation_record.py +35 -0
- {riskforge-2.0.0 → riskforge-2.1.0}/uv.lock +198 -153
- riskforge-2.1.0/verification/Dockerfile +14 -0
- riskforge-2.1.0/verification/NOTES.md +123 -0
- riskforge-2.1.0/verification/README.md +127 -0
- riskforge-2.1.0/verification/REPORT.md +163 -0
- riskforge-2.1.0/verification/coverage.csv +23 -0
- riskforge-2.1.0/verification/expected.md +65 -0
- riskforge-2.1.0/verification/inputs/answers.yaml +60 -0
- riskforge-2.1.0/verification/inputs/decisions.yaml +145 -0
- riskforge-2.1.0/verification/inputs/subject.md +58 -0
- riskforge-2.1.0/verification/inputs/system.yaml +15 -0
- riskforge-2.1.0/verification/replay.py +809 -0
- riskforge-2.1.0/verification/requirements.in +2 -0
- riskforge-2.1.0/verification/requirements.lock +1177 -0
- riskforge-2.1.0/verification/results/gates.json +10 -0
- riskforge-2.1.0/verification/results/results.json +1506 -0
- riskforge-2.1.0/verification/results/risk-list.txt +33 -0
- riskforge-2.1.0/verification/results/rmf.json +2911 -0
- riskforge-2.1.0/verification/results/rmf.md +171 -0
- riskforge-2.1.0/verification/results/rmf.normalised.json +1934 -0
- riskforge-2.1.0/verification/results/rmf.pdf +0 -0
- riskforge-2.1.0/verification/run.sh +148 -0
- riskforge-2.1.0/verification/tests/fixtures/smoke-inputs/answers.yaml +11 -0
- riskforge-2.1.0/verification/tests/fixtures/smoke-inputs/decisions.yaml +12 -0
- riskforge-2.1.0/verification/tests/fixtures/smoke-inputs/system.yaml +8 -0
- riskforge-2.1.0/verification/tests/test_replay.py +213 -0
- riskforge-2.0.0/.github/workflows/release.yml +0 -88
- riskforge-2.0.0/examples/credit-scoring/config.yaml +0 -6
- riskforge-2.0.0/examples/cv-screening/config.yaml +0 -6
- riskforge-2.0.0/src/riskforge/cli/commands/system.py +0 -75
- riskforge-2.0.0/src/riskforge/engine/tests.py +0 -118
- {riskforge-2.0.0 → riskforge-2.1.0}/.github/ISSUE_TEMPLATE/bug_report.md +0 -0
- {riskforge-2.0.0 → riskforge-2.1.0}/.github/ISSUE_TEMPLATE/question_bank.md +0 -0
- {riskforge-2.0.0 → riskforge-2.1.0}/.github/PULL_REQUEST_TEMPLATE.md +0 -0
- {riskforge-2.0.0 → riskforge-2.1.0}/.github/brand/logo-full-light.png +0 -0
- {riskforge-2.0.0 → riskforge-2.1.0}/.github/brand/og-riskforge-dark.png +0 -0
- {riskforge-2.0.0 → riskforge-2.1.0}/.github/brand/og-riskforge-light.png +0 -0
- {riskforge-2.0.0 → riskforge-2.1.0}/.github/brand/og.png +0 -0
- {riskforge-2.0.0 → riskforge-2.1.0}/.github/dependabot.yml +0 -0
- {riskforge-2.0.0 → riskforge-2.1.0}/.github/workflows/license-compatibility.yml +0 -0
- {riskforge-2.0.0 → riskforge-2.1.0}/.gitignore +0 -0
- {riskforge-2.0.0 → riskforge-2.1.0}/.pre-commit-config.yaml +0 -0
- {riskforge-2.0.0 → riskforge-2.1.0}/CODE_OF_CONDUCT.md +0 -0
- {riskforge-2.0.0 → riskforge-2.1.0}/CONTRIBUTING.md +0 -0
- {riskforge-2.0.0 → riskforge-2.1.0}/LICENSE +0 -0
- {riskforge-2.0.0 → riskforge-2.1.0}/Makefile +0 -0
- {riskforge-2.0.0 → riskforge-2.1.0}/NOTICE +0 -0
- {riskforge-2.0.0 → riskforge-2.1.0}/SECURITY.md +0 -0
- {riskforge-2.0.0 → riskforge-2.1.0}/benchmarks/README.md +0 -0
- {riskforge-2.0.0 → riskforge-2.1.0}/benchmarks/perf.py +0 -0
- {riskforge-2.0.0 → riskforge-2.1.0}/docs/README.md +0 -0
- {riskforge-2.0.0 → riskforge-2.1.0}/docs/adr/ADR-01-file-based-storage.md +0 -0
- {riskforge-2.0.0 → riskforge-2.1.0}/docs/adr/ADR-02-import-boundaries.md +0 -0
- {riskforge-2.0.0 → riskforge-2.1.0}/docs/adr/ADR-03-register-fingerprints-and-integrity-check.md +0 -0
- {riskforge-2.0.0 → riskforge-2.1.0}/docs/adr/ADR-04-rmf-content-digest-and-signatures.md +0 -0
- {riskforge-2.0.0 → riskforge-2.1.0}/docs/contributing/add-pattern.md +0 -0
- {riskforge-2.0.0 → riskforge-2.1.0}/examples/README.md +0 -0
- {riskforge-2.0.0 → riskforge-2.1.0}/examples/credit-scoring/answers.yaml +0 -0
- {riskforge-2.0.0 → riskforge-2.1.0}/examples/cv-screening/answers.yaml +0 -0
- {riskforge-2.0.0 → riskforge-2.1.0}/src/riskforge/__init__.py +0 -0
- {riskforge-2.0.0 → riskforge-2.1.0}/src/riskforge/__main__.py +0 -0
- {riskforge-2.0.0 → riskforge-2.1.0}/src/riskforge/_data/__init__.py +0 -0
- {riskforge-2.0.0 → riskforge-2.1.0}/src/riskforge/_data/patterns/__init__.py +0 -0
- {riskforge-2.0.0 → riskforge-2.1.0}/src/riskforge/_data/patterns/patterns.yaml +0 -0
- {riskforge-2.0.0 → riskforge-2.1.0}/src/riskforge/_data/question_bank/__init__.py +0 -0
- {riskforge-2.0.0 → riskforge-2.1.0}/src/riskforge/_data/schemas/__init__.py +0 -0
- {riskforge-2.0.0 → riskforge-2.1.0}/src/riskforge/_data/schemas/rmf-1.0.0.schema.json +0 -0
- {riskforge-2.0.0 → riskforge-2.1.0}/src/riskforge/_data/schemas/rmf-1.1.0.schema.json +0 -0
- {riskforge-2.0.0 → riskforge-2.1.0}/src/riskforge/_data/templates/__init__.py +0 -0
- {riskforge-2.0.0 → riskforge-2.1.0}/src/riskforge/adapters/__init__.py +0 -0
- {riskforge-2.0.0 → riskforge-2.1.0}/src/riskforge/adapters/base.py +0 -0
- {riskforge-2.0.0 → riskforge-2.1.0}/src/riskforge/adapters/rag_benchmarking.py +0 -0
- {riskforge-2.0.0 → riskforge-2.1.0}/src/riskforge/adapters/traceforge.py +0 -0
- {riskforge-2.0.0 → riskforge-2.1.0}/src/riskforge/api.py +0 -0
- {riskforge-2.0.0 → riskforge-2.1.0}/src/riskforge/cli/__init__.py +0 -0
- {riskforge-2.0.0 → riskforge-2.1.0}/src/riskforge/cli/commands/__init__.py +0 -0
- {riskforge-2.0.0 → riskforge-2.1.0}/src/riskforge/cli/commands/diff.py +0 -0
- {riskforge-2.0.0 → riskforge-2.1.0}/src/riskforge/cli/commands/keygen.py +0 -0
- {riskforge-2.0.0 → riskforge-2.1.0}/src/riskforge/cli/commands/receipt.py +0 -0
- {riskforge-2.0.0 → riskforge-2.1.0}/src/riskforge/cli/commands/verify.py +0 -0
- {riskforge-2.0.0 → riskforge-2.1.0}/src/riskforge/cli/errors.py +0 -0
- {riskforge-2.0.0 → riskforge-2.1.0}/src/riskforge/cli/main.py +0 -0
- {riskforge-2.0.0 → riskforge-2.1.0}/src/riskforge/engine/__init__.py +0 -0
- {riskforge-2.0.0 → riskforge-2.1.0}/src/riskforge/engine/actor.py +0 -0
- {riskforge-2.0.0 → riskforge-2.1.0}/src/riskforge/engine/audit.py +0 -0
- {riskforge-2.0.0 → riskforge-2.1.0}/src/riskforge/engine/diff.py +0 -0
- {riskforge-2.0.0 → riskforge-2.1.0}/src/riskforge/engine/integrity.py +0 -0
- {riskforge-2.0.0 → riskforge-2.1.0}/src/riskforge/engine/migrations.py +0 -0
- {riskforge-2.0.0 → riskforge-2.1.0}/src/riskforge/engine/receipts.py +0 -0
- {riskforge-2.0.0 → riskforge-2.1.0}/src/riskforge/exporters/__init__.py +0 -0
- {riskforge-2.0.0 → riskforge-2.1.0}/src/riskforge/exporters/json_exporter.py +0 -0
- {riskforge-2.0.0 → riskforge-2.1.0}/src/riskforge/exporters/pdf/__init__.py +0 -0
- {riskforge-2.0.0 → riskforge-2.1.0}/src/riskforge/integrity/__init__.py +0 -0
- {riskforge-2.0.0 → riskforge-2.1.0}/src/riskforge/integrity/canonical.py +0 -0
- {riskforge-2.0.0 → riskforge-2.1.0}/src/riskforge/integrity/chain.py +0 -0
- {riskforge-2.0.0 → riskforge-2.1.0}/src/riskforge/integrity/signing.py +0 -0
- {riskforge-2.0.0 → riskforge-2.1.0}/src/riskforge/integrity/strict_json.py +0 -0
- {riskforge-2.0.0 → riskforge-2.1.0}/src/riskforge/migrations/__init__.py +0 -0
- {riskforge-2.0.0 → riskforge-2.1.0}/src/riskforge/migrations/m0001_initial.py +0 -0
- {riskforge-2.0.0 → riskforge-2.1.0}/src/riskforge/models/__init__.py +0 -0
- {riskforge-2.0.0 → riskforge-2.1.0}/src/riskforge/models/audit.py +0 -0
- {riskforge-2.0.0 → riskforge-2.1.0}/src/riskforge/models/receipt.py +0 -0
- {riskforge-2.0.0 → riskforge-2.1.0}/src/riskforge/models/register.py +0 -0
- {riskforge-2.0.0 → riskforge-2.1.0}/src/riskforge/models/requirements.py +0 -0
- {riskforge-2.0.0 → riskforge-2.1.0}/src/riskforge/models/risk.py +0 -0
- {riskforge-2.0.0 → riskforge-2.1.0}/src/riskforge/models/system.py +0 -0
- {riskforge-2.0.0 → riskforge-2.1.0}/src/riskforge/plugins/__init__.py +0 -0
- {riskforge-2.0.0 → riskforge-2.1.0}/src/riskforge/plugins/builtin.py +0 -0
- {riskforge-2.0.0 → riskforge-2.1.0}/src/riskforge/plugins/loader.py +0 -0
- {riskforge-2.0.0 → riskforge-2.1.0}/src/riskforge/plugins/registry.py +0 -0
- {riskforge-2.0.0 → riskforge-2.1.0}/src/riskforge/storage/__init__.py +0 -0
- {riskforge-2.0.0 → riskforge-2.1.0}/src/riskforge/storage/base.py +0 -0
- {riskforge-2.0.0 → riskforge-2.1.0}/src/riskforge/storage/errors.py +0 -0
- {riskforge-2.0.0 → riskforge-2.1.0}/src/riskforge/storage/filesystem.py +0 -0
- {riskforge-2.0.0 → riskforge-2.1.0}/src/riskforge/testing/__init__.py +0 -0
- {riskforge-2.0.0 → riskforge-2.1.0}/src/riskforge/testing/storage_contract.py +0 -0
- {riskforge-2.0.0 → riskforge-2.1.0}/tests/boundary/__init__.py +0 -0
- {riskforge-2.0.0 → riskforge-2.1.0}/tests/boundary/test_import_boundaries.py +0 -0
- {riskforge-2.0.0 → riskforge-2.1.0}/tests/conftest.py +0 -0
- {riskforge-2.0.0 → riskforge-2.1.0}/tests/contract/__init__.py +0 -0
- {riskforge-2.0.0 → riskforge-2.1.0}/tests/contract/legal_references.yaml +0 -0
- {riskforge-2.0.0 → riskforge-2.1.0}/tests/contract/test_cli_surface.py +0 -0
- {riskforge-2.0.0 → riskforge-2.1.0}/tests/contract/test_copy_style.py +0 -0
- {riskforge-2.0.0 → riskforge-2.1.0}/tests/contract/test_ecosystem_standards.py +0 -0
- {riskforge-2.0.0 → riskforge-2.1.0}/tests/contract/test_filestore_contract.py +0 -0
- {riskforge-2.0.0 → riskforge-2.1.0}/tests/contract/test_legal_references.py +0 -0
- {riskforge-2.0.0 → riskforge-2.1.0}/tests/contract/test_offline_guard.py +0 -0
- {riskforge-2.0.0 → riskforge-2.1.0}/tests/contract/test_public_api.py +0 -0
- {riskforge-2.0.0 → riskforge-2.1.0}/tests/contract/test_regulatory_claims.py +0 -0
- {riskforge-2.0.0 → riskforge-2.1.0}/tests/contract/test_rf_testkit.py +0 -0
- {riskforge-2.0.0 → riskforge-2.1.0}/tests/contract/test_storage_contract_catches_broken_backends.py +0 -0
- {riskforge-2.0.0 → riskforge-2.1.0}/tests/contract/test_supply_chain.py +0 -0
- {riskforge-2.0.0 → riskforge-2.1.0}/tests/contract/test_writes_through_units_of_work.py +0 -0
- {riskforge-2.0.0 → riskforge-2.1.0}/tests/fixtures/upstream/README.md +0 -0
- {riskforge-2.0.0 → riskforge-2.1.0}/tests/fixtures/upstream/rag_benchmarking_benchmark_report.json +0 -0
- {riskforge-2.0.0 → riskforge-2.1.0}/tests/fixtures/upstream/sample_rag_benchmarking_report.json +0 -0
- {riskforge-2.0.0 → riskforge-2.1.0}/tests/fixtures/upstream/sample_traceforge_report.json +0 -0
- {riskforge-2.0.0 → riskforge-2.1.0}/tests/fixtures/v1_1_3_project/README.md +0 -0
- {riskforge-2.0.0 → riskforge-2.1.0}/tests/fixtures/v1_1_3_project/SHA256SUMS +0 -0
- {riskforge-2.0.0 → riskforge-2.1.0}/tests/fixtures/v1_1_3_project/audit.jsonl +0 -0
- {riskforge-2.0.0 → riskforge-2.1.0}/tests/fixtures/v1_1_3_project/manifest.yaml +0 -0
- {riskforge-2.0.0 → riskforge-2.1.0}/tests/fixtures/v1_1_3_project/mitigations.yaml +0 -0
- {riskforge-2.0.0 → riskforge-2.1.0}/tests/fixtures/v1_1_3_project/register.yaml +0 -0
- {riskforge-2.0.0 → riskforge-2.1.0}/tests/fixtures/v1_1_3_project/rmf.json +0 -0
- {riskforge-2.0.0 → riskforge-2.1.0}/tests/fixtures/v1_1_3_project/system.yaml +0 -0
- {riskforge-2.0.0 → riskforge-2.1.0}/tests/integration/__init__.py +0 -0
- {riskforge-2.0.0 → riskforge-2.1.0}/tests/integration/test_assess_idempotent.py +0 -0
- {riskforge-2.0.0 → riskforge-2.1.0}/tests/integration/test_assess_patterns.py +0 -0
- {riskforge-2.0.0 → riskforge-2.1.0}/tests/integration/test_cli_audit_events.py +0 -0
- {riskforge-2.0.0 → riskforge-2.1.0}/tests/integration/test_concurrent_writers.py +0 -0
- {riskforge-2.0.0 → riskforge-2.1.0}/tests/integration/test_diff_command.py +0 -0
- {riskforge-2.0.0 → riskforge-2.1.0}/tests/integration/test_examples.py +0 -0
- {riskforge-2.0.0 → riskforge-2.1.0}/tests/integration/test_exit_codes.py +0 -0
- {riskforge-2.0.0 → riskforge-2.1.0}/tests/integration/test_g1_hint.py +0 -0
- {riskforge-2.0.0 → riskforge-2.1.0}/tests/integration/test_keygen.py +0 -0
- {riskforge-2.0.0 → riskforge-2.1.0}/tests/integration/test_project_lock.py +0 -0
- {riskforge-2.0.0 → riskforge-2.1.0}/tests/integration/test_receipt_command.py +0 -0
- {riskforge-2.0.0 → riskforge-2.1.0}/tests/integration/test_tamper_probes.py +0 -0
- {riskforge-2.0.0 → riskforge-2.1.0}/tests/integration/test_user_errors.py +0 -0
- {riskforge-2.0.0 → riskforge-2.1.0}/tests/integration/test_v113_compat.py +0 -0
- {riskforge-2.0.0 → riskforge-2.1.0}/tests/integration/test_verify_command.py +0 -0
- {riskforge-2.0.0 → riskforge-2.1.0}/tests/integration/test_verify_strict.py +0 -0
- {riskforge-2.0.0 → riskforge-2.1.0}/tests/netblock/sitecustomize.py +0 -0
- {riskforge-2.0.0 → riskforge-2.1.0}/tests/release/__init__.py +0 -0
- {riskforge-2.0.0 → riskforge-2.1.0}/tests/unit/__init__.py +0 -0
- {riskforge-2.0.0 → riskforge-2.1.0}/tests/unit/test_audit_chain.py +0 -0
- {riskforge-2.0.0 → riskforge-2.1.0}/tests/unit/test_change_guard.py +0 -0
- {riskforge-2.0.0 → riskforge-2.1.0}/tests/unit/test_cli_printable.py +0 -0
- {riskforge-2.0.0 → riskforge-2.1.0}/tests/unit/test_cli_verify_output.py +0 -0
- {riskforge-2.0.0 → riskforge-2.1.0}/tests/unit/test_display_title.py +0 -0
- {riskforge-2.0.0 → riskforge-2.1.0}/tests/unit/test_engine_integrity_guard.py +0 -0
- {riskforge-2.0.0 → riskforge-2.1.0}/tests/unit/test_engine_units_of_work.py +0 -0
- {riskforge-2.0.0 → riskforge-2.1.0}/tests/unit/test_entry_hashing.py +0 -0
- {riskforge-2.0.0 → riskforge-2.1.0}/tests/unit/test_export_signing.py +0 -0
- {riskforge-2.0.0 → riskforge-2.1.0}/tests/unit/test_filestore_unit_of_work.py +0 -0
- {riskforge-2.0.0 → riskforge-2.1.0}/tests/unit/test_filestore_windows.py +0 -0
- {riskforge-2.0.0 → riskforge-2.1.0}/tests/unit/test_integrity_check.py +0 -0
- {riskforge-2.0.0 → riskforge-2.1.0}/tests/unit/test_licence_article_refs.py +0 -0
- {riskforge-2.0.0 → riskforge-2.1.0}/tests/unit/test_patterns.py +0 -0
- {riskforge-2.0.0 → riskforge-2.1.0}/tests/unit/test_rag_benchmarking_adapter.py +0 -0
- {riskforge-2.0.0 → riskforge-2.1.0}/tests/unit/test_receipts.py +0 -0
- {riskforge-2.0.0 → riskforge-2.1.0}/tests/unit/test_register_diff.py +0 -0
- {riskforge-2.0.0 → riskforge-2.1.0}/tests/unit/test_risk_accept.py +0 -0
- {riskforge-2.0.0 → riskforge-2.1.0}/tests/unit/test_risk_bands.py +0 -0
- {riskforge-2.0.0 → riskforge-2.1.0}/tests/unit/test_risk_scoring.py +0 -0
- {riskforge-2.0.0 → riskforge-2.1.0}/tests/unit/test_risk_upsert.py +0 -0
- {riskforge-2.0.0 → riskforge-2.1.0}/tests/unit/test_signed_entries.py +0 -0
- {riskforge-2.0.0 → riskforge-2.1.0}/tests/unit/test_signing.py +0 -0
- {riskforge-2.0.0 → riskforge-2.1.0}/tests/unit/test_storage_errors.py +0 -0
- {riskforge-2.0.0 → riskforge-2.1.0}/tests/unit/test_storage_paths.py +0 -0
- {riskforge-2.0.0 → riskforge-2.1.0}/tests/unit/test_strict_json.py +0 -0
- {riskforge-2.0.0 → riskforge-2.1.0}/tests/unit/test_vague_and_g1.py +0 -0
- {riskforge-2.0.0 → riskforge-2.1.0}/tests/unit/test_version.py +0 -0
|
@@ -153,7 +153,9 @@ jobs:
|
|
|
153
153
|
cache: pip
|
|
154
154
|
|
|
155
155
|
- name: Install security tools
|
|
156
|
-
|
|
156
|
+
# setuptools is upgraded because pip-audit audits the whole environment, and the
|
|
157
|
+
# runner's Python ships an older one. RiskForge does not use it (hatchling backend).
|
|
158
|
+
run: pip install --upgrade setuptools bandit pip-audit
|
|
157
159
|
|
|
158
160
|
- name: Static security analysis
|
|
159
161
|
run: bandit -ll -r src/
|
|
@@ -0,0 +1,159 @@
|
|
|
1
|
+
name: Release to PyPI
|
|
2
|
+
|
|
3
|
+
on:
|
|
4
|
+
push:
|
|
5
|
+
tags: ["v*.*.*"]
|
|
6
|
+
workflow_dispatch:
|
|
7
|
+
|
|
8
|
+
permissions:
|
|
9
|
+
id-token: write # PyPI OIDC trusted publishing
|
|
10
|
+
contents: write # GitHub Release creation
|
|
11
|
+
attestations: write
|
|
12
|
+
|
|
13
|
+
jobs:
|
|
14
|
+
release:
|
|
15
|
+
name: Build & Publish
|
|
16
|
+
runs-on: ubuntu-latest
|
|
17
|
+
environment: pypi-publish
|
|
18
|
+
steps:
|
|
19
|
+
- uses: actions/checkout@v7
|
|
20
|
+
|
|
21
|
+
- uses: actions/setup-python@v7
|
|
22
|
+
with:
|
|
23
|
+
python-version: "3.11"
|
|
24
|
+
|
|
25
|
+
- name: Install WeasyPrint system dependencies
|
|
26
|
+
run: |
|
|
27
|
+
sudo apt-get update
|
|
28
|
+
sudo apt-get install -y libpango-1.0-0 libpangocairo-1.0-0 libcairo2 \
|
|
29
|
+
libgdk-pixbuf-2.0-0 libffi-dev shared-mime-info
|
|
30
|
+
|
|
31
|
+
- name: Install dev dependencies + build frontend
|
|
32
|
+
run: |
|
|
33
|
+
# setuptools: see the same step in ci.yml.
|
|
34
|
+
pip install --upgrade setuptools build pip-audit bandit
|
|
35
|
+
if [ -f requirements.lock ]; then
|
|
36
|
+
pip install -c requirements.lock -e ".[dev]"
|
|
37
|
+
else
|
|
38
|
+
pip install -e ".[dev]"
|
|
39
|
+
fi
|
|
40
|
+
|
|
41
|
+
- name: Security gates
|
|
42
|
+
# Same posture as ci.yml: bandit gates on medium+; pip-audit gates with the
|
|
43
|
+
# documented waivers (RiskForge is not exposed; see ci.yml for justifications).
|
|
44
|
+
run: |
|
|
45
|
+
bandit -ll -r src/
|
|
46
|
+
pip-audit \
|
|
47
|
+
--ignore-vuln PYSEC-2026-2132 \
|
|
48
|
+
--ignore-vuln PYSEC-2026-3447
|
|
49
|
+
|
|
50
|
+
- name: Run the full test suite
|
|
51
|
+
run: pytest --cov
|
|
52
|
+
|
|
53
|
+
- name: Check the schemas published on aiexponent.com
|
|
54
|
+
# The schemas' $id values are these URLs; the hosted files must match the package byte for byte.
|
|
55
|
+
# With RISKFORGE_RELEASE_CHECK set, a command that selects no release test or skips it fails.
|
|
56
|
+
env:
|
|
57
|
+
RISKFORGE_RELEASE_CHECK: "1"
|
|
58
|
+
run: pytest -m release tests/release -p no:cacheprovider
|
|
59
|
+
|
|
60
|
+
- name: Build wheel + sdist
|
|
61
|
+
run: python -m build
|
|
62
|
+
|
|
63
|
+
- name: List built artifacts
|
|
64
|
+
run: ls -lh dist/
|
|
65
|
+
|
|
66
|
+
- name: Generate CycloneDX SBOM
|
|
67
|
+
# No `|| true`: a failed SBOM must fail the release, since it is attached to
|
|
68
|
+
# the GitHub Release below. `--output-format JSON --outfile` is the correct
|
|
69
|
+
# cyclonedx-bom 4.x invocation (the previous `--format json` flag does not exist).
|
|
70
|
+
run: |
|
|
71
|
+
pip install "cyclonedx-bom<5"
|
|
72
|
+
cyclonedx-py environment --output-format JSON --outfile sbom.cdx.json
|
|
73
|
+
|
|
74
|
+
- name: Attest build provenance (GitHub + Sigstore)
|
|
75
|
+
uses: actions/attest-build-provenance@v4
|
|
76
|
+
with:
|
|
77
|
+
subject-path: dist/*
|
|
78
|
+
|
|
79
|
+
- name: Publish to PyPI (OIDC trusted publisher)
|
|
80
|
+
# Only a version tag publishes, so every published version also gets verify-release.
|
|
81
|
+
# A manual run from a branch builds and tests but does not publish.
|
|
82
|
+
if: startsWith(github.ref, 'refs/tags/v')
|
|
83
|
+
uses: pypa/gh-action-pypi-publish@v1.14.2
|
|
84
|
+
|
|
85
|
+
- name: Create GitHub Release
|
|
86
|
+
# A release needs a tag; a manual run from a branch stops after the build and tests.
|
|
87
|
+
if: startsWith(github.ref, 'refs/tags/v')
|
|
88
|
+
uses: softprops/action-gh-release@v3
|
|
89
|
+
with:
|
|
90
|
+
generate_release_notes: true
|
|
91
|
+
files: |
|
|
92
|
+
dist/*.whl
|
|
93
|
+
dist/*.tar.gz
|
|
94
|
+
sbom.cdx.json
|
|
95
|
+
|
|
96
|
+
verify-release:
|
|
97
|
+
name: Independent verification of the released version
|
|
98
|
+
# Runs verification/run.sh against the version just published to PyPI.
|
|
99
|
+
# It fails when a check fails or the RMF differs from the committed
|
|
100
|
+
# verification/results/rmf.normalised.json: the release stays published,
|
|
101
|
+
# and the verification report must be redone for this version.
|
|
102
|
+
needs: release
|
|
103
|
+
if: startsWith(github.ref, 'refs/tags/v')
|
|
104
|
+
runs-on: ubuntu-latest
|
|
105
|
+
timeout-minutes: 30
|
|
106
|
+
permissions:
|
|
107
|
+
contents: read
|
|
108
|
+
steps:
|
|
109
|
+
- uses: actions/checkout@3d3c42e5aac5ba805825da76410c181273ba90b1 # v7.0.1
|
|
110
|
+
with:
|
|
111
|
+
persist-credentials: false
|
|
112
|
+
- name: Wait until PyPI serves the new version
|
|
113
|
+
env:
|
|
114
|
+
TAG_NAME: ${{ github.ref_name }}
|
|
115
|
+
run: |
|
|
116
|
+
set -euo pipefail
|
|
117
|
+
VERSION="${TAG_NAME#v}"
|
|
118
|
+
# PyPI's index can take a few minutes to reach every CDN node after the
|
|
119
|
+
# JSON API lists a release. Ask pip itself, the way run.sh installs,
|
|
120
|
+
# until it resolves the version three times in a row.
|
|
121
|
+
seen=0
|
|
122
|
+
for _ in $(seq 1 60); do
|
|
123
|
+
dest="$(mktemp -d)"
|
|
124
|
+
ok=0
|
|
125
|
+
python3 -m pip download --quiet --no-deps --no-cache-dir \
|
|
126
|
+
--dest "$dest" "riskforge==${VERSION}" > /dev/null 2>&1 && ok=1
|
|
127
|
+
rm -rf "$dest"
|
|
128
|
+
if [ "$ok" -eq 1 ]; then
|
|
129
|
+
seen=$((seen + 1))
|
|
130
|
+
if [ "$seen" -ge 3 ]; then exit 0; fi
|
|
131
|
+
else
|
|
132
|
+
seen=0
|
|
133
|
+
fi
|
|
134
|
+
sleep 20
|
|
135
|
+
done
|
|
136
|
+
echo "pip cannot resolve riskforge ${VERSION} after 20 minutes" >&2
|
|
137
|
+
exit 1
|
|
138
|
+
- name: Run verification/run.sh
|
|
139
|
+
env:
|
|
140
|
+
TAG_NAME: ${{ github.ref_name }}
|
|
141
|
+
OUT: ${{ runner.temp }}/verification
|
|
142
|
+
run: |
|
|
143
|
+
smoke=""
|
|
144
|
+
if [ ! -f verification/inputs/decisions.yaml ]; then smoke="--smoke"; fi
|
|
145
|
+
verification/run.sh --out "$OUT" --version "${TAG_NAME#v}" ${smoke:+"$smoke"}
|
|
146
|
+
- name: Keep the results
|
|
147
|
+
if: always()
|
|
148
|
+
uses: actions/upload-artifact@cf430e030ddbb5b0abf93d22962f4752f3646cd9 # v7.0.2
|
|
149
|
+
with:
|
|
150
|
+
name: verification-results
|
|
151
|
+
path: |
|
|
152
|
+
${{ runner.temp }}/verification/results.json
|
|
153
|
+
${{ runner.temp }}/verification/rmf.normalised.json
|
|
154
|
+
${{ runner.temp }}/verification/gates.json
|
|
155
|
+
${{ runner.temp }}/verification/run-a/export/
|
|
156
|
+
${{ runner.temp }}/verification/run-a/logs/
|
|
157
|
+
${{ runner.temp }}/verification/run-b/logs/
|
|
158
|
+
if-no-files-found: ignore
|
|
159
|
+
retention-days: 90
|
|
@@ -0,0 +1,79 @@
|
|
|
1
|
+
name: Verification
|
|
2
|
+
|
|
3
|
+
# Runs the independent verification in verification/ with the released
|
|
4
|
+
# package from PyPI, pinned in verification/requirements.lock. A manual run
|
|
5
|
+
# can test another released version. After each release the same check runs
|
|
6
|
+
# as the last job of release.yml, against the version just published.
|
|
7
|
+
|
|
8
|
+
on:
|
|
9
|
+
pull_request:
|
|
10
|
+
branches: [main]
|
|
11
|
+
paths:
|
|
12
|
+
- "verification/**"
|
|
13
|
+
- ".github/workflows/verification.yml"
|
|
14
|
+
workflow_dispatch:
|
|
15
|
+
inputs:
|
|
16
|
+
version:
|
|
17
|
+
description: "riskforge version to test (blank: the version pinned in requirements.lock)"
|
|
18
|
+
required: false
|
|
19
|
+
default: ""
|
|
20
|
+
|
|
21
|
+
permissions:
|
|
22
|
+
contents: read
|
|
23
|
+
|
|
24
|
+
jobs:
|
|
25
|
+
replay-tests:
|
|
26
|
+
name: Replay self-tests
|
|
27
|
+
runs-on: ubuntu-latest
|
|
28
|
+
steps:
|
|
29
|
+
- uses: actions/checkout@3d3c42e5aac5ba805825da76410c181273ba90b1 # v7.0.1
|
|
30
|
+
with:
|
|
31
|
+
persist-credentials: false
|
|
32
|
+
- uses: actions/setup-python@6d4fd22b20465ccc0f7354476588e8df7c9ca0e0 # v7.1.0
|
|
33
|
+
with:
|
|
34
|
+
python-version: "3.12"
|
|
35
|
+
- run: python -m unittest discover -s verification/tests -v
|
|
36
|
+
|
|
37
|
+
verify:
|
|
38
|
+
name: Verification run (Docker, package from PyPI)
|
|
39
|
+
runs-on: ubuntu-latest
|
|
40
|
+
timeout-minutes: 20
|
|
41
|
+
steps:
|
|
42
|
+
- uses: actions/checkout@3d3c42e5aac5ba805825da76410c181273ba90b1 # v7.0.1
|
|
43
|
+
with:
|
|
44
|
+
persist-credentials: false
|
|
45
|
+
- name: Choose the version and the inputs
|
|
46
|
+
id: pick
|
|
47
|
+
env:
|
|
48
|
+
EVENT: ${{ github.event_name }}
|
|
49
|
+
INPUT_VERSION: ${{ github.event.inputs.version }}
|
|
50
|
+
run: |
|
|
51
|
+
version=""
|
|
52
|
+
if [ "$EVENT" = "workflow_dispatch" ]; then version="$INPUT_VERSION"; fi
|
|
53
|
+
if [ -n "$version" ] && ! [[ "$version" =~ ^[0-9]+\.[0-9]+\.[0-9]+((a|b|rc)[0-9]+)?$ ]]; then
|
|
54
|
+
echo "Not a release version: $version" >&2; exit 1
|
|
55
|
+
fi
|
|
56
|
+
echo "version=$version" >> "$GITHUB_OUTPUT"
|
|
57
|
+
# Until the tester's inputs are committed, run the made-up smoke inputs.
|
|
58
|
+
if [ -f verification/inputs/decisions.yaml ]; then smoke=""; else smoke="--smoke"; fi
|
|
59
|
+
echo "smoke=$smoke" >> "$GITHUB_OUTPUT"
|
|
60
|
+
- name: Run verification/run.sh
|
|
61
|
+
env:
|
|
62
|
+
VERSION: ${{ steps.pick.outputs.version }}
|
|
63
|
+
SMOKE: ${{ steps.pick.outputs.smoke }}
|
|
64
|
+
OUT: ${{ runner.temp }}/verification
|
|
65
|
+
run: verification/run.sh --out "$OUT" ${VERSION:+--version "$VERSION"} ${SMOKE:+"$SMOKE"}
|
|
66
|
+
- name: Keep the results
|
|
67
|
+
if: always()
|
|
68
|
+
uses: actions/upload-artifact@cf430e030ddbb5b0abf93d22962f4752f3646cd9 # v7.0.2
|
|
69
|
+
with:
|
|
70
|
+
name: verification-results
|
|
71
|
+
path: |
|
|
72
|
+
${{ runner.temp }}/verification/results.json
|
|
73
|
+
${{ runner.temp }}/verification/rmf.normalised.json
|
|
74
|
+
${{ runner.temp }}/verification/gates.json
|
|
75
|
+
${{ runner.temp }}/verification/run-a/export/
|
|
76
|
+
${{ runner.temp }}/verification/run-a/logs/
|
|
77
|
+
${{ runner.temp }}/verification/run-b/logs/
|
|
78
|
+
if-no-files-found: ignore
|
|
79
|
+
retention-days: 30
|
|
@@ -81,10 +81,10 @@ exporters/ JSON, PDF and Markdown exporters, loaded through entry points
|
|
|
81
81
|
## Hard rules
|
|
82
82
|
|
|
83
83
|
1. **No network calls and no telemetry.** RiskForge never calls home. Do not add code that sends data anywhere unless the user explicitly configures a destination. This applies to dependencies too.
|
|
84
|
-
2. **Exports must be reproducible.** The same register must produce the same export content. Do not add timestamps, random values, dictionary-order effects or environment-dependent text to export content. The known exceptions are the `id` and `generated_at` fields of the Risk Management File and, from RMF schema 1.1.0, the fields [ADR-04](docs/adr/ADR-04-rmf-content-digest-and-signatures.md) defines in its provenance blocks `signatures`, `public_keys`, `chain_proof` and `receipt`, and no others. The content digest leaves all of these out, and the 1.1.0
|
|
84
|
+
2. **Exports must be reproducible.** The same register must produce the same export content. Do not add timestamps, random values, dictionary-order effects or environment-dependent text to export content. The known exceptions are the `id` and `generated_at` fields of the Risk Management File and, from RMF schema 1.1.0, the fields [ADR-04](docs/adr/ADR-04-rmf-content-digest-and-signatures.md) defines in its provenance blocks `signatures`, `public_keys`, `chain_proof` and `receipt`, and no others. The content digest leaves all of these out, and the 1.1.0 and 1.2.0 schemas forbid any other field in those blocks. The 1.2.0 `validation` block ([ADR-05](docs/adr/ADR-05-rmf-validation-block.md)) is content, not an exception: the gates depend only on the register. Adding more is a bug.
|
|
85
85
|
3. **The question bank is the source of truth.** Questions live in `src/riskforge/_data/question_bank/*.yaml` and patterns in `src/riskforge/_data/patterns/patterns.yaml`. Never hardcode questions in Python. Leave these files alone unless the ticket asks for a change. When it does, flag it at the top of the PR description so a maintainer can arrange a regulatory review.
|
|
86
86
|
4. **Regulatory references must be exact.** Any EU AI Act reference in code, docstrings, output or docs must name the exact article or annex, for example `Art.9(2)(a)`. Never write a regulatory date, deadline or paraphrase of the law from memory. If a change needs one and you cannot check it against the official text, stop and raise it in the PR rather than guess.
|
|
87
|
-
5. **Do not change the hashing.** The audit chain hash, the export SHA-256 and the fields blanked before hashing (`sha256_hash`, `audit_entry_hash`, `signed_by` for RMF schema 1.0.0) must stay compatible with `riskforge verify`. For RMF
|
|
87
|
+
5. **Do not change the hashing.** The audit chain hash, the export SHA-256 and the fields blanked before hashing (`sha256_hash`, `audit_entry_hash`, `signed_by` for RMF schema 1.0.0) must stay compatible with `riskforge verify`. For RMF schemas 1.1.0 and 1.2.0 the export digest leaves out `id`, `generated_at`, `sha256_hash`, `signatures`, `public_keys`, `chain_proof` and `receipt`, as [ADR-04](docs/adr/ADR-04-rmf-content-digest-and-signatures.md) and [ADR-05](docs/adr/ADR-05-rmf-validation-block.md) record. Changing any of them needs an ADR in `docs/adr/` first.
|
|
88
88
|
6. **No secrets in the repository.** Never commit keys, tokens or `.env` files, and never print secrets in output or logs.
|
|
89
89
|
7. **Dependencies must be Apache-2.0 compatible.** Use bounded version ranges (`>=x,<y`) in `pyproject.toml`, then run `make lock` to refresh `uv.lock` and `requirements.lock`.
|
|
90
90
|
|
|
@@ -6,6 +6,49 @@ Versioning: [Semantic Versioning](https://semver.org/)
|
|
|
6
6
|
|
|
7
7
|
## [Unreleased]
|
|
8
8
|
|
|
9
|
+
## [2.1.0] - 2026-11-07
|
|
10
|
+
|
|
11
|
+
Upgrade note: the JSON export is now RMF schema 1.2.0, which RiskForge 2.0.0 does not read: its `riskforge verify --file` exits 3 on a 1.2.0 file. Upgrade every reviewer who checks exported files at the same time. Files written by 2.0.0 (schema 1.1.0) and 1.1.3 (schema 1.0.0) keep verifying.
|
|
12
|
+
|
|
13
|
+
### Added
|
|
14
|
+
|
|
15
|
+
- `riskforge init` takes `--intended-user`, `--input` and `--output` (each repeatable), `--deployment-context` and `--provider-contact`, and the new `riskforge system describe <id>` sets them later. A change is written to the system record and its register together and recorded as `system.described`, with the fields that changed. Library API: `SystemEngine.describe()`. The worked examples now fill these fields.
|
|
16
|
+
|
|
17
|
+
### Changed
|
|
18
|
+
|
|
19
|
+
- The Markdown export has a "Test Requirements" table and a "Change Log" of the audit entries the file carries, as the PDF does. The user guide describes what each export format holds (usability finding 8 of the 2.0.0 independent test).
|
|
20
|
+
- `riskforge risk list` shows the residual score, the score gate G3 uses, beside the inherent score (finding 7).
|
|
21
|
+
- `riskforge init --help` lists the allowed `--category` values (finding 3), and `riskforge tests generate --help` says which risks get a requirement (finding 6). The user guide notes that `-r` and `-d` mean different things in different commands and recommends the long forms in scripts (finding 4).
|
|
22
|
+
- Question bank change, for regulatory review: each question names the metric a test of its risk would measure (`test_metric_type` and `test_measure`). `riskforge tests generate` gives a risk the metric of its question, or of its dimension for a pattern or manual risk, and every requirement cites Art.9(8) with the threshold "set by the provider before testing". The PDF shows what each metric measures. Saved requirements from an earlier release no longer match, so gate G4 warns until `riskforge tests generate` runs again.
|
|
23
|
+
- Question bank change, for regulatory review: each of the 37 questions has a `risk_title`, the risk it records phrased as the risk ("Bias tests not repeated at each model update"), and risk items made from the bank take it as their title. The item's description is now the full question followed by its guidance. The interactive `assess` prints the risk under each question, and the user guide says that `applies: yes` means the risk applies. Items already in a register keep their title and description. A question without a `risk_title`, as in a bank written for an earlier release, gives the earlier title and description.
|
|
24
|
+
- Gate G5 "System metadata complete" warns, naming the fields, while the intended users, inputs, outputs, deployment context or provider contact is empty. It used to pass with all of them empty, and `init` could not set them (defect D7 of the 2.0.0 independent test). It still fails without a name, version, purpose or provider. A warning does not block an export, and the export records it in its `validation` block.
|
|
25
|
+
- The JSON export is RMF schema 1.2.0 ([ADR-05](docs/adr/ADR-05-rmf-validation-block.md)). It adds one required block, `validation`: the result of every validation gate as it ran on the exported register (id, description, `PASS`, `WARN` or `FAIL`, and details), and an overall `status`, the most severe of them. The content digest covers it, so the digest and any signature over it now vouch for the gate results. The schema is published at `https://aiexponent.com/schemas/riskforge/rmf/1.2.0.json`. Two exports of one register state by one release still share a digest.
|
|
26
|
+
- Each cross-reference in the JSON export lists every distinct NIST AI RMF and ISO/IEC 42001 reference of its risk items, in the new required fields `nist_rmf_refs` and `iso42001_refs` of RMF schema 1.2.0. `nist_rmf_ref` and `iso42001_ref` keep the first of each.
|
|
27
|
+
- The `rmf.exported` audit entry lists the failing gates as `failing_gates` when an export is forced past them. An export that passed every gate writes the same entry as before.
|
|
28
|
+
- The Markdown export has a "Validation Gates" section, and the PDF shows the gate results recorded in the file instead of running the gates again when it renders.
|
|
29
|
+
|
|
30
|
+
### Fixed
|
|
31
|
+
|
|
32
|
+
- The PDF printed stored names such as `almost_certain (5)`, `question_bank` and `pending_implementing_act`; it now prints "Almost certain (5)", "Question bank" and "Pending implementing act". Text read from the PDF, by copy and paste or a screen reader, put each mitigation's bullet at the end of the page; the bullets now come before their mitigation. The last page ended "riskforge verify --file ." with no file; it now reads `riskforge verify --file <JSON export>` (defect D9 of the 2.0.0 independent test).
|
|
33
|
+
- `riskforge validate --help` described `--force` as "Export even if FAIL gates present", but `validate` never exports. The help and the message now say that `--force` only makes `validate` exit 0, and that `export` takes its own `--force` (defect D11).
|
|
34
|
+
- The README's sample question used the id `PRIV-007`, which matches no bank id; it is now `PR-006`, the next free privacy id (defect D12).
|
|
35
|
+
- Test requirements came from one template per dimension with a fixed threshold, so the robustness risks of a tabular credit model got `faithfulness >= 0.85`, a metric for generated text, reviewer training got `override_latency_ms <= 500`, and `fundamental_rights_impact_score = 0` was defined nowhere. Under the PDF heading for Article 9(6) to 9(8), entries cited Art.9(2)(a), Art.9(2)(b), Art.10, Art.13 and Art.14 (defect D5 of the 2.0.0 independent test). Requirements now take the metric of their question and cite Art.9(8), as above.
|
|
36
|
+
- Risk items made from the question bank were titled with the question text cut at 120 characters, often mid-phrase, and phrased as a question, so a score did not say whether it was for the control missing or present (defect D3 of the 2.0.0 independent test). They now take the question's risk title, as above.
|
|
37
|
+
- The audit log named `cli` as the actor of `init`, `system classify`, `system describe`, `tests generate`, `export` and `import`, while `assess` and `risk accept` named a person, so one project's log mixed `cli`, "Mara Lindqvist" and "Mara Lindqvist, Head of Model Risk" (defect D10 of the 2.0.0 independent test). These commands now record the `RISKFORGE_ACTOR` environment variable when it is set, which `risk accept` and `risk mitigate` already read, and `cli` otherwise. A value with a line break or control character exits 3.
|
|
38
|
+
- A question answered `unknown` was scored from the question's hints, or 3 x 3 when it has none, without saying so, and `knowledge_gap_reason` was always empty (defect D6 of the 2.0.0 independent test). The reason now says the answer was unknown and where each score came from, the Markdown and PDF exports show it next to the item, and the user guide documents the rule. Knowledge gaps recorded before keep an empty reason until their answer changes. Library API: `AssessEngine.knowledge_gap_item()` builds such an item.
|
|
39
|
+
- The review date is now whole calendar months after the assessment date: `assess --review-months 12` on 4 November 2026 gives 4 November 2027. It used to count 30 days a month, so 12 months came out 360 days later, on 30 October 2027 (defect D2 of the 2.0.0 independent test). A day the target month does not have becomes its last day. Registers written before keep their stored review date. `--review-months` below 1 now exits 3 instead of setting a review date on or before the assessment, and `RiskEngine.create_register()` raises `ValueError` for it.
|
|
40
|
+
- A cross-reference group showed the NIST AI RMF and ISO/IEC 42001 references of one of its risk items only, so the `Art.9(2)(a)` group of the 2.0.0 independent test showed `MEASURE 2.11` and `Annex A.7` while it also held items citing `GOVERN 1.1` and `MAP 5.1` (defect D4). The new lists name every reference of the group.
|
|
41
|
+
- An export forced past a failing gate with `--force` was invisible in the signed JSON and the Markdown export, and the PDF's "Exported with failing gates" line was not covered by the digest it printed (defect D1 of the 2.0.0 independent test, `verification/REPORT.md`). All three formats now show the failing gates, under the content digest.
|
|
42
|
+
- `riskforge verify --file` reads RMF schema 1.2.0, and fails a 1.2.0 file with exit 2 when its `validation` status is not the most severe gate status or a gate is listed twice, so a file cannot report PASS over a failing gate even when its signer redoes the digest and the signature.
|
|
43
|
+
|
|
44
|
+
### Security
|
|
45
|
+
|
|
46
|
+
- The locked dependency versions in `requirements.lock` and `uv.lock` move past advisories published after 2.0.0: Pillow 13.0.0 (WeasyPrint's image library), filelock 4.2.8, Brotli 1.2.1 and packaging 26.3. `pyproject.toml` already allows filelock 4.2.8 and packaging 26.3, and WeasyPrint and FontTools already allow the new Pillow and Brotli, so an install that does not use the lock files is unchanged.
|
|
47
|
+
|
|
48
|
+
### Known issues
|
|
49
|
+
|
|
50
|
+
- Bank questions PR-003 (data minimisation) and PR-004 (personal data in training data) still cite no EU AI Act article (D8 of the 2.0.0 independent test). The reference will be added in 2.1.1 once it is checked against the official text of Article 10.
|
|
51
|
+
|
|
9
52
|
## [2.0.0] - 2026-10-18
|
|
10
53
|
|
|
11
54
|
Upgrade note: do not downgrade a project. Once RiskForge 2.0.0 has changed a project, `riskforge verify` in RiskForge 1.1.3 reports its audit log as corrupt (exit 2, `entry_hash mismatch` from the first entry that carries `register_fingerprint`), and so do releases 1.0.0 to 1.1.2. Upgrade every machine that works on a project at the same time. Back up `.riskforge/` before the first 2.0.0 command. Projects and RMF files written by 1.1.3 keep verifying under 2.0.0.
|