plinq.com.br

Markers associated with a specific builder or platform. A marker can be added by hand or inherited from a template, so it suggests — but does not prove — which tool was used.

• Builder-specific asset reference: Lovable direct +60 pts
  PROV_PLATFORM_ASSET · provenance

  The page references an asset publicly associated with Lovable projects. This may indicate the site was generated or edited with Lovable; it is not proof of authorship, and references can be copied or inherited from a template.

  tool:

  Lovable

  tools:

  ["Lovable"]

  matched:

  ["script: /~flock.js","script: /__l5e/events.4d3abd1f6b7321c2.js"]

  signatures:

  ["lovable_flock_script","lovable_l5e_events_script"]

Design, copy and structure patterns. These are weak, capped signals — plenty of hand-made sites share them.

• Full pre-installed component kit in an app shell weak +4 pts
  SCAF_SHADCN_FULL_KIT_IN_SHELL · design

  The app shell ships CSS for almost the entire shadcn/ui component set, as starter templates of AI app builders do (seen on most Lovable and Base44 sites in our spot check, on none of the hand-made controls). Starter kits used by people can look the same.

  components:

  ["sidebar","toast","accordion","command","navigation-menu","select"]

• Untouched shadcn/ui default theme weak +2 pts
  SCAF_SHADCN_DEFAULT_THEME · design

  The stylesheet still uses the default shadcn/ui theme values. Builder templates ship them and are often left unchanged; hand-made projects that skipped theming do the same.

  signals:

  ["default sidebar tokens"]

Frameworks, libraries and hosting we noticed. Context only — popular tools are not evidence of AI generation and add 0 points.

• Hosting / CDN hint context 0 pts
  TECH_HOSTING_HINT · technology

  The static HTML suggests a known hosting / CDN provider. This is technology context only and adds no points: it is common in both hand-written and generated sites.

  signals:

  ["Cloudflare response header","Server: Cloudflare"]

• Uses React context 0 pts
  TECH_REACT · technology

  The static HTML suggests React. This is technology context only and adds no points: it is common in both hand-written and generated sites.

  signals:

  ["empty #root mount point with module script"]

• Uses Tailwind CSS context 0 pts
  TECH_TAILWIND · technology

  The static HTML suggests Tailwind CSS. This is technology context only and adds no points: it is common in both hand-written and generated sites.

  signals:

  ["--tw-* custom properties in CSS"]

• Uses Vite context 0 pts
  TECH_VITE · technology

  The static HTML suggests Vite. This is technology context only and adds no points: it is common in both hand-written and generated sites.

  signals:

  ["default Vite build entry: /assets/index-BlpHuf2v.js"]

• Client-rendered app shell context 0 pts
  LIMIT_HTML_ONLY · constraint

  The homepage HTML is mostly an empty JavaScript app shell. The scanner does not run JavaScript, so the rendered page could not be analyzed and design or content signals are mostly unavailable.

  empty_mount_point:

  true

  visible_text_chars:

  0