Sentry, feature-complete and packaged up for low-volume deployments and proofs-of-concept
This report presents the forensic synthetic code analysis of getsentry/self-hosted, a Shell project with 9,447 GitHub stars. SynthScan v2.0 examined 8,692 lines of code across 106 source files, recording 76 pattern matches distributed across 10 syntactic categories. The overall adjusted score of 15.8 places this repository in the Moderate AI signal band.
The scanner applied 160+ deterministic lexical heuristics, multi-line block detectors, abstract syntax tree depth profilers, and a cross-file Jaccard similarity matrix to construct a statistically normalised synthetic code estimate. All matches are individually weighted by severity coefficient and contextual multiplier before summation, and the resulting headline score is temporally discounted to account for the repository's development history relative to the commercial emergence of large language model coding tooling (November 2022 onward).
This chart maps the temporal evolution of the adjusted synthetic code score across successive scan runs. An upward trajectory indicates ongoing incorporation of AI-generated code or expanding LLM-assisted scaffolding; a stable or declining trajectory may reflect active human refactoring, code removal, or the adoption of stricter authorship policies. The dashed secondary line (right axis) independently tracks total raw pattern hit count, which can diverge from the normalised score when codebase size changes significantly between scans.
Classifies detected patterns by their diagnostic confidence and structural impact. CRITICAL patterns (coefficient 10) represent definitive synthetic signatures — hallucinated imports, explicit LLM attribution metadata — virtually never produced by human authors. HIGH (5) indicates strong structural tells such as cross-file repetition or cross-linguistic idioms. MEDIUM (2) covers recognisable conversational padding and AI-specific vocabulary. LOW (1) captures subtle indicators like tautological comments and generic boilerplate that require density to carry independent signal.
This horizontal bar chart decomposes the repository's raw synthetic code score by top-level directory, allowing you to pinpoint precisely which modules or components carry the highest AI authorship density. Directories with disproportionately high scores relative to their size warrant targeted manual review: concentrated AI signatures often trace back to mass-generated configuration layers, auto-ported test suites, LLM-scaffolded boilerplate classes, or entire subsystems authored under heavy copilot assistance. Use this view to prioritise your human code-review effort.
The scanner identified 76 distinct pattern matches across 10 syntactic categories. Each entry below represents a discrete location in the source code where the engine recorded a statistically significant AI authorship indicator. Expand any category row to inspect the individual file paths, line numbers, code snippets, and the lexical context (CODE, COMMENT, or STRING) in which each match was detected.
Reading the findings table: The Severity column indicates the diagnostic confidence level (CRITICAL / HIGH / MEDIUM / LOW). The Context column identifies whether the match occurred inside executable code, an inline comment, or a string literal — comment-context matches receive a ×1.5 weight because LLMs systematically over-annotate. The ⚡ bolt icon marks clustered matches: three or more patterns within a 10-line window, each receiving an additional ×1.5 density multiplier as dense clusters constitute far stronger evidence of synthetic authorship than isolated hits.
| Severity | File | Line | Snippet | Context |
|---|---|---|---|---|
| MEDIUM⚡ | _unit-test/setup-custom-ca-certificate-test.sh | 9 | # ----------------------------------------------------------------------- | COMMENT |
| MEDIUM⚡ | _unit-test/setup-custom-ca-certificate-test.sh | 11 | # ----------------------------------------------------------------------- | COMMENT |
| MEDIUM⚡ | _unit-test/setup-custom-ca-certificate-test.sh | 17 | # ----------------------------------------------------------------------- | COMMENT |
| MEDIUM⚡ | _unit-test/setup-custom-ca-certificate-test.sh | 19 | # ----------------------------------------------------------------------- | COMMENT |
| MEDIUM⚡ | _unit-test/setup-custom-ca-certificate-test.sh | 25 | # ----------------------------------------------------------------------- | COMMENT |
| MEDIUM⚡ | _unit-test/setup-custom-ca-certificate-test.sh | 27 | # ----------------------------------------------------------------------- | COMMENT |
| MEDIUM⚡ | _unit-test/setup-custom-ca-certificate-test.sh | 34 | # ----------------------------------------------------------------------- | COMMENT |
| MEDIUM⚡ | _unit-test/setup-custom-ca-certificate-test.sh | 36 | # ----------------------------------------------------------------------- | COMMENT |
| MEDIUM | _unit-test/setup-custom-ca-certificate-test.sh | 48 | # ----------------------------------------------------------------------- | COMMENT |
| MEDIUM | _unit-test/setup-custom-ca-certificate-test.sh | 55 | # ----------------------------------------------------------------------- | COMMENT |
| MEDIUM | _unit-test/setup-custom-ca-certificate-test.sh | 98 | # ----------------------------------------------------------------------- | COMMENT |
| MEDIUM | _unit-test/setup-custom-ca-certificate-test.sh | 100 | # ----------------------------------------------------------------------- | COMMENT |
| MEDIUM | scripts/_lib.sh | 22 | # ---------------------------------------- | COMMENT |
| Severity | File | Line | Snippet | Context |
|---|---|---|---|---|
| LOW | workstation/299_setup-completed.sh | 1 | #!/bin/bash | COMMENT |
| LOW | install/migrate-pgbouncer.sh | 1 | echo "${_group}Migrating Postgres config to PGBouncer..." | COMMENT |
| LOW | install/detect-platform.sh | 1 | source install/_detect-container-engine.sh | COMMENT |
| LOW | install/bootstrap-s3-profiles.sh | 1 | # The purpose of this file is to have both `sentry`-based containers and `vroom` use the same bucket for profiling. | COMMENT |
| LOW | _unit-test/migrate-pgbouncer-test.sh | 21 | "PORT": "", | COMMENT |
| LOW | _unit-test/migrate-pgbouncer-test.sh | 81 | rm $SENTRY_CONFIG_PY | COMMENT |
| LOW | _unit-test/migrate-pgbouncer-test.sh | 141 | echo "Test 3 (custom postgres config)" | COMMENT |
| LOW | relay/config.example.yml | 21 | # max_memory_percent: 1.0 | COMMENT |
| LOW | relay/config.example.yml | 41 | prefix: "sentry.relay" # Adjust this to your needs, default is "sentry.relay" | COMMENT |
| LOW | sentry/config.example.yml | 1 | # While a lot of configuration in Sentry can be changed via the UI, for all | COMMENT |
| LOW | sentry/config.example.yml | 21 | # appear at the same time. Only uncomment one of them. | COMMENT |
| LOW | sentry/config.example.yml | 41 | # When email-replies are enabled, this value is used in the Reply-To header | COMMENT |
| LOW | sentry/config.example.yml | 61 | # | COMMENT |
| LOW | sentry/config.example.yml | 81 | # 0: | COMMENT |
| LOW | sentry/config.example.yml | 121 | COMMENT | |
| LOW | sentry/config.example.yml | 141 | # -----END RSA PRIVATE KEY----- | COMMENT |
| LOW | sentry/config.example.yml | 161 | COMMENT | |
| LOW | sentry/sentry.conf.example.py | 61 | ########### | COMMENT |
| LOW | sentry/sentry.conf.example.py | 81 | # Changing this value will result in all current sessions being invalidated. | COMMENT |
| LOW | sentry/sentry.conf.example.py | 101 | # Setting the value to False while running in an air-gapped environment will | COMMENT |
| LOW | sentry/sentry.conf.example.py | 121 | # "169.254.0.0/16", | COMMENT |
| LOW | sentry/sentry.conf.example.py | 141 | # "::ffff:c000:200/120", | COMMENT |
| LOW | sentry/sentry.conf.example.py | 161 | # "ff00::/8", | COMMENT |
| LOW | sentry/sentry.conf.example.py | 241 | ################## | COMMENT |
| LOW | sentry/sentry.conf.example.py | 261 | ######## | COMMENT |
| LOW | sentry/sentry.conf.example.py | 341 | # End of SSL/TLS settings | COMMENT |
| LOW | sentry/sentry.conf.example.py | 461 | ####################### | COMMENT |
| LOW | sentry/sentry.conf.example.py | 481 | # CSP_SCRIPT_SRC += ["example.com"] | COMMENT |
| LOW | sentry/sentry.conf.example.py | 501 | # this to match your IPs/domains. Ports should be included if you are using custom ports. | COMMENT |
| LOW | sentry/sentry.conf.example.py | 521 | COMMENT | |
| LOW | sentry/enhance-image.example.sh | 1 | #!/bin/bash | COMMENT |
| Severity | File | Line | Snippet | Context |
|---|---|---|---|---|
| MEDIUM | sentry-admin.sh | 11 | # Define the Docker volume mapping. | COMMENT |
| MEDIUM | install/error-handling.sh | 22 | # Create the breadcrumb payload now before stacktrace is printed | COMMENT |
| MEDIUM | _unit-test/migrate-pgbouncer-test.sh | 40 | # Create the replacement text in a temp file | COMMENT |
| MEDIUM | _unit-test/migrate-pgbouncer-test.sh | 97 | # Create the replacement text in a temp file | COMMENT |
| MEDIUM | _unit-test/migrate-pgbouncer-test.sh | 154 | # Create the replacement text in a temp file | COMMENT |
| MEDIUM | sentry/sentry.conf.example.py | 1 | # This file is just Python, with a touch of Django which means | COMMENT |
| Severity | File | Line | Snippet | Context |
|---|---|---|---|---|
| LOW | docker-compose.yml | 86 | # Leaving the value empty to just pass whatever is set | COMMENT |
| LOW | docker-compose.yml | 119 | # Leaving the value empty to just pass whatever is set | COMMENT |
| MEDIUM | docker-compose.yml | 122 | # If you have statsd server, you can utilize that to monitor self-hosted Snuba containers. | COMMENT |
| LOW | install/error-handling.sh | 86 | # If not, we'll just use the kernel name and version from `uname`. | COMMENT |
| MEDIUM | symbolicator/config.example.yml | 9 | # If you have statsd server, you can utilize that to monitor self-hosted Symbolicator. | COMMENT |
| MEDIUM | relay/config.example.yml | 36 | # If you have statsd server, you can utilize that to monitor self-hosted Relay. | COMMENT |
| MEDIUM | sentry/sentry.conf.example.py | 539 | # If you have a statsd server, you can utilize that to monitor self-hosted | COMMENT |
| Severity | File | Line | Snippet | Context |
|---|---|---|---|---|
| LOW | install/_min-requirements.sh | 1 | # Don't forget to update the README and other docs when you change these! | COMMENT |
| LOW | sentry/config.example.yml | 46 | # Also don't forget to set `mail.enable-replies: true` above. | COMMENT |
| LOW | sentry/config.example.yml | 46 | # Also don't forget to set `mail.enable-replies: true` above. | COMMENT |
| MEDIUM | sentry/sentry.conf.example.py | 173 | # Through this setting, you can use the provided blob storage or | COMMENT |
| Severity | File | Line | Snippet | Context |
|---|---|---|---|---|
| LOW | _integration-test/conftest.py | 14 | def configure_self_hosted_environment(request): | CODE |
| LOW | _integration-test/conftest.py | 44 | def setup_backup_restore_env_variables(): | CODE |
| LOW | _integration-test/test_01_basics.py | 113 | def test_asset_internal_rewrite(): | CODE |
| LOW | _integration-test/test_01_basics.py | 121 | def test_memcached_django_cache(): | CODE |
| LOW | _integration-test/test_01_basics.py | 210 | def test_cleanup_crons_running(): | STRING |
| LOW | _integration-test/test_01_basics.py | 229 | def test_custom_certificate_authorities(): | STRING |
| LOW | _integration-test/test_01_basics.py | 476 | def test_receive_transaction_events(client_login): | STRING |
| LOW | _integration-test/test_01_basics.py | 503 | def test_receive_user_feedback_events(client_login): | STRING |
| LOW | _integration-test/test_01_basics.py | 534 | def test_receive_metrics_events(client_login): | STRING |
| LOW | _integration-test/test_01_basics.py | 601 | def test_upload_mobile_builds(client_login): | STRING |
| Severity | File | Line | Snippet | Context |
|---|---|---|---|---|
| LOW | install/ensure-correct-permissions-profiles-dir.sh | 9 | # Check if the parent directory of /var/vroom/sentry-profiles is already owned by vroom:vroom | COMMENT |
| LOW | install/bootstrap-s3-profiles.sh | 75 | # Check if there are files in the sentry-vroom volume | COMMENT |
| Severity | File | Line | Snippet | Context |
|---|---|---|---|---|
| LOW | sentry/config.example.yml | 25 | # NOTE: The following 2 configs (mail.from and mail.list-namespace) are set | COMMENT |
| Severity | File | Line | Snippet | Context |
|---|---|---|---|---|
| LOW | _integration-test/nodejs/user-feedback.js | 5 | name: "John Doe", | CODE |
| Severity | File | Line | Snippet | Context |
|---|---|---|---|---|
| LOW | sentry/sentry.conf.example.py | 4 | CODE |