inspect.software

Press & brand assets

Logos, colours, boilerplate texts and usage rules for inspect.software — the media kit for journalists, directories, conference organizers and integration documentation.

Updated 2026-08-27

Everything on this page may be used to refer to inspect.software in editorial coverage, conference material, directories, and documentation that mentions the record. The assets are generated from the running site, so what is downloaded here is what appears in the header.

The lockup is the primary form: the mark and the name together. The mark alone is for contexts where the name is already established — avatars, app tiles, favicons.

The inspect.software lockup on a light background
LockupLight backgroundsSVGPNG 1024PNG 2048
The inspect.software lockup on a dark background
Lockup on darkDark backgroundsSVGPNG 1024PNG 2048
The inspect.software mark
MarkAvatars, tiles, faviconsSVGPNG 256PNG 512PNG 1024
The inspect.software wordmark
WordmarkWhere a mark already appearsSVGBlackWhite
The one-colour inspect.software lockup in black
One colourPrint, embossing, engravingLockupMark
The one-colour inspect.software lockup in white
One colour, reversedOver photography or solid colourLockupMark

Every file above, together with a short usage summary: inspect-software-press-kit.zip.

Using the assets

  • Keep the proportions. Scale the files; do not redraw, stretch, rotate, or rebuild the lockup from its parts.
  • Keep the colours. The full-colour files are for colour reproduction; the one-colour files are for everything else. No other recolouring.
  • Leave clear space. At least the height of the mark on every side, free of type, rules, and other logos.
  • Respect the minimum size. The lockup stays legible down to a mark height of 16 pixels; below that, the mark alone.
  • No effects. No shadows, outlines, gradients, glows, or containers added on top of what the files already carry.
  • No implied endorsement. The assets identify inspect.software. They do not signal a partnership, a certification, or an approval of the material they appear in.
△
The badge and the certification seal are not brand assets. A badge states one repository's inspected result, and a seal states its certification level. Both are certification marks, carried only by the repository that earned them, and neither may be used as decoration or as a general logo for inspect.software.

Colour

Ink#0F2335 Green#25A86F Green on dark#3FD39A Blue#3868FF Ground#F6F9FF

Ink carries the name, green carries the domain, and blue is reserved for links and interactive elements. The band colours that appear in reports — from exceptional deep green to critical red — belong to the rating scale and are documented there.

Typography

The site is set in Geist and Geist Mono, both under the SIL Open Font License. The wordmark files carry outlines rather than live text, so no font installation is required to reproduce them.

The name

inspect.software is written as one word, lowercase, always with the dot — including at the start of a sentence. Not Inspect Software, not Inspect.Software, not inspect-software outside of a URL or an account handle. On first mention in prose, "the public record inspect.software" reads naturally and avoids a sentence opening on a lowercase word.

Boilerplate

Approved descriptions, in three lengths. Shortening one further risks losing the qualifications that make it accurate.

One line

inspect.software keeps a public record of open-source software health.

Short

inspect.software is an independent public record of open-source software health. Every repository is assessed by the same published, versioned methodology, spanning maintainability, engineering quality, security posture, ecosystem adoption, and governance. The scanner that produces the results is open source, each report carries the evidence behind it, and no payment can change an outcome.

Long

inspect.software is an independent public record of open-source software health. Modern software is assembled from thousands of open-source dependencies, yet the signals available for judging them are weak: stars measure popularity rather than health, and a package with millions of weekly downloads maintained by a single volunteer looks, from the outside, like any other.

The record inspects repositories against one published, versioned methodology, spanning maintainability, engineering quality, security posture, ecosystem adoption, and governance, and publishes each result as a report, a health index, and an embeddable badge. Weights, formulas and thresholds are documented, the production scanner is released under the AGPL, and every report carries the observed evidence, so any figure can be checked by hand or recomputed from the published code. Results are signals rather than warranties, and no commercial relationship can change one.

Facts

  • What it is — a public record of open-source software health, published as reports, health indices, and badges.
  • Methodology — one published, versioned specification; see methodology for the current version and its full text.
  • Scanner — AGPL-licensed and public at inspect-software/scanner.
  • Independence — results are independent of payment; see certification & pricing.
  • Operator — Vitalii Stepanenko, València, Spain; full identification in section 10 of the terms.
  • Corpus size — deliberately not stated here, because it changes daily. The current figures are on the front page and in the public /api/stats endpoint.

Contact

Press enquiries, interview requests, and questions about a published result: mail@inspect.software, with press in the subject line.

Corrections to a specific report follow the data corrections route instead, which triggers a re-scan when an error is confirmed.