Loading report…
← nittim
← nittimshared report
README badgeBadge for your project's readme fileREADME badge
[](https://nittim.com)[](https://nittim.com)Shippable once the listed conditions are addressed.You can make it live once the listed conditions are handled.Handle the listed conditions, then ship.
This verdict covers the 2% of your repository we read — see what we didn’t read below.This result is based on the 2% of your project’s code we actually read — see what we didn’t read below.Covers 2% of your repo — see what we didn’t read below.
This audit read 220 of your 7664 files — the ones most likely to hurt you first. The snapshot was truncated — this audit's size limit was reached.
The scores and findings above cover only those files. The rest of the repository hasn’t been audited yet. The denominator counts every file in the repository — images, generated output, vendored and build directories included.
220 of 7664 files were audited. This audit's size or file-count limit was reached, so some source and configuration files were left unread. The denominator counts every file in the repository — images, generated output, vendored and build directories included.
This audit's size limit was reached before it read the whole repository. The verdict and every score on this report were computed from what it did read — read them as evidence about that sample, not a clean bill of health for the rest.
AI Code Confidence capped at 18
This snapshot is the official PostgreSQL source tree (postgres/postgres), a public GitHub mirror of one of the most mature, rigorously reviewed C codebases in existence. The deterministic scanners found zero hardcoded secrets and zero known-vulnerable dependencies. The audited files (contrib extensions, amcheck, pgcrypto, bloom AM, CI workflow) show deliberate, complete, internally consistent engineering with extensive comments, defensive error handling, ResourceOwner-based leak protection, and comprehensive regression/TAP tests. This is the antithesis of vibe-coded software: there are no placeholder stubs, hallucinated APIs, or unhandled edge cases of the kind this audit screens for. The few observations below are minor and largely inherent to a low-level C database engine (manual memory management, shell invocation in an opt-in backup module, a non-cryptographic PRNG used intentionally for on-disk index signatures). Note that this is explicitly a read-only mirror — the project does not accept GitHub pull requests, which is a devex/process consideration rather than a defect. The snapshot was truncated to 220 of 7664 files, so this assessment is scoped to the highest-priority files seen and does not penalize unseen code. Overall the repository is production-ready by any reasonable standard; PostgreSQL is itself the production datastore for countless systems. IP exposure is assessed independently: the novel algorithms here (GIN/B-tree corruption verification, bloom signature indexing, PGP/shacrypt implementations) are intentionally published under the PostgreSQL open-source license and are heavily backed by prior art, so there is little defensible IP at risk and no production impact.
.github/workflows/pg-ci.ymlsets permissions: contents: read, gates execution on PG_CI_ENABLED to avoid resource waste in forks, pins runner/container versions, and collects core backtraces and logs on failure.Weighted blend of 4 dimensions → ~82/100. Dimensions are weighted by importance (Security and Privacy weigh heaviest). Published figures are approximate; nittim's exact weighting and precise scoring are proprietary, while the verdict is computed on exact internal values.4 categories combine into ~82/100. Some categories count for more than others (Security and Privacy count the most). The published numbers are approximate; nittim's exact math is kept private, while the verdict itself is worked out from the exact internal numbers.Weighted blend of 4 dimensions → ~82/100 (Security and Privacy weigh heaviest). Published figures are approximate; nittim's exact weighting is proprietary. The verdict runs on exact internal values.
IP Protection is an independent IP-defensibility lens and is excluded from this blend.IP Protection (checking whether your ideas are exposed) is judged separately and isn’t
part of this combined number.IP Protection is judged separately, excluded from this blend.
Scores are a judgement, not a measurement: a re-audit of the same commit can land a few
points either side of this figure. The evidence underneath it is deterministic — the same
commit always yields the same committed-secret and vulnerable-dependency findings.Scores are a judgment call, not an exact measurement: checking the same saved snapshot of
your code twice can land a few points either side of this number. The evidence underneath
it is not — the same snapshot always turns up the same passwords-in-code and known-security-bug
findings.Scores are a judgment, not a measurement — a re-audit can land a few points either side. The evidence underneath is deterministic: the same commit always yields the same secret and vulnerable-dependency findings.
Each score is the model's overall assessment of the dimensions it covers, across everything it reviewed — not a tally of the findings in this report. Findings are the subset worth acting on, so a score can sit above or below what the listed findings alone would suggest.Each score is the AI's overall judgment of everything it reviewed in that category — not a
count of the problems listed in this report. The listed problems are the ones worth acting
on, so a score can sit above or below what they alone would suggest.Each score is the model's overall assessment across everything it reviewed — not a tally of this report's findings. A score can sit above or below what the findings alone suggest.
Verdict rationale — Why this verdict — Verdict rationale — This is the canonical PostgreSQL source — a decades-mature, exhaustively reviewed C codebase with comprehensive test suites, clean least-privilege CI, zero detected secrets, and zero vulnerable dependencies. The audited files exhibit deliberate, complete, internally consistent engineering with strong defensive error handling and no AI/vibe-coding anti-patterns. The only observations are minor and largely intrinsic to a low-level database kernel (manual C memory management warranting continued fuzzing, an opt-in shell-based backup module that already sanitizes input, and diagnostic modules that can log sensitive data when explicitly enabled). None of these block production use. IP exposure is assessed independently and does not affect the verdict: the novel algorithms present are intentionally open-sourced and backed by extensive prior art, so little defensible IP is at risk.