verify-layer: cloud exports (AWS ECS/EC2/Lambda, Azure VMs/Container Instances/Container Apps/Web Apps, GCP Compute Engine/Cloud Run) read from the operator's own CLI export, never from an account; fixtures derived from the vendors' documented examples; a real account is unmeasured and the README says so

This commit is contained in:
Aere Network committed 2026-10-18 14:12:00 +03:00
1 parent ea695dcf32
commit ac14880703
49 files changed
+10080 -17

No files matched your search

+5 -1
View File
@@ -12,17 +12,21 @@ wrote it.
Paths that DO resolve are written relative to a side-by-side checkout of the Aere repositories, so they begin with a
repository name, for example `aere-contracts/contracts/pqc/AereCryptoRegistry.sol`.
Unresolvable distinct paths in this repository: **12**.
Unresolvable distinct paths in this repository: **16**.
- `ContainerApps_ListBySubscription.json` cited in: aere-quantum/verify-layer/fixturi-cloud/README.md
- `VirtualMachine_List_MaximumSet_Gen.json` cited in: aere-quantum/verify-layer/fixturi-cloud/README.md
- `addresses.txt` cited in: aere-quantum/exposure-report/README.md
- `antete.mjs` cited in: aere-quantum/exposure-report/README.md
- `btc/antete.mjs` cited in: aere-quantum/exposure-report/README.md
- `data/audit.log` cited in: aere-quantum/pq-kms/README.md
- `data/root-check.json` cited in: aere-quantum/pq-kms/README.md
- `fixturi-cloud/deriva.mjs` cited in: aere-quantum/README.md
- `libs.versions.toml` cited in: aere-quantum/crypto-inventory/README.md
- `plic-aip23.json` cited in: aere-quantum/exposure-report/README.md
- `proba-client-real.mjs` cited in: aere-quantum/readiness/README.md
- `raport.json` cited in: aere-quantum/exposure-report/README.md
- `raport.md` cited in: aere-quantum/exposure-report/README.md
- `src/azure-cli/azure/cli/command_modules/vm/custom.py` cited in: aere-quantum/verify-layer/fixturi-cloud/README.md
- `verify.mjs` cited in: aere-quantum/exposure-report/README.md
- `wallet.json` cited in: aere-quantum/agents/x402/README.md