seo 0.0.15 → 0.1.0

package/LICENSE

@@ -0,0 +1,201 @@
+                                 Apache License
+                           Version 2.0, January 2004
+                        http://www.apache.org/licenses/
+
+   TERMS AND CONDITIONS FOR USE, REPRODUCTION, AND DISTRIBUTION
+
+   1. Definitions.
+
+      "License" shall mean the terms and conditions for use, reproduction,
+      and distribution as defined by Sections 1 through 9 of this document.
+
+      "Licensor" shall mean the copyright owner or entity authorized by
+      the copyright owner that is granting the License.
+
+      "Legal Entity" shall mean the union of the acting entity and all
+      other entities that control, are controlled by, or are under common
+      control with that entity. For the purposes of this definition,
+      "control" means (i) the power, direct or indirect, to cause the
+      direction or management of such entity, whether by contract or
+      otherwise, or (ii) ownership of fifty percent (50%) or more of the
+      outstanding shares, or (iii) beneficial ownership of such entity.
+
+      "You" (or "Your") shall mean an individual or Legal Entity
+      exercising permissions granted by this License.
+
+      "Source" form shall mean the preferred form for making modifications,
+      including but not limited to software source code, documentation
+      source, and configuration files.
+
+      "Object" form shall mean any form resulting from mechanical
+      transformation or translation of a Source form, including but
+      not limited to compiled object code, generated documentation,
+      and conversions to other media types.
+
+      "Work" shall mean the work of authorship, whether in Source or
+      Object form, made available under the License, as indicated by a
+      copyright notice that is included in or attached to the work
+      (an example is provided in the Appendix below).
+
+      "Derivative Works" shall mean any work, whether in Source or Object
+      form, that is based on (or derived from) the Work and for which the
+      editorial revisions, annotations, elaborations, or other modifications
+      represent, as a whole, an original work of authorship. For the purposes
+      of this License, Derivative Works shall not include works that remain
+      separable from, or merely link (or bind by name) to the interfaces of,
+      the Work and Derivative Works thereof.
+
+      "Contribution" shall mean any work of authorship, including
+      the original version of the Work and any modifications or additions
+      to that Work or Derivative Works thereof, that is intentionally
+      submitted to Licensor for inclusion in the Work by the copyright owner
+      or by an individual or Legal Entity authorized to submit on behalf of
+      the copyright owner. For the purposes of this definition, "submitted"
+      means any form of electronic, verbal, or written communication sent
+      to the Licensor or its representatives, including but not limited to
+      communication on electronic mailing lists, source code control systems,
+      and issue tracking systems that are managed by, or on behalf of, the
+      Licensor for the purpose of discussing and improving the Work, but
+      excluding communication that is conspicuously marked or otherwise
+      designated in writing by the copyright owner as "Not a Contribution."
+
+      "Contributor" shall mean Licensor and any individual or Legal Entity
+      on behalf of whom a Contribution has been received by Licensor and
+      subsequently incorporated within the Work.
+
+   2. Grant of Copyright License. Subject to the terms and conditions of
+      this License, each Contributor hereby grants to You a perpetual,
+      worldwide, non-exclusive, no-charge, royalty-free, irrevocable
+      copyright license to reproduce, prepare Derivative Works of,
+      publicly display, publicly perform, sublicense, and distribute the
+      Work and such Derivative Works in Source or Object form.
+
+   3. Grant of Patent License. Subject to the terms and conditions of
+      this License, each Contributor hereby grants to You a perpetual,
+      worldwide, non-exclusive, no-charge, royalty-free, irrevocable
+      (except as stated in this section) patent license to make, have made,
+      use, offer to sell, sell, import, and otherwise transfer the Work,
+      where such license applies only to those patent claims licensable
+      by such Contributor that are necessarily infringed by their
+      Contribution(s) alone or by combination of their Contribution(s)
+      with the Work to which such Contribution(s) was submitted. If You
+      institute patent litigation against any entity (including a
+      cross-claim or counterclaim in a lawsuit) alleging that the Work
+      or a Contribution incorporated within the Work constitutes direct
+      or contributory patent infringement, then any patent licenses
+      granted to You under this License for that Work shall terminate
+      as of the date such litigation is filed.
+
+   4. Redistribution. You may reproduce and distribute copies of the
+      Work or Derivative Works thereof in any medium, with or without
+      modifications, and in Source or Object form, provided that You
+      meet the following conditions:
+
+      (a) You must give any other recipients of the Work or
+          Derivative Works a copy of this License; and
+
+      (b) You must cause any modified files to carry prominent notices
+          stating that You changed the files; and
+
+      (c) You must retain, in the Source form of any Derivative Works
+          that You distribute, all copyright, patent, trademark, and
+          attribution notices from the Source form of the Work,
+          excluding those notices that do not pertain to any part of
+          the Derivative Works; and
+
+      (d) If the Work includes a "NOTICE" text file as part of its
+          distribution, then any Derivative Works that You distribute must
+          include a readable copy of the attribution notices contained
+          within such NOTICE file, excluding those notices that do not
+          pertain to any part of the Derivative Works, in at least one
+          of the following places: within a NOTICE text file distributed
+          as part of the Derivative Works; within the Source form or
+          documentation, if provided along with the Derivative Works; or,
+          within a display generated by the Derivative Works, if and
+          wherever such third-party notices normally appear. The contents
+          of the NOTICE file are for informational purposes only and
+          do not modify the License. You may add Your own attribution
+          notices within Derivative Works that You distribute, alongside
+          or as an addendum to the NOTICE text from the Work, provided
+          that such additional attribution notices cannot be construed
+          as modifying the License.
+
+      You may add Your own copyright statement to Your modifications and
+      may provide additional or different license terms and conditions
+      for use, reproduction, or distribution of Your modifications, or
+      for any such Derivative Works as a whole, provided Your use,
+      reproduction, and distribution of the Work otherwise complies with
+      the conditions stated in this License.
+
+   5. Submission of Contributions. Unless You explicitly state otherwise,
+      any Contribution intentionally submitted for inclusion in the Work
+      by You to the Licensor shall be under the terms and conditions of
+      this License, without any additional terms or conditions.
+      Notwithstanding the above, nothing herein shall supersede or modify
+      the terms of any separate license agreement you may have executed
+      with Licensor regarding such Contributions.
+
+   6. Trademarks. This License does not grant permission to use the trade
+      names, trademarks, service marks, or product names of the Licensor,
+      except as required for reasonable and customary use in describing the
+      origin of the Work and reproducing the content of the NOTICE file.
+
+   7. Disclaimer of Warranty. Unless required by applicable law or
+      agreed to in writing, Licensor provides the Work (and each
+      Contributor provides its Contributions) on an "AS IS" BASIS,
+      WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or
+      implied, including, without limitation, any warranties or conditions
+      of TITLE, NON-INFRINGEMENT, MERCHANTABILITY, or FITNESS FOR A
+      PARTICULAR PURPOSE. You are solely responsible for determining the
+      appropriateness of using or redistributing the Work and assume any
+      risks associated with Your exercise of permissions under this License.
+
+   8. Limitation of Liability. In no event and under no legal theory,
+      whether in tort (including negligence), contract, or otherwise,
+      unless required by applicable law (such as deliberate and grossly
+      negligent acts) or agreed to in writing, shall any Contributor be
+      liable to You for damages, including any direct, indirect, special,
+      incidental, or consequential damages of any character arising as a
+      result of this License or out of the use or inability to use the
+      Work (including but not limited to damages for loss of goodwill,
+      work stoppage, computer failure or malfunction, or any and all
+      other commercial damages or losses), even if such Contributor
+      has been advised of the possibility of such damages.
+
+   9. Accepting Warranty or Additional Liability. While redistributing
+      the Work or Derivative Works thereof, You may choose to offer,
+      and charge a fee for, acceptance of support, warranty, indemnity,
+      or other liability obligations and/or rights consistent with this
+      License. However, in accepting such obligations, You may act only
+      on Your own behalf and on Your sole responsibility, not on behalf
+      of any other Contributor, and only if You agree to indemnify,
+      defend, and hold each Contributor harmless for any liability
+      incurred by, or claims asserted against, such Contributor by reason
+      of your accepting any such warranty or additional liability.
+
+   END OF TERMS AND CONDITIONS
+
+   APPENDIX: How to apply the Apache License to your work.
+
+      To apply the Apache License to your work, attach the following
+      boilerplate notice, with the fields enclosed by brackets "[]"
+      replaced with your own identifying information. (Don't include
+      the brackets!)  The text should be enclosed in the appropriate
+      comment syntax for the file format. We also recommend that a
+      file or class name and description of purpose be included on the
+      same "printed page" as the copyright notice for easier
+      identification within third-party archives.
+
+   Copyright 2026 Ian Nuttall
+
+   Licensed under the Apache License, Version 2.0 (the "License");
+   you may not use this file except in compliance with the License.
+   You may obtain a copy of the License at
+
+       http://www.apache.org/licenses/LICENSE-2.0
+
+   Unless required by applicable law or agreed to in writing, software
+   distributed under the License is distributed on an "AS IS" BASIS,
+   WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
+   See the License for the specific language governing permissions and
+   limitations under the License.

package/PRIVACY.md

@@ -0,0 +1,95 @@
+# Privacy policy
+
+Last updated: 10 July 2026
+
+This policy covers the official `seo` command-line tool, library, MCP server,
+and the seoskills.dev website.
+
+The current software runs on your machine. It does not create an SEO account,
+upload reports to an SEO service, or send your Google data to the project
+maintainer.
+
+## Google data the software can access
+
+Google access is optional. If you connect an account, the software asks for
+read-only access to:
+
+- your Google account email address, so the local app can identify the account
+  you connected;
+- Search Console properties, performance data, and URL Inspection data you can
+  already access; and
+- Google Analytics 4 accounts, properties, and report data you can already
+  access.
+
+The software uses this data to list properties, run the report you requested,
+join search or analytics evidence to crawl findings, and save local report
+history when a command supports it. It does not use Google data for advertising
+or to train general-purpose AI models.
+
+The shared desktop OAuth client identifies the `seo` app to Google. OAuth
+tokens and API responses are returned to your machine, not to the project
+maintainer.
+
+The use of information received from Google APIs follows the [Google API
+Services User Data Policy](https://developers.google.com/terms/api-services-user-data-policy),
+including its Limited Use requirements.
+
+## What stays on your machine
+
+The software stores project profiles, settings, OAuth tokens, caches, logs, and
+saved reports in local user directories. `seo privacy` prints the relevant
+paths and file permissions.
+
+OAuth tokens use the operating system keychain when that option is enabled.
+The fallback token file and any bring-your-own OAuth client file are written
+with user-only file permissions. You are responsible for the security of your
+device, backups, shell history, exported reports, and any environment variables
+you create.
+
+## Network requests
+
+Commands connect directly from your machine to the services needed for the
+work you request. These can include Google APIs, public pages and sitemaps you
+choose to crawl, and the npm registry for package update checks. Those services
+receive ordinary request data under their own privacy policies.
+
+The CLI does not include project-controlled usage telemetry. Installing the
+package through npm or using GitHub is covered by the policies of those
+services.
+
+The seoskills.dev host and security provider may process normal web request
+data such as an IP address, user agent, requested path, and timestamp. Website
+logs do not include the reports, tokens, or Google API responses stored by the
+local software.
+
+## Sharing and sale
+
+The project maintainer does not receive or sell the Google user data processed
+by the local software. The software sends data to Google only as needed to make
+the API request you initiated. It sends crawl requests to the public sites you
+ask it to inspect.
+
+No local report is shared with another person or service unless you export,
+copy, publish, or transmit it yourself.
+
+## Removing local data and Google access
+
+`seo auth logout` removes locally stored Google tokens. `seo reset --yes`
+removes local SEO configuration, tokens, caches, logs, and saved data managed by
+the tool.
+
+You can also revoke the app from your [Google Account connections](https://myaccount.google.com/connections).
+Deleting local files does not delete data held by Google, npm, GitHub, a site
+you crawled, or your operating system backups.
+
+## Changes to this policy
+
+This policy will change if the product starts collecting data or adds a hosted
+service. The date at the top will be updated when that happens. Earlier versions
+remain available in the public Git history.
+
+## Privacy questions
+
+Open an issue in the [public GitHub repository](https://github.com/iannuttall/seo/issues).
+Do not include OAuth tokens, private reports, personal data, or other secrets in
+a public issue.

package/README.md

@@ -1,51 +1,354 @@
-# node-seo [![Build Status](https://travis-ci.org/saschagehlich/node-seo.svg?branch=master)](https://travis-ci.org/saschagehlich/node-seo)
+<p align="center">
+  <img src="apps/web/public/favicon.svg" alt="SEO Skills CLI" width="72" height="72">
+</p>
 
-node-seo is a connect middleware that can generate, cache and serve HTML
-snapshots of single page web apps for search bots. Uses [PhantomJS](http://phantomjs.org/)
-for generating snapshots.
+<h1 align="center">SEO Skills CLI</h1>
 
-## Installation
+<p align="center">
+  Find what is costing you traffic, which pages are closest to more clicks, and what to fix first. Local SEO tools and skills for people, AI agents, and CI.
+</p>
 
-via npm:
+<p align="center">
+  <a href="#quick-start">Get started</a>
+  ·
+  <a href="https://seoskills.dev/docs">Documentation</a>
+  ·
+  <a href="https://www.npmjs.com/package/seo">npm</a>
+  ·
+  <a href="https://github.com/iannuttall/seo/issues">Questions</a>
+  ·
+  <a href="https://seoskills.dev/privacy">Privacy</a>
+  ·
+  <a href="SECURITY.md">Security</a>
+  ·
+  <a href="LICENSE">License</a>
+  ·
+  <a href="AGENTS.md">Agent notes</a>
+</p>
 
-```bash
-$ npm install seo
+<p align="center">
+  <a href="https://github.com/iannuttall/seo/actions/workflows/ci.yml"><img alt="Checks" src="https://img.shields.io/github/actions/workflow/status/iannuttall/seo/ci.yml?branch=main&label=checks&style=flat-square"></a>
+  <a href="https://www.npmjs.com/package/seo"><img alt="npm version" src="https://img.shields.io/npm/v/seo?style=flat-square"></a>
+  <a href="https://www.npmjs.com/package/seo"><img alt="npm downloads" src="https://img.shields.io/npm/dm/seo?style=flat-square"></a>
+  <img alt="Node 22 or newer" src="https://img.shields.io/badge/Node-22%2B-339933?style=flat-square">
+  <img alt="TypeScript" src="https://img.shields.io/badge/TypeScript-ready-3178c6?style=flat-square">
+  <a href="LICENSE"><img alt="Apache 2.0 license" src="https://img.shields.io/badge/license-Apache--2.0-lightgrey?style=flat-square"></a>
+</p>
+
+`seo` turns a local crawl and your own search data into work you can inspect
+and ship. Find technical blockers, recover search demand, improve pages already
+close to more clicks, and catch regressions after a release.
+
+## Quick start
+
+Requires Node 22 or newer.
+
+Install the command once, then add the skills when an agent will use it:
+
+```sh
+npm i -g seo
+npx skills add iannuttall/seo --all
+seo start
+seo report
+```
+
+The setup walks you through Google sign-in, your Search Console property, an
+optional GA4 property, and a local project profile. Public releases can include
+the shared Google app. If it is unavailable in your build, setup guides you
+through adding your own desktop OAuth client.
+
+That is the normal path. `seo` is then available in every terminal, script,
+CI job, and local MCP client on the machine.
+
+The main report uses the evidence you have, explains what it could not check,
+and recommends a short list of follow-up commands. You can start with a local
+technical report before connecting Google.
+
+## What you get
+
+- Find technical blockers across metadata, links, indexability, canonicals,
+  structured data, performance, security, mobile, international SEO, and
+  social previews.
+- Rank the work using affected URLs, rule severity, search visibility, and
+  analytics value instead of treating every warning equally.
+- See why a finding matters, what evidence supports it, how to fix it, and how
+  to verify the change.
+- Save and compare crawl reports without running the same crawl again.
+- Measure SEO changes with matched before and after Search Console windows.
+- Give scripts and agents deterministic JSON, Markdown, stable rule IDs, and a
+  compact local MCP surface.
+
+## Everyday use
+
+`seo start` can save a project profile, which is a local shortcut for a site,
+Search Console property, GA4 property, and brand terms. If you have one default
+project, most commands need no flags.
+
+```sh
+seo report
+seo refresh-priorities
+seo quick-wins
+seo second-page
+seo technical-watch
+```
+
+Use `--project` when you have more than one:
+
+```sh
+seo report --project example
+seo projects list
+```
+
+You can also work without a saved profile:
+
+```sh
+seo report --site sc-domain:example.com
+seo report --url https://example.com
+seo crawl https://example.com
+seo audit-page --url https://example.com/pricing
+```
+
+`seo report --url` crawls the site and saves technical evidence. It does not
+pretend to know traffic, queries, or rankings until you add a Search Console
+property with `seo start`.
+
+Run `seo help` for the short path or `seo help all` for the full command list.
+
+## Crawl a site
+
+Run a readable technical crawl:
+
+```sh
+seo crawl https://example.com --format pretty
+```
+
+Save it, export it, or compare it with an earlier crawl:
+
+```sh
+seo crawl https://example.com --save
+seo crawl https://example.com --format html --output report.html
+seo crawl-reports
+seo crawl-reports --compare latest --against previous
+```
+
+Useful crawl controls include `--max-pages`, `--max-depth`, `--include`,
+`--exclude`, `--no-sitemap`, `--no-external`, and `--fail-on` for CI.
+
+## Use it in CI and scripts
+
+JSON mode never prompts. Pass the site or project explicitly in unattended
+runs.
+
+```sh
+seo report --project example --json
+seo crawl https://example.com --json --output crawl.json
+seo crawl https://example.com --fail-on high --json
 ```
 
-## Configuration
+Reports keep observed data, derived findings, skipped sections, limits, and
+provider errors separate so automation can make decisions without parsing
+terminal prose.
+
+`seo report --json` returns a compact summary, action queue, and bounded crawl
+evidence so an agent can choose its next call without loading every raw report.
+Use `--full` only when a script needs the complete report object.
+
+When a CI job needs Search Console or GA4 data, give it a Google service
+account JSON key through its secret store. The service account needs access to
+the exact properties it will query. This GitHub Actions step runs without a
+browser or a copied local token:
 
-node-seo can be used as a middleware for connect/express, like this:
+```yaml
+- name: Run the SEO report
+  run: |
+    npm i -g seo
+    seo report --site sc-domain:example.com --json > seo-report.json
+  env:
+    SEO_GOOGLE_SERVICE_ACCOUNT_JSON: ${{ secrets.SEO_GOOGLE_SERVICE_ACCOUNT_JSON }}
+```
 
-```js
-var express = require('express');
-var seo  = require('seo');
-var app = express();
+The [Google data guide](https://seoskills.dev/docs/google) covers Search
+Console and GA4 permissions, mounted secret files, and how to check the active
+identity safely.
 
-app.use(new seo({
-  cacheDirectory: path.resolve(process.cwd(), '.seo-cache'),
-  routes: require('./seo-routes'),
-  requestURL: 'http://localhost:8080',
-  pageModifier: function (page, callback) {
-    // This function can be used to modify a page before it is cached
-    // `page` is an instance of PhantomJS's Page object. For an example
-    // see `test/middleware.test.js`
-  }
-}).init());
+Agents can discover and run the same report catalog as MCP without starting a
+server:
 
-app.listen(8080);
+```sh
+seo reports list --category crawl --json
+seo reports describe audit-page --json
+seo reports run audit-page --params '{"url":"https://example.com"}' --json
 ```
 
-In this case, node-seo will use `seo-routes.js` to check whether it should
-create a snapshot for the current path. This file should export a function that
-returns a boolean. The first parameter is the current request:
+Always describe a report before constructing its parameters. The CLI and MCP
+surfaces read from the same registry, so their ids and JSON Schemas cannot
+drift.
+
+## Use it with AI agents
+
+Agents work best with both parts of the project. The `seo` package runs the
+reports. The skills teach an agent which report to choose, how to read it, and
+what to verify before changing a site.
 
-```js
-module.exports = function (request) {
-  if (request.path === '/') return true;
-  return false;
-}
+```sh
+npm i -g seo
+npx skills add iannuttall/seo --all
 ```
 
-## Todo
+Then install the local stdio MCP server into a supported client:
+
+```sh
+seo mcp install
+```
+
+The prompt detects installed clients. Scripts can choose one or more explicitly:
+
+```sh
+seo mcp install --codex
+seo mcp install --claude-code
+seo mcp install --cursor
+seo mcp install --claude-desktop
+```
+
+Your client starts the server when it needs it. Run it directly only for manual
+configuration or testing:
+
+```sh
+seo mcp serve
+```
+
+The repository ships the focused instructions under `skills/`. They teach
+agents when to discover reports, inspect evidence, and request a smaller
+follow-up instead of loading a giant result into context.
+
+The npm package includes the same files for local inspection:
+
+```sh
+seo skills list
+seo skills path quick-wins
+```
+
+Agents can also discover the complete skill catalog from
+`https://seoskills.dev/.well-known/agent-skills/index.json`. Each entry links to
+the canonical skill instructions and includes a content digest for verification.
+
+See [MCP and agents](https://seoskills.dev/docs/agents) for setup and tool
+details.
+
+## Use it as a library
+
+Install the same unscoped package in any Node 22 or newer project:
+
+```sh
+npm install seo
+```
+
+Run any public report by id with the same definition, input schema, and
+evidence used by the CLI and MCP server:
+
+```ts
+import { describeReport, executeReport } from 'seo/mcp'
+
+const description = describeReport('quick-wins')
+const result = await executeReport('quick-wins', {
+  site: 'sc-domain:example.com',
+  days: 90,
+})
+
+console.log(description.inputSchema)
+console.log(result)
+```
+
+Or call typed analysis functions directly when your app already knows the job
+it needs to run:
+
+```ts
+import { auditPage, crawlSite } from 'seo'
+
+const page = await auditPage({
+  url: 'https://example.com/pricing',
+})
+
+const crawl = await crawlSite({
+  url: 'https://example.com',
+  maxPages: 100,
+  maxDepth: 4,
+})
+
+console.log(page.issues)
+console.log(crawl.summary, crawl.issueGroups)
+```
+
+The main `seo` export contains the report, provider, crawler, storage, and
+rendering APIs. `seo/mcp` exposes report discovery, report execution, and the
+embeddable MCP server. See the [TypeScript library
+guide](https://seoskills.dev/docs/library) for structured error handling,
+local Google access, and more examples.
+
+## Local data and Google access
+
+Google OAuth tokens use your system keychain when it is available. On a
+headless machine or a locked keychain, SEO Skills CLI falls back to a private
+`0600` file in your user config directory. Project profiles, crawl reports, and
+provider caches are also local. Use these commands to inspect or remove them:
+
+```sh
+seo privacy
+seo doctor
+seo auth logout
+seo reset
+```
+
+`seo auth status` shows the active storage mode. Power users can choose it with
+`seo auth storage --keychain` or `seo auth storage --file`.
+
+Power users can bring their own Google OAuth client. See
+[getting started](https://seoskills.dev/docs/getting-started) for the available
+auth paths.
+
+## Documentation
+
+Questions, bug reports, and feature requests go through
+[GitHub Issues](https://github.com/iannuttall/seo/issues). Report suspected
+vulnerabilities privately through the process in [SECURITY.md](SECURITY.md).
+
+- [Getting started](https://seoskills.dev/docs/getting-started)
+- [CLI commands](https://seoskills.dev/docs/cli)
+- [Crawler](https://seoskills.dev/docs/crawler)
+- [Reports and data](https://seoskills.dev/docs/reports)
+- [MCP and agents](https://seoskills.dev/docs/agents)
+- [AI-search evidence](https://seoskills.dev/docs/ai-search)
+- [Privacy policy](https://seoskills.dev/privacy)
+- [Terms of use](https://seoskills.dev/terms)
+- [Security policy](https://seoskills.dev/security)
+- [Contributing](CONTRIBUTING.md)
+- [Trademark and brand policy](TRADEMARKS.md)
+
+## Develop locally
+
+Most users do not need the source checkout. If you want to contribute:
+
+```sh
+git clone https://github.com/iannuttall/seo.git
+cd seo
+pnpm install
+pnpm build
+node dist/cli.js start --dry-run
+```
+
+Run the full quality gate before opening a pull request:
+
+```sh
+pnpm build
+pnpm typecheck
+pnpm test
+pnpm lint
+pnpm pack --dry-run
+```
+
+Contributor architecture and report-quality rules live in [AGENTS.md](AGENTS.md).
+
+## License
 
-* Ability to pre-render (initial rendering can take some time and we don't want to affect our search engine ranking by slow rendering times)
+The code is available under [Apache-2.0](LICENSE). Project names and artwork are
+covered separately by the [trademark and brand policy](TRADEMARKS.md).