Build Azure Cosmos DB NoSQL services with Python/FastAPI following production-grade patterns. Use when implementing database client setup with dual auth (DefaultAzureCredential + emulator), service layer classes with CRUD operations, partition key strategies, parameterized queries, or TDD patterns for Cosmos. Triggers on phrases like "Cosmos DB", "NoSQL database", "document store", "add persistence", "database service layer", or "Python Cosmos SDK".
○ declared by the publisher, as-is
Safety
CC: 3 or more mediums, or any high2 severity-bearing
Safety · gatev1.0.0 · = 354361d · assessed 2w ago
C2 severity-bearing
Graded from 2 severity-bearing findings on this release.
A gate; it passes or fails, never weighed against price or quality.
Reliability & Quality
n/anot yet graded
Reliability & Qualityv1.0.0 · = 354361d · assessed 2w ago
n/anot yet graded
Rows exist, but none carries a severity; no grade has been earned yet.
Findings with severity, graded on the same letter scale as safety.
Cost
n/anot assessed
Costv1.0.0 · = 354361d · assessed 2w ago
n/anot assessed
Not assessed; no producer has emitted into this category. An absence, not a zero.
Declared external service dependencies. Never a monetary figure.
not assessed
Popularity
355Forks
Popularity · not a figurev1.0.0 · = 354361d · assessed 2w ago
355Forks
Read off the linked repository, not off this record. It carries no verdict and enters no grade.
Context read off the linked repository. It enters no ranking and no grade.
Performance tested for◌ not assessed
no controlled task evaluation on this release
Repo★ 3.1k○·355 forks·19 watchers·80 open issues·last commit 0d old when scanned
◌Internal reference resolution completednothing foundAll body-referenced paths under references/, scripts/, and assets/ resolved in the bundle.vettd · scan · 2wnothing found
Not assessed; no producer has emitted into cost for this asset. That is different from a check that ran and found nothing, which the record would carry as a row of its own.
assessed2w ago · Cisco AI Defense · Vettd core● current
source stateThe source matches what was scanned. No changes detected.Up to date
re-check policyre-checked against the upstream source on the scheduler's cadencenext check in 10h
re-run whena new release ships, the upstream source changes, or the scanner ruleset is revisedauto-scheduled
Limitations & open conflicts
limitationCost is not assessed: behaviour there is unmeasured, not clean△ gap
limitationReliability & Quality carries rows but no severity-bearing one: nothing has been graded there△ gap
conflictno two sources report the same quantity on this record
Verify: does this record describe your copy?
What record 985de4d2-a802-453b-9798-2f80cead1333 covers
scannerv11● current
validityassessed 2w ago · Up to date
$vettd scan folder <path>
this record was taken at digest sha256:1a03b83a1054… compare it against the digest your own scan prints
Reproduce: re-run the evidence yourself
$vettd scan folder /path/to/your/copy
runs the same scanners against your own copy; the published record is never overwritten
How this record comparesagainst other published records · full comparison →
Signal kinds
▲ finding: something to act on, carries a severity● measurement: a reproducible quantityƒ estimate: inferred from a sample▪ fact: read directly off the artifact◆ classification: assigned from a taxonomy◌ nothing found: a producer looked and emitted no object◇ context only: described, never graded
Custody marks
◐ computed by vettd○ declared by the publisher, as-is△ not assessed: nothing looked
Weigh azure-cosmos-db-py against other published skills: the safety grade, its finding counts and each category’s verdict, one row apiece. The full comparison page carries every signal and framework coverage.