{"id":811,"date":"2026-04-06T13:59:09","date_gmt":"2026-04-06T13:59:09","guid":{"rendered":"https:\/\/quickref.me\/blog\/?p=811"},"modified":"2026-04-06T13:59:09","modified_gmt":"2026-04-06T13:59:09","slug":"how-to-evaluate-sast-tools-for-enterprise-teams","status":"publish","type":"post","link":"https:\/\/quickref.me\/blog\/how-to-evaluate-sast-tools-for-enterprise-teams\/","title":{"rendered":"How to Evaluate SAST Tools for Enterprise Teams"},"content":{"rendered":"<p><span style=\"font-weight: 400;\">Choosing a SAST tool at an enterprise level is not about features. Most tools today can scan code, detect vulnerabilities, and generate reports. On paper, that makes many of them look interchangeable.<\/span><\/p>\n<p><span style=\"font-weight: 400;\">The real question is different. Can this tool work inside how your teams actually build software?<\/span><\/p>\n<p><span style=\"font-weight: 400;\">At scale, security tools don\u2019t fail on detection. They fail on adoption, interpretation, and impact. If developers don\u2019t trust the results, don\u2019t understand them, or don\u2019t see them at the right moment, those findings don\u2019t turn into action.<\/span><\/p>\n<p><span style=\"font-weight: 400;\">And once that happens, even the best scanner becomes background noise.<\/span><\/p>\n<h2><span style=\"font-weight: 400;\">Why enterprise teams struggle with SAST in practice<\/span><\/h2>\n<p><span style=\"font-weight: 400;\">In smaller teams, SAST is manageable. You run scans, review findings, fix issues, and move forward.<\/span><\/p>\n<p><span style=\"font-weight: 400;\">At enterprise scale, everything changes.<\/span><\/p>\n<p><span style=\"font-weight: 400;\">You\u2019re dealing with:<\/span><\/p>\n<ul>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">Multiple teams<\/span><\/li>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">Different tech stacks<\/span><\/li>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">Independent release cycles<\/span><\/li>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">Varying levels of security maturity<\/span><\/li>\n<\/ul>\n<p><span style=\"font-weight: 400;\">Now SAST is no longer a tool. It\u2019s a system that has to operate across all of that.<\/span><\/p>\n<p><span style=\"font-weight: 400;\">And this is where problems start.<\/span><\/p>\n<p><span style=\"font-weight: 400;\">Findings pile up faster than they can be reviewed. Different teams interpret results differently. Some fix issues immediately, others delay, and others ignore.<\/span><\/p>\n<p><span style=\"font-weight: 400;\">The tool is working. The system around it is not.<\/span><\/p>\n<h2><span style=\"font-weight: 400;\">The difference between detection and usefulness<\/span><\/h2>\n<p><span style=\"font-weight: 400;\">Most SAST tools are evaluated based on what they can find. That\u2019s the wrong metric. At the enterprise level, usefulness matters more than detection depth.<\/span><\/p>\n<p><span style=\"font-weight: 400;\">Because if a tool produces hundreds of findings that engineers don\u2019t trust or understand, those findings don\u2019t lead to action.<\/span><\/p>\n<p><span style=\"font-weight: 400;\">They create friction. And friction leads to avoidance. What actually matters is:<\/span><\/p>\n<ul>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">How accurate the findings are<\/span><\/li>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">How clearly they are prioritized<\/span><\/li>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">How easily engineers can act on them<\/span><\/li>\n<\/ul>\n<p><span style=\"font-weight: 400;\">If those things are missing, more coverage doesn\u2019t help. It makes things worse.<\/span><\/p>\n<h2><span style=\"font-weight: 400;\">Where traditional evaluation falls apart<\/span><\/h2>\n<p><span style=\"font-weight: 400;\">Enterprise teams often evaluate SAST tools through structured comparisons:<\/span><\/p>\n<ul>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">Feature lists<\/span><\/li>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">Benchmarks<\/span><\/li>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">Compliance requirements<\/span><\/li>\n<\/ul>\n<p><span style=\"font-weight: 400;\">On paper, many tools look similar. But those comparisons miss how the tool behaves in real workflows.<\/span><\/p>\n<p><span style=\"font-weight: 400;\">The difference becomes obvious only after implementation. How fast are the scans? Do developers see results in their workflow or somewhere else? Are findings actionable, or do they require manual investigation every time?<\/span><\/p>\n<p><a href=\"https:\/\/www.aikido.dev\/blog\/snyk-vs-checkmarx\"><span style=\"font-weight: 400;\">Snyk vs Checkmarx<\/span><\/a><span style=\"font-weight: 400;\"> usually comes down to something simple: which tool is actually easier to work with day to day, where there\u2019s less noise, clearer results, and less time spent figuring things out.<\/span><\/p>\n<p><span style=\"font-weight: 400;\">Because what looks equivalent in a checklist often feels very different in practice.<\/span><\/p>\n<h2><span style=\"font-weight: 400;\">What actually matters when evaluating SAST tools<\/span><\/h2>\n<p><span style=\"font-weight: 400;\">Enterprise teams that get this right focus on a smaller set of deeper criteria.<\/span><\/p>\n<h3><span style=\"font-weight: 400;\">Signal over volume<\/span><\/h3>\n<p><span style=\"font-weight: 400;\">The tool should reduce noise, not create it. If engineers constantly deal with false positives or irrelevant findings, they stop paying attention.<\/span><\/p>\n<h3><span style=\"font-weight: 400;\">Context, not just detection<\/span><\/h3>\n<p><span style=\"font-weight: 400;\">A finding without context is a problem. A finding with clear impact, exploitability, and location in the codebase is something that can be fixed.<\/span><\/p>\n<h3><span style=\"font-weight: 400;\">Speed and feedback loops<\/span><\/h3>\n<p><span style=\"font-weight: 400;\">If results come too late, they don\u2019t influence development. Security feedback has to fit into the pace of CI\/CD, not slow it down.<\/span><\/p>\n<h3><span style=\"font-weight: 400;\">Integration into real workflows<\/span><\/h3>\n<p><span style=\"font-weight: 400;\">If developers have to leave their environment to understand security issues, adoption drops. Findings should appear where work is already happening \u2014 pull requests, commits, pipelines.<\/span><\/p>\n<h3><span style=\"font-weight: 400;\">Consistency across teams<\/span><\/h3>\n<p><span style=\"font-weight: 400;\">At scale, the tool should behave predictably across different teams and stacks. If every team interprets results differently, security becomes fragmented.<\/span><\/p>\n<h2><span style=\"font-weight: 400;\">Why noise becomes the biggest risk<\/span><\/h2>\n<p><span style=\"font-weight: 400;\">One of the most underestimated problems in SAST is noise. Not because it\u2019s annoying. Because it changes behavior.<\/span><\/p>\n<p><span style=\"font-weight: 400;\">When engineers see too many irrelevant findings, they start filtering mentally. They skim results. They assume most issues are not critical.<\/span><\/p>\n<p><span style=\"font-weight: 400;\">Eventually, real vulnerabilities get treated the same way as noise.<\/span><\/p>\n<p><span style=\"font-weight: 400;\">That\u2019s the shift from security as a signal to security as background.<\/span><\/p>\n<p><span style=\"font-weight: 400;\">And once that happens, adding more scanning does not improve security. It weakens it.<\/span><\/p>\n<h2><span style=\"font-weight: 400;\">The role of prioritization in enterprise environments<\/span><\/h2>\n<p><span style=\"font-weight: 400;\">Prioritization is where most SAST tools either succeed or fail. Severity scores alone are not enough.<\/span><\/p>\n<p><span style=\"font-weight: 400;\">A \u201ccritical\u201d issue that is not exploitable in your environment is not urgent. A \u201cmedium\u201d issue in exposed code might be.<\/span><\/p>\n<p><span style=\"font-weight: 400;\">Without context, teams either:<\/span><\/p>\n<ul>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">Overreact and waste time<\/span><\/li>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">Or underreact and miss real risks<\/span><\/li>\n<\/ul>\n<p><span style=\"font-weight: 400;\">Effective prioritization answers a simple question:<\/span><\/p>\n<p><span style=\"font-weight: 400;\">Does this matter for us, right now?<\/span><\/p>\n<p><span style=\"font-weight: 400;\">That requires understanding not just code, but how that code is used, exposed, and connected to the rest of the system.<\/span><\/p>\n<h2><span style=\"font-weight: 400;\">Why developer experience is not optional<\/span><\/h2>\n<p><span style=\"font-weight: 400;\">In enterprise environments, developers are the ones who interact with SAST every day. If the experience is slow, confusing, or interruptive, they will work around it.<\/span><\/p>\n<p><span style=\"font-weight: 400;\">Not because they don\u2019t care about security. Because they are optimizing for delivery.<\/span><\/p>\n<p><span style=\"font-weight: 400;\">A good SAST tool does not compete with development speed. It aligns with it.<\/span><\/p>\n<p><span style=\"font-weight: 400;\">That means:<\/span><\/p>\n<ul>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">Fast scans<\/span><\/li>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">Clear results<\/span><\/li>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">Minimal manual effort to fix issues<\/span><\/li>\n<\/ul>\n<p><span style=\"font-weight: 400;\">When that happens, security becomes part of development. When it doesn\u2019t, it becomes something separate.<\/span><\/p>\n<h2><span style=\"font-weight: 400;\">What a good SAST implementation looks like<\/span><\/h2>\n<p><span style=\"font-weight: 400;\">When SAST works at scale, it feels different. Findings don\u2019t overwhelm teams. They guide them.<\/span><\/p>\n<p><span style=\"font-weight: 400;\">Engineers don\u2019t question every result. They trust what they see.<\/span><\/p>\n<p><span style=\"font-weight: 400;\">Security is not something that happens later. It happens as part of writing and reviewing code.<\/span><\/p>\n<p><span style=\"font-weight: 400;\">And most importantly, decisions become clearer. Teams know:<\/span><\/p>\n<ul>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">What needs to be fixed now<\/span><\/li>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">What can wait<\/span><\/li>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">What doesn\u2019t matter in their context<\/span><\/li>\n<\/ul>\n<p><span style=\"font-weight: 400;\">That clarity is what turns SAST from a tool into a system that actually improves security.<\/span><\/p>\n<h2><span style=\"font-weight: 400;\">The real question you should be asking<\/span><\/h2>\n<p><span style=\"font-weight: 400;\">When evaluating SAST tools, the question is not: \u201cWhat can this tool detect?\u201d It\u2019s: \u201cWill this tool change how our teams make decisions?\u201d Because detection without action doesn\u2019t reduce risk.<\/span><\/p>\n<p><span style=\"font-weight: 400;\">And at enterprise scale, the gap between detection and action is where most security programs fail. Closing that gap is what actually matters.<\/span><\/p>\n","protected":false},"excerpt":{"rendered":"<p>Choosing a SAST tool at an enterprise level is not about features. Most tools today can scan code, detect vulnerabilities, and generate reports. On paper, that makes many of them &hellip; <a href=\"https:\/\/quickref.me\/blog\/how-to-evaluate-sast-tools-for-enterprise-teams\/\" class=\"more-link\">Read More<\/a><\/p>\n","protected":false},"author":1,"featured_media":0,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[1],"tags":[],"class_list":["post-811","post","type-post","status-publish","format-standard","hentry","category-uncategorized","entry"],"yoast_head":"<!-- This site is optimized with the Yoast SEO plugin v26.4 - https:\/\/yoast.com\/wordpress\/plugins\/seo\/ -->\n<title>How to Evaluate SAST Tools for Enterprise Teams - Blog QuickRef<\/title>\n<meta name=\"robots\" content=\"index, follow, max-snippet:-1, max-image-preview:large, max-video-preview:-1\" \/>\n<link rel=\"canonical\" href=\"https:\/\/quickref.me\/blog\/how-to-evaluate-sast-tools-for-enterprise-teams\/\" \/>\n<meta property=\"og:locale\" content=\"en_US\" \/>\n<meta property=\"og:type\" content=\"article\" \/>\n<meta property=\"og:title\" content=\"How to Evaluate SAST Tools for Enterprise Teams - Blog QuickRef\" \/>\n<meta property=\"og:description\" content=\"Choosing a SAST tool at an enterprise level is not about features. Most tools today can scan code, detect vulnerabilities, and generate reports. On paper, that makes many of them &hellip; Read More\" \/>\n<meta property=\"og:url\" content=\"https:\/\/quickref.me\/blog\/how-to-evaluate-sast-tools-for-enterprise-teams\/\" \/>\n<meta property=\"og:site_name\" content=\"Blog QuickRef\" \/>\n<meta property=\"article:published_time\" content=\"2026-04-06T13:59:09+00:00\" \/>\n<meta name=\"author\" content=\"tedm\" \/>\n<meta name=\"twitter:card\" content=\"summary_large_image\" \/>\n<meta name=\"twitter:label1\" content=\"Written by\" \/>\n\t<meta name=\"twitter:data1\" content=\"tedm\" \/>\n<script type=\"application\/ld+json\" class=\"yoast-schema-graph\">{\"@context\":\"https:\/\/schema.org\",\"@graph\":[{\"@type\":[\"Article\",\"BlogPosting\"],\"@id\":\"https:\/\/quickref.me\/blog\/how-to-evaluate-sast-tools-for-enterprise-teams\/#article\",\"isPartOf\":{\"@id\":\"https:\/\/quickref.me\/blog\/how-to-evaluate-sast-tools-for-enterprise-teams\/\"},\"author\":{\"name\":\"tedm\",\"@id\":\"https:\/\/quickref.me\/blog\/#\/schema\/person\/781b09d7f4bdae81ce0d191fb1b1d5ec\"},\"headline\":\"How to Evaluate SAST Tools for Enterprise Teams\",\"datePublished\":\"2026-04-06T13:59:09+00:00\",\"mainEntityOfPage\":{\"@id\":\"https:\/\/quickref.me\/blog\/how-to-evaluate-sast-tools-for-enterprise-teams\/\"},\"wordCount\":998,\"commentCount\":0,\"publisher\":{\"@id\":\"https:\/\/quickref.me\/blog\/#organization\"},\"inLanguage\":\"en-US\",\"potentialAction\":[{\"@type\":\"CommentAction\",\"name\":\"Comment\",\"target\":[\"https:\/\/quickref.me\/blog\/how-to-evaluate-sast-tools-for-enterprise-teams\/#respond\"]}]},{\"@type\":\"WebPage\",\"@id\":\"https:\/\/quickref.me\/blog\/how-to-evaluate-sast-tools-for-enterprise-teams\/\",\"url\":\"https:\/\/quickref.me\/blog\/how-to-evaluate-sast-tools-for-enterprise-teams\/\",\"name\":\"How to Evaluate SAST Tools for Enterprise Teams - Blog QuickRef\",\"isPartOf\":{\"@id\":\"https:\/\/quickref.me\/blog\/#website\"},\"datePublished\":\"2026-04-06T13:59:09+00:00\",\"breadcrumb\":{\"@id\":\"https:\/\/quickref.me\/blog\/how-to-evaluate-sast-tools-for-enterprise-teams\/#breadcrumb\"},\"inLanguage\":\"en-US\",\"potentialAction\":[{\"@type\":\"ReadAction\",\"target\":[\"https:\/\/quickref.me\/blog\/how-to-evaluate-sast-tools-for-enterprise-teams\/\"]}]},{\"@type\":\"BreadcrumbList\",\"@id\":\"https:\/\/quickref.me\/blog\/how-to-evaluate-sast-tools-for-enterprise-teams\/#breadcrumb\",\"itemListElement\":[{\"@type\":\"ListItem\",\"position\":1,\"name\":\"Home\",\"item\":\"https:\/\/quickref.me\/blog\/\"},{\"@type\":\"ListItem\",\"position\":2,\"name\":\"How to Evaluate SAST Tools for Enterprise Teams\"}]},{\"@type\":\"WebSite\",\"@id\":\"https:\/\/quickref.me\/blog\/#website\",\"url\":\"https:\/\/quickref.me\/blog\/\",\"name\":\"Blog QuickRef\",\"description\":\"\",\"publisher\":{\"@id\":\"https:\/\/quickref.me\/blog\/#organization\"},\"potentialAction\":[{\"@type\":\"SearchAction\",\"target\":{\"@type\":\"EntryPoint\",\"urlTemplate\":\"https:\/\/quickref.me\/blog\/?s={search_term_string}\"},\"query-input\":{\"@type\":\"PropertyValueSpecification\",\"valueRequired\":true,\"valueName\":\"search_term_string\"}}],\"inLanguage\":\"en-US\"},{\"@type\":\"Organization\",\"@id\":\"https:\/\/quickref.me\/blog\/#organization\",\"name\":\"Blog QuickRef\",\"url\":\"https:\/\/quickref.me\/blog\/\",\"logo\":{\"@type\":\"ImageObject\",\"inLanguage\":\"en-US\",\"@id\":\"https:\/\/quickref.me\/blog\/#\/schema\/logo\/image\/\",\"url\":\"https:\/\/quickref.me\/blog\/wp-content\/uploads\/2023\/10\/cropped-wuickref.png\",\"contentUrl\":\"https:\/\/quickref.me\/blog\/wp-content\/uploads\/2023\/10\/cropped-wuickref.png\",\"width\":236,\"height\":63,\"caption\":\"Blog QuickRef\"},\"image\":{\"@id\":\"https:\/\/quickref.me\/blog\/#\/schema\/logo\/image\/\"}},{\"@type\":\"Person\",\"@id\":\"https:\/\/quickref.me\/blog\/#\/schema\/person\/781b09d7f4bdae81ce0d191fb1b1d5ec\",\"name\":\"tedm\",\"image\":{\"@type\":\"ImageObject\",\"inLanguage\":\"en-US\",\"@id\":\"https:\/\/quickref.me\/blog\/#\/schema\/person\/image\/\",\"url\":\"https:\/\/secure.gravatar.com\/avatar\/2689288940b2c1525bf9633d5f4c4b96d14ab0593b0ec8d5404a1f968810e963?s=96&d=mm&r=g\",\"contentUrl\":\"https:\/\/secure.gravatar.com\/avatar\/2689288940b2c1525bf9633d5f4c4b96d14ab0593b0ec8d5404a1f968810e963?s=96&d=mm&r=g\",\"caption\":\"tedm\"},\"sameAs\":[\"https:\/\/quickref.me\/blog\"],\"url\":\"https:\/\/quickref.me\/blog\/author\/tedm\/\"}]}<\/script>\n<!-- \/ Yoast SEO plugin. -->","yoast_head_json":{"title":"How to Evaluate SAST Tools for Enterprise Teams - Blog QuickRef","robots":{"index":"index","follow":"follow","max-snippet":"max-snippet:-1","max-image-preview":"max-image-preview:large","max-video-preview":"max-video-preview:-1"},"canonical":"https:\/\/quickref.me\/blog\/how-to-evaluate-sast-tools-for-enterprise-teams\/","og_locale":"en_US","og_type":"article","og_title":"How to Evaluate SAST Tools for Enterprise Teams - Blog QuickRef","og_description":"Choosing a SAST tool at an enterprise level is not about features. Most tools today can scan code, detect vulnerabilities, and generate reports. On paper, that makes many of them &hellip; Read More","og_url":"https:\/\/quickref.me\/blog\/how-to-evaluate-sast-tools-for-enterprise-teams\/","og_site_name":"Blog QuickRef","article_published_time":"2026-04-06T13:59:09+00:00","author":"tedm","twitter_card":"summary_large_image","twitter_misc":{"Written by":"tedm"},"schema":{"@context":"https:\/\/schema.org","@graph":[{"@type":["Article","BlogPosting"],"@id":"https:\/\/quickref.me\/blog\/how-to-evaluate-sast-tools-for-enterprise-teams\/#article","isPartOf":{"@id":"https:\/\/quickref.me\/blog\/how-to-evaluate-sast-tools-for-enterprise-teams\/"},"author":{"name":"tedm","@id":"https:\/\/quickref.me\/blog\/#\/schema\/person\/781b09d7f4bdae81ce0d191fb1b1d5ec"},"headline":"How to Evaluate SAST Tools for Enterprise Teams","datePublished":"2026-04-06T13:59:09+00:00","mainEntityOfPage":{"@id":"https:\/\/quickref.me\/blog\/how-to-evaluate-sast-tools-for-enterprise-teams\/"},"wordCount":998,"commentCount":0,"publisher":{"@id":"https:\/\/quickref.me\/blog\/#organization"},"inLanguage":"en-US","potentialAction":[{"@type":"CommentAction","name":"Comment","target":["https:\/\/quickref.me\/blog\/how-to-evaluate-sast-tools-for-enterprise-teams\/#respond"]}]},{"@type":"WebPage","@id":"https:\/\/quickref.me\/blog\/how-to-evaluate-sast-tools-for-enterprise-teams\/","url":"https:\/\/quickref.me\/blog\/how-to-evaluate-sast-tools-for-enterprise-teams\/","name":"How to Evaluate SAST Tools for Enterprise Teams - Blog QuickRef","isPartOf":{"@id":"https:\/\/quickref.me\/blog\/#website"},"datePublished":"2026-04-06T13:59:09+00:00","breadcrumb":{"@id":"https:\/\/quickref.me\/blog\/how-to-evaluate-sast-tools-for-enterprise-teams\/#breadcrumb"},"inLanguage":"en-US","potentialAction":[{"@type":"ReadAction","target":["https:\/\/quickref.me\/blog\/how-to-evaluate-sast-tools-for-enterprise-teams\/"]}]},{"@type":"BreadcrumbList","@id":"https:\/\/quickref.me\/blog\/how-to-evaluate-sast-tools-for-enterprise-teams\/#breadcrumb","itemListElement":[{"@type":"ListItem","position":1,"name":"Home","item":"https:\/\/quickref.me\/blog\/"},{"@type":"ListItem","position":2,"name":"How to Evaluate SAST Tools for Enterprise Teams"}]},{"@type":"WebSite","@id":"https:\/\/quickref.me\/blog\/#website","url":"https:\/\/quickref.me\/blog\/","name":"Blog QuickRef","description":"","publisher":{"@id":"https:\/\/quickref.me\/blog\/#organization"},"potentialAction":[{"@type":"SearchAction","target":{"@type":"EntryPoint","urlTemplate":"https:\/\/quickref.me\/blog\/?s={search_term_string}"},"query-input":{"@type":"PropertyValueSpecification","valueRequired":true,"valueName":"search_term_string"}}],"inLanguage":"en-US"},{"@type":"Organization","@id":"https:\/\/quickref.me\/blog\/#organization","name":"Blog QuickRef","url":"https:\/\/quickref.me\/blog\/","logo":{"@type":"ImageObject","inLanguage":"en-US","@id":"https:\/\/quickref.me\/blog\/#\/schema\/logo\/image\/","url":"https:\/\/quickref.me\/blog\/wp-content\/uploads\/2023\/10\/cropped-wuickref.png","contentUrl":"https:\/\/quickref.me\/blog\/wp-content\/uploads\/2023\/10\/cropped-wuickref.png","width":236,"height":63,"caption":"Blog QuickRef"},"image":{"@id":"https:\/\/quickref.me\/blog\/#\/schema\/logo\/image\/"}},{"@type":"Person","@id":"https:\/\/quickref.me\/blog\/#\/schema\/person\/781b09d7f4bdae81ce0d191fb1b1d5ec","name":"tedm","image":{"@type":"ImageObject","inLanguage":"en-US","@id":"https:\/\/quickref.me\/blog\/#\/schema\/person\/image\/","url":"https:\/\/secure.gravatar.com\/avatar\/2689288940b2c1525bf9633d5f4c4b96d14ab0593b0ec8d5404a1f968810e963?s=96&d=mm&r=g","contentUrl":"https:\/\/secure.gravatar.com\/avatar\/2689288940b2c1525bf9633d5f4c4b96d14ab0593b0ec8d5404a1f968810e963?s=96&d=mm&r=g","caption":"tedm"},"sameAs":["https:\/\/quickref.me\/blog"],"url":"https:\/\/quickref.me\/blog\/author\/tedm\/"}]}},"_links":{"self":[{"href":"https:\/\/quickref.me\/blog\/wp-json\/wp\/v2\/posts\/811","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/quickref.me\/blog\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/quickref.me\/blog\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/quickref.me\/blog\/wp-json\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"https:\/\/quickref.me\/blog\/wp-json\/wp\/v2\/comments?post=811"}],"version-history":[{"count":1,"href":"https:\/\/quickref.me\/blog\/wp-json\/wp\/v2\/posts\/811\/revisions"}],"predecessor-version":[{"id":812,"href":"https:\/\/quickref.me\/blog\/wp-json\/wp\/v2\/posts\/811\/revisions\/812"}],"wp:attachment":[{"href":"https:\/\/quickref.me\/blog\/wp-json\/wp\/v2\/media?parent=811"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/quickref.me\/blog\/wp-json\/wp\/v2\/categories?post=811"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/quickref.me\/blog\/wp-json\/wp\/v2\/tags?post=811"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}