Skip to content

docs(veracode): Add documentation for 4 new tables - #22415

Open
inkeep[bot] wants to merge 1 commit into
masterfrom
docs-writer-ai-update-2026-11-16T16-56-35-566Z-6lveh8
Open

inkeep[bot] wants to merge 1 commit into
masterfrom
docs-writer-ai-update-2026-11-16T16-56-35-566Z-6lveh8

Conversation

@inkeep

@inkeep inkeep Bot commented Nov 16, 2026

Copy link
Copy Markdown
Contributor

Changes

Updates the Veracode source documentation to reflect the addition of four new tables from PostHog/posthog#136541:

  • summary_report – Per-application compliance status, Veracode Level, and flaw counts
  • cwes – Lookup table to resolve CWE IDs on findings
  • categories – Lookup table to resolve category IDs on findings
  • scans – Org-wide scan history from the Reporting API v2 (off by default, requires Veracode support to enable)

Documentation updates

  1. Updated intro – Now mentions compliance reports, CWE and category lookups, and scan history
  2. Updated sync modes – Changed from "All Veracode tables are full refresh" to "Most Veracode tables are full refresh" since the scans table syncs incrementally on last_updated_date, going back at most 180 days
  3. Added troubleshooting item – Guidance that the scans table requires the Reporting API to be enabled by Veracode support

The <SourceTables /> and <SourceParameters /> components will automatically render the new tables and their descriptions from the canonical descriptions and settings files updated in the original PR.


This PR was created by the Inkeep Content Writer agent, which is maintained by the Docs and Wizard team. Please reach out on Slack for help if needed.

@github-actions

github-actions Bot commented Nov 16, 2026 •

Copy link
Copy Markdown
Contributor

Deploy preview

Status Details Updated (UTC)
🟢 Ready View preview Nov 16, 2026 05:11PM

Changed pages

Page Source
Linking Veracode as a source contents/docs/data-pipelines/sources/veracode.md

@github-actions

Copy link
Copy Markdown
Contributor

Vale prose linter → found 1 errors, 12 warnings, 0 suggestions in your markdown

Full report → Copy the linter results into an LLM to batch-fix issues.

Linter being weird? Update the rules!

contents/docs/data-pipelines/sources/veracode.md — 1 errors, 12 warnings, 0 suggestions
Line Severity Message Rule
2:16 warning 'Veracode' is a possible misspelling. PostHogBase.Spelling
16:5 warning 'Veracode' is a possible misspelling. PostHogBase.Spelling
16:76 warning Use the Oxford comma before 'and' or 'or' in a list of three or more items. PostHogBase.OxfordComma
16:145 warning Capitalize 'Data Warehouse' for PostHog's product. Use 'data warehouse' for the general industry concept. PostHogBase.ProductNames
26:9 warning 'Veracode' is a possible misspelling. PostHogBase.Spelling
26:185 warning 'Veracode's' is a possible misspelling. PostHogBase.Spelling
28:147 warning 'Veracode' is a possible misspelling. PostHogBase.Spelling
28:171 error Hi, Andy here... use an en dash ( – ) with spaces. On Mac, holding down the Option and hyphen key will give you an en dash. PostHogBase.EnDash
34:45 warning Use 'API' instead of 'api'. Vale.Terms
34:74 warning Use 'API' instead of 'api'. Vale.Terms
34:107 warning Use 'API' instead of 'api'. Vale.Terms
40:6 warning 'Veracode' is a possible misspelling. PostHogBase.Spelling
54:51 warning 'Veracode' is a possible misspelling. PostHogBase.Spelling

@github-actions

Copy link
Copy Markdown
Contributor

Bundle report

Total JS (gzip)

12.22 MiB (no change)

Eager graph (modules shipped in each entrypoint's initial chunks)

Entrypoint Eager size Budget Modules
✅ app 11.15 MiB (no change) report-only 1107
Largest modules in the app closure
Module Size
css ./node_modules/.pnpm/css-loader@5.2.7_webpack@5.101.3/node_modules/css-loader/dist/cjs.js??ruleSet[1].rules[8].oneOf[1].use[1]!./node_modules/.pnpm/postcss-loader@4.3.0_postcss@8.5.6_webpack@5.101.3/node_modules/postcss-loader/dist/cjs.js??ruleSet[1].rules[8].oneOf[1].use[2]!./src/styles/global.css 1023.1 KiB
./src/components/Stickers/Stickers.tsx 696.4 KiB
./node_modules/.pnpm/@posthog+brand@0.13.0_react@18.3.1/node_modules/@posthog/brand/dist/generated/hoggies/svg/puzzle.mjs 388.5 KiB
./node_modules/.pnpm/@posthog+icons@0.36.6_react-dom@18.3.1_react@18.3.1__react@18.3.1/node_modules/@posthog/icons/dist/posthog-icons.es.js 354.8 KiB
./node_modules/.pnpm/react-markdown@8.0.7_@types+react@16.14.66_react@18.3.1/node_modules/react-markdown/lib/react-markdown.js + 88 modules 351.4 KiB
./node_modules/.pnpm/@posthog+brand@0.13.0_react@18.3.1/node_modules/@posthog/brand/dist/generated/hoggies/svg/basketball-coach.mjs 337.4 KiB
./node_modules/.pnpm/framer-motion@14.0.0_react-dom@18.3.1_react@18.3.1__react@18.3.1/node_modules/framer-motion/dist/es/render/components/motion/proxy.mjs + 126 modules 287.2 KiB
./node_modules/.pnpm/cloudinary-core@2.14.0_lodash@4.17.21/node_modules/cloudinary-core/cloudinary-core.js 281.9 KiB
./src/components/SearchUI/index.tsx + 87 modules 273.1 KiB
./gatsby-browser.tsx + 60 modules 259.4 KiB
./node_modules/.pnpm/@posthog+brand@0.13.0_react@18.3.1/node_modules/@posthog/brand/dist/generated/hoggies/svg/construction-1.mjs 248.5 KiB
./src/components/Pricing/PricingSlider/Slider.tsx + 87 modules 240.2 KiB
./node_modules/.pnpm/@posthog+brand@0.13.0_react@18.3.1/node_modules/@posthog/brand/dist/generated/hoggies/svg/construction-2.mjs 228.2 KiB
./node_modules/.pnpm/@posthog+brand@0.13.0_react@18.3.1/node_modules/@posthog/brand/dist/generated/hoggies/svg/magnifying-glass.mjs 221.7 KiB
./src/hooks/useProduct.ts + 18 modules 166.8 KiB

Eager-graph budgets are report-only until a baseline is established. Sizes are gzip of public/**/*.js; eager size is webpack module source bytes for the modules actually shipped in the entrypoint's initial chunks (post-tree-shake).

@github-actions

Copy link
Copy Markdown
Contributor

Hey @Gilbert09! This docs PR was generated for you by an agent. You're responsible for reviewing and merging it into production.

  1. Review and approve the PR
  2. Merge the PR
    a. Check the preview env and CI build and merge it yourself
    b. Enable auto-merge if you're confident in the changes

This branch has not been deployed

No deployments
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

0 participants