Industry Context — Common BS Fingerprints in Software, SaaS & Tech Products
Generic Claims:
the all-in-one platform, trusted by thousands of companies, increase productivity by X percent, save hours every week…
Red Flags:
AI claims without explaining what the AI does, customer logos without case study or testimonial evidence, no live product access or demo, SOC 2 claims without audit period or report availability…
Semantic Drift Patterns:
homepage claims AI-powered but product is rules-based, claims enterprise-grade but pricing page shows startup tiers only, homepage shows Fortune 500 logos but case studies are small businesses, claims all-in-one but integration page shows critical missing pieces…
Proof Expectations:
live product demo or free trial access, specific feature documentation with screenshots, verified customer logos with published case studies, third-party review scores on G2, Capterra, or TrustRadius…
containerd
(https://containerd.io) 📸 Data Snapshot: May 26, 2026Analyze the raw signals below. How would a machine score this business’s credibility?
Here are the exact signals captured from up to six pages of the site — the same raw inputs the evaluation engine analyzed. They are grouped by signal type so you can weigh each the way the machine does.
🏗️ Semantic Structure — heading hierarchy & page identity (Info Density · Commodity Fingerprint)
HOMEPAGE containerd – An industry-standard container runtime with an emphasis on simplicity, robustness and portability (https://containerd.io)
Title
containerd – An industry-standard container runtime with an emphasis on simplicity, robustness and portability
NAV_REPEATED_BODY_FOOTER containerd docs – README (https://containerd.io/docs/2.3/)
Title
containerd docs – README
H2 Announcements
H2 Getting Started
H2 Nightly builds
H2 Kubernetes (k8s) CI Dashboard Group
H2 Runtime Requirements
H2 Supported Registries
H2 Features
H2 Licenses
H2 Project details
H2 Adoption
H3 Now Recruiting
H3 Releases and API Stability
H3 CRI
H3 Communication
H3 Security audit
H3 Reporting security issues
H4 Enabling command auto-completion
H4 Distribution of ctr autocomplete for bash and zsh
H4 CRI Status
H4 Validating Your cri Setup
H4 CRI Guides
NAV_REPEATED_FOOTER containerd docs – README (https://containerd.io/docs/2.2/)
Title
containerd docs – README
H2 Announcements
H2 Getting Started
H2 Nightly builds
H2 Kubernetes (k8s) CI Dashboard Group
H2 Runtime Requirements
H2 Supported Registries
H2 Features
H2 Licenses
H2 Project details
H2 Adoption
H3 containerd v2.0 is now released!
H3 Now Recruiting
H3 Releases and API Stability
H3 CRI
H3 Communication
H3 Security audit
H3 Reporting security issues
H4 Enabling command auto-completion
H4 Distribution of ctr autocomplete for bash and zsh
H4 CRI Status
H4 Validating Your cri Setup
H4 CRI Guides
NAV_REPEATED_FOOTER containerd docs – README (https://containerd.io/docs/2.1/)
Title
containerd docs – README
H2 Announcements
H2 Getting Started
H2 Nightly builds
H2 Kubernetes (k8s) CI Dashboard Group
H2 Runtime Requirements
H2 Supported Registries
H2 Features
H2 Licenses
H2 Project details
H2 Adoption
H3 containerd v2.0 is now released!
H3 Now Recruiting
H3 Releases and API Stability
H3 CRI
H3 Communication
H3 Security audit
H3 Reporting security issues
H4 Enabling command auto-completion
H4 Distribution of ctr autocomplete for bash and zsh
H4 CRI Status
H4 Validating Your cri Setup
H4 CRI Guides
📝 The Narrative — clean text per page (Info Density · Semantic Coherence)
HOMEPAGE (https://containerd.io) containerd – An industry-standard container runtime with an emphasis on simplicity, robustness and portability
[IMG: containerd hero logo] An industry-standard container runtime with an emphasis on simplicity, robustness and portability Getting started Docs Downloadscontainerd is graduating within the CNCF!As of February 28, 2019, containerd is officially a graduated project within the Cloud Native Computing Foundation, following Kubernetes, Prometheus, Envoy, and CoreDNS. We'd like to thank the amazing containerd community for making this all possible and we're excited for the future of the project.You can read the official announcement on the CNCF website.???? [IMG: Cloud Native Computing Foundation logo] containerd is available as a daemon for Linux and Windows. It manages the complete container lifecycle of its host system, from image transfer and storage to container execution and supervision to low-level storage to network attachments and beyond. [IMG: containerd architecture diagram] FeaturesOCI Image Spec supportImage push and pull supportNetwork primitives for creation, modification, and deletion of interfacesMulti-tenant supported with CAS storage for global imagesOCI Runtime Spec support (aka runC)Container runtime and lifecycle supportManagement of network namespaces containers to join existing namespacesAdopters [IMG: icks] [IMG: gke] [IMG: cloud-foundry] [IMG: pouchcontainer] [IMG: balena] [IMG: linuxkit] [IMG: docker] [IMG: firecracker] [IMG: kata-containers] [IMG: instana] [IMG: fargate] [IMG: eks] [IMG: bottlerocket] [IMG: aks] containerd is a Cloud Native Computing Foundation graduated project [IMG: Cloud Native Computing Foundation logo]
1573 chars
SUB-PAGE (https://containerd.io/docs/2.3/) containerd docs – README
README Version: 2.3 Docs Contents Edit this page [IMG: containerd banner light mode] [IMG: containerd banner dark mode] [IMG: PkgGoDev] [IMG: Build Status] [IMG: Nightlies] [IMG: Go Report Card] [IMG: CII Best Practices] [IMG: OpenSSF Scorecard] [IMG: Check Links] containerd is an industry-standard container runtime with an emphasis on simplicity, robustness, and portability. It is available as a daemon for Linux and Windows, which can manage the complete container lifecycle of its host system: image transfer and storage, container execution and supervision, low-level storage and network attachments, etc.containerd is a member of CNCF with ‘graduated’ status.containerd is designed to be embedded into a larger system, rather than being used directly by developers or end-users. [IMG: architecture] [H2] Announcements [H3] Now Recruiting We are a large inclusive OSS project that is welcoming help of any kind shape or form:Documentation help is needed to make the product easier to consume and extend.We need OSS community outreach/organizing help to get the word out; manage and create messaging and educational content; and help with social media, community forums/groups, and google groups.We are actively inviting new security advisors to join the team.New subprojects are being created, core and non-core that could use additional development help.Each of the containerd projects has a list of issues currently being worked on or that need help resolving.If the issue has not already been assigned to someone or has not made recent progress, and you are interested, please inquire.If you are interested in starting with a smaller/beginner-level issue, look for issues with an exp/beginner tag, for example containerd/containerd beginner issues. [H2] Getting Started See our documentation on containerd.io :for ops and adminsnamespacesclient optionsTo get started contributing to containerd, see CONTRIBUTING .If you are interested in trying out containerd see our example at Getting Started . [H2] Nightly builds There are nightly builds available for download here . Binaries are generated from main branch every night for Linux and Windows.Please be aware: nightly builds might have critical bugs, it’s not recommended for use in production and no support provided. [H2] Kubernetes (k8s) CI Dashboard Group The k8s CI dashboard group for containerd contains test results regarding the health of kubernetes when run against main and a number of containerd release branches.containerd-periodics [H2] Runtime Requirements Runtime requirements for containerd are very minimal. Most interactions with the Linux and Windows container feature sets are handled via runc and/or OS-specific libraries (e.g. hcsshim for Microsoft). The current required version of runc is described in RUNC.md .There are specific features used by containerd core code and snapshotters that will require a minimum kernel version on Linux. With the understood caveat of distro kernel versioning, a reasonable starting point for Linux is a minimum 4.x kernel version.The overlay filesystem snapshotter, used by default, uses features that were finalized in the 4.x kernel series. If you choose to use btrfs, there may be more flexibility in kernel version (minimum recommended is 3.18), but will require the btrfs kernel module and btrfs tools to be installed on your Linux distribution.To use Linux checkpoint and restore features, you will need criu installed on your system. See more details in Checkpoint and Restore .Build requirements for developers are listed in BUILDING . [H2] Supported Registries Any registry which is compliant with the OCI Distribution Specification is supported by containerd.For configuring registries, see registry host configuration documentation [H2] Features For a detailed overview of containerd’s core concepts and the features it supports, please refer to the FEATURES.MD document. [H3] Releases and API Stability Please see RELEASES.md for details on versioning and stability of containerd components.Downloadable 64-bit Intel/AMD binaries of all official releases are available on our releases page .For other architectures and distribution support, you will find that many Linux distributions package their own containerd and provide it across several architectures, such as Canonical’s Ubuntu packaging . [H4] Enabling command auto-completion Starting with containerd 1.4, the urfave client feature for auto-creation of bash and zsh autocompletion data is enabled. To use the autocomplete feature in a bash shell for example, source the autocomplete/ctr file in your .bashrc, or manually like:$ source ./contrib/autocomplete/ctr [H4] Distribution of ctr autocomplete for bash and zsh For bash, copy the contrib/autocomplete/ctr script into /etc/bash_completion.d/ and rename it to ctr. The zsh_autocomplete file is also available and can be used similarly for zsh users.Provide documentation to users to source this file into their shell if you don’t place the autocomplete file in a location where it is automatically loaded for the user’s shell environment. [H3] CRI cri is a containerd plugin implementation of the Kubernetes container runtime interface (CRI) . With it, you are able to use containerd as the container runtime for a Kubernetes cluster. [IMG: cri] [H4] CRI Status cri is a native plugin of containerd. Since containerd 1.1, the cri plugin is built into the release binaries and enabled by default.The cri plugin has reached GA status, representing that it is:Feature completeWorks with Kubernetes 1.10 and abovePasses all CRI validation tests .Passes all node e2e tests .Passes all e2e tests .See results on the containerd k8s test dashboard [H4] Validating Your cri Setup A Kubernetes incubator project, cri-tools , includes programs for exercising CRI implementations. More importantly, cri-tools includes the program critest which is used for running CRI Validation Testing . [H4] CRI Guides Installing with Ansible and KubeadmFor Non-Ansible Users, Performing a Custom Installation Using the Release Tarball and KubeadmCRI Plugin Testing GuideDebugging Pods, Containers, and Images with crictlConfiguring cri PluginsConfiguring containerd [H3] Communication For async communication and long-running discussions please use issues and pull requests on the GitHub repo. This will be the best place to discuss design and implementation.For sync communication catch us in the #containerd and #containerd-dev Slack channels on Cloud Native Computing Foundation’s (CNCF) Slack - cloud-native.slack.com. Everyone is welcome to join and chat. Get Invite to CNCF Slack.Join our next community meeting hosted on Zoom. The schedule is posted on the CNCF Calendar (search ‘containerd’ to filter). [H3] Security audit Security audits for the containerd project are hosted on our website. Please see the security page at containerd.io for more information. [H3] Reporting security issues Please follow the instructions at containerd/project [H2] Licenses The containerd codebase is released under the Apache 2.0 license . The README.md file and files in the “docs” folder are licensed under the Creative Commons Attribution 4.0 International License. You may obtain a copy of the license, titled CC-BY-4.0, at http://creativecommons.org/licenses/by/4.0/ . [H2] Project details containerd is the primary open source project within the broader containerd GitHub organization. However, all projects within the repo have common maintainership, governance, and contributing guidelines which are stored in a project repository commonly for all containerd projects.Please find all these core project documents, including the:Project governance ,Maintainers ,and Contributing guidelinesinformation in our containerd/project repository. [H2] Adoption Interested to see who is using containerd? Are you using containerd in a project? Please add yourself via pull request to our ADOPTERS.md file.
7921 chars
SUB-PAGE (https://containerd.io/docs/2.2/) containerd docs – README
README Version: 2.2 Docs Contents Edit this page [IMG: containerd banner light mode] [IMG: containerd banner dark mode] [IMG: PkgGoDev] [IMG: Build Status] [IMG: Nightlies] [IMG: Go Report Card] [IMG: CII Best Practices] [IMG: OpenSSF Scorecard] [IMG: Check Links] containerd is an industry-standard container runtime with an emphasis on simplicity, robustness, and portability. It is available as a daemon for Linux and Windows, which can manage the complete container lifecycle of its host system: image transfer and storage, container execution and supervision, low-level storage and network attachments, etc.containerd is a member of CNCF with ‘graduated’ status.containerd is designed to be embedded into a larger system, rather than being used directly by developers or end-users. [IMG: architecture] [H2] Announcements [H3] containerd v2.0 is now released! See docs/containerd-2.0.md . [H3] Now Recruiting We are a large inclusive OSS project that is welcoming help of any kind shape or form:Documentation help is needed to make the product easier to consume and extend.We need OSS community outreach/organizing help to get the word out; manage and create messaging and educational content; and help with social media, community forums/groups, and google groups.We are actively inviting new security advisors to join the team.New subprojects are being created, core and non-core that could use additional development help.Each of the containerd projects has a list of issues currently being worked on or that need help resolving.If the issue has not already been assigned to someone or has not made recent progress, and you are interested, please inquire.If you are interested in starting with a smaller/beginner-level issue, look for issues with an exp/beginner tag, for example containerd/containerd beginner issues. [H2] Getting Started See our documentation on containerd.io :for ops and adminsnamespacesclient optionsTo get started contributing to containerd, see CONTRIBUTING .If you are interested in trying out containerd see our example at Getting Started . [H2] Nightly builds There are nightly builds available for download here . Binaries are generated from main branch every night for Linux and Windows.Please be aware: nightly builds might have critical bugs, it’s not recommended for use in production and no support provided. [H2] Kubernetes (k8s) CI Dashboard Group The k8s CI dashboard group for containerd contains test results regarding the health of kubernetes when run against main and a number of containerd release branches.containerd-periodics [H2] Runtime Requirements Runtime requirements for containerd are very minimal. Most interactions with the Linux and Windows container feature sets are handled via runc and/or OS-specific libraries (e.g. hcsshim for Microsoft). The current required version of runc is described in RUNC.md .There are specific features used by containerd core code and snapshotters that will require a minimum kernel version on Linux. With the understood caveat of distro kernel versioning, a reasonable starting point for Linux is a minimum 4.x kernel version.The overlay filesystem snapshotter, used by default, uses features that were finalized in the 4.x kernel series. If you choose to use btrfs, there may be more flexibility in kernel version (minimum recommended is 3.18), but will require the btrfs kernel module and btrfs tools to be installed on your Linux distribution.To use Linux checkpoint and restore features, you will need criu installed on your system. See more details in Checkpoint and Restore .Build requirements for developers are listed in BUILDING . [H2] Supported Registries Any registry which is compliant with the OCI Distribution Specification is supported by containerd.For configuring registries, see registry host configuration documentation [H2] Features For a detailed overview of containerd’s core concepts and the features it supports, please refer to the FEATURES.MD document. [H3] Releases and API Stability Please see RELEASES.md for details on versioning and stability of containerd components.Downloadable 64-bit Intel/AMD binaries of all official releases are available on our releases page .For other architectures and distribution support, you will find that many Linux distributions package their own containerd and provide it across several architectures, such as Canonical’s Ubuntu packaging . [H4] Enabling command auto-completion Starting with containerd 1.4, the urfave client feature for auto-creation of bash and zsh autocompletion data is enabled. To use the autocomplete feature in a bash shell for example, source the autocomplete/ctr file in your .bashrc, or manually like:$ source ./contrib/autocomplete/ctr [H4] Distribution of ctr autocomplete for bash and zsh For bash, copy the contrib/autocomplete/ctr script into /etc/bash_completion.d/ and rename it to ctr. The zsh_autocomplete file is also available and can be used similarly for zsh users.Provide documentation to users to source this file into their shell if you don’t place the autocomplete file in a location where it is automatically loaded for the user’s shell environment. [H3] CRI cri is a containerd plugin implementation of the Kubernetes container runtime interface (CRI) . With it, you are able to use containerd as the container runtime for a Kubernetes cluster. [IMG: cri] [H4] CRI Status cri is a native plugin of containerd. Since containerd 1.1, the cri plugin is built into the release binaries and enabled by default.The cri plugin has reached GA status, representing that it is:Feature completeWorks with Kubernetes 1.10 and abovePasses all CRI validation tests .Passes all node e2e tests .Passes all e2e tests .See results on the containerd k8s test dashboard [H4] Validating Your cri Setup A Kubernetes incubator project, cri-tools , includes programs for exercising CRI implementations. More importantly, cri-tools includes the program critest which is used for running CRI Validation Testing . [H4] CRI Guides Installing with Ansible and KubeadmFor Non-Ansible Users, Preforming a Custom Installation Using the Release Tarball and KubeadmCRI Plugin Testing GuideDebugging Pods, Containers, and Images with crictlConfiguring cri PluginsConfiguring containerd [H3] Communication For async communication and long-running discussions please use issues and pull requests on the GitHub repo. This will be the best place to discuss design and implementation.For sync communication catch us in the #containerd and #containerd-dev Slack channels on Cloud Native Computing Foundation’s (CNCF) Slack - cloud-native.slack.com. Everyone is welcome to join and chat. Get Invite to CNCF Slack.Join our next community meeting hosted on Zoom. The schedule is posted on the CNCF Calendar (search ‘containerd’ to filter). [H3] Security audit Security audits for the containerd project are hosted on our website. Please see the security page at containerd.io for more information. [H3] Reporting security issues Please follow the instructions at containerd/project [H2] Licenses The containerd codebase is released under the Apache 2.0 license . The README.md file and files in the “docs” folder are licensed under the Creative Commons Attribution 4.0 International License. You may obtain a copy of the license, titled CC-BY-4.0, at http://creativecommons.org/licenses/by/4.0/ . [H2] Project details containerd is the primary open source project within the broader containerd GitHub organization. However, all projects within the repo have common maintainership, governance, and contributing guidelines which are stored in a project repository commonly for all containerd projects.Please find all these core project documents, including the:Project governance ,Maintainers ,and Contributing guidelinesinformation in our containerd/project repository. [H2] Adoption Interested to see who is using containerd? Are you using containerd in a project? Please add yourself via pull request to our ADOPTERS.md file.
7988 chars
SUB-PAGE (https://containerd.io/docs/2.1/) containerd docs – README
README Version: 2.1 Docs Contents Edit this page [IMG: containerd banner light mode] [IMG: containerd banner dark mode] [IMG: PkgGoDev] [IMG: Build Status] [IMG: Nightlies] [IMG: Go Report Card] [IMG: CII Best Practices] [IMG: OpenSSF Scorecard] [IMG: Check Links] containerd is an industry-standard container runtime with an emphasis on simplicity, robustness, and portability. It is available as a daemon for Linux and Windows, which can manage the complete container lifecycle of its host system: image transfer and storage, container execution and supervision, low-level storage and network attachments, etc.containerd is a member of CNCF with ‘graduated’ status.containerd is designed to be embedded into a larger system, rather than being used directly by developers or end-users. [IMG: architecture] [H2] Announcements [H3] containerd v2.0 is now released! See docs/containerd-2.0.md . [H3] Now Recruiting We are a large inclusive OSS project that is welcoming help of any kind shape or form:Documentation help is needed to make the product easier to consume and extend.We need OSS community outreach/organizing help to get the word out; manage and create messaging and educational content; and help with social media, community forums/groups, and google groups.We are actively inviting new security advisors to join the team.New subprojects are being created, core and non-core that could use additional development help.Each of the containerd projects has a list of issues currently being worked on or that need help resolving.If the issue has not already been assigned to someone or has not made recent progress, and you are interested, please inquire.If you are interested in starting with a smaller/beginner-level issue, look for issues with an exp/beginner tag, for example containerd/containerd beginner issues. [H2] Getting Started See our documentation on containerd.io :for ops and adminsnamespacesclient optionsTo get started contributing to containerd, see CONTRIBUTING .If you are interested in trying out containerd see our example at Getting Started . [H2] Nightly builds There are nightly builds available for download here . Binaries are generated from main branch every night for Linux and Windows.Please be aware: nightly builds might have critical bugs, it’s not recommended for use in production and no support provided. [H2] Kubernetes (k8s) CI Dashboard Group The k8s CI dashboard group for containerd contains test results regarding the health of kubernetes when run against main and a number of containerd release branches.containerd-periodics [H2] Runtime Requirements Runtime requirements for containerd are very minimal. Most interactions with the Linux and Windows container feature sets are handled via runc and/or OS-specific libraries (e.g. hcsshim for Microsoft). The current required version of runc is described in RUNC.md .There are specific features used by containerd core code and snapshotters that will require a minimum kernel version on Linux. With the understood caveat of distro kernel versioning, a reasonable starting point for Linux is a minimum 4.x kernel version.The overlay filesystem snapshotter, used by default, uses features that were finalized in the 4.x kernel series. If you choose to use btrfs, there may be more flexibility in kernel version (minimum recommended is 3.18), but will require the btrfs kernel module and btrfs tools to be installed on your Linux distribution.To use Linux checkpoint and restore features, you will need criu installed on your system. See more details in Checkpoint and Restore .Build requirements for developers are listed in BUILDING . [H2] Supported Registries Any registry which is compliant with the OCI Distribution Specification is supported by containerd.For configuring registries, see registry host configuration documentation [H2] Features For a detailed overview of containerd’s core concepts and the features it supports, please refer to the FEATURES.MD document. [H3] Releases and API Stability Please see RELEASES.md for details on versioning and stability of containerd components.Downloadable 64-bit Intel/AMD binaries of all official releases are available on our releases page .For other architectures and distribution support, you will find that many Linux distributions package their own containerd and provide it across several architectures, such as Canonical’s Ubuntu packaging . [H4] Enabling command auto-completion Starting with containerd 1.4, the urfave client feature for auto-creation of bash and zsh autocompletion data is enabled. To use the autocomplete feature in a bash shell for example, source the autocomplete/ctr file in your .bashrc, or manually like:$ source ./contrib/autocomplete/ctr [H4] Distribution of ctr autocomplete for bash and zsh For bash, copy the contrib/autocomplete/ctr script into /etc/bash_completion.d/ and rename it to ctr. The zsh_autocomplete file is also available and can be used similarly for zsh users.Provide documentation to users to source this file into their shell if you don’t place the autocomplete file in a location where it is automatically loaded for the user’s shell environment. [H3] CRI cri is a containerd plugin implementation of the Kubernetes container runtime interface (CRI) . With it, you are able to use containerd as the container runtime for a Kubernetes cluster. [IMG: cri] [H4] CRI Status cri is a native plugin of containerd. Since containerd 1.1, the cri plugin is built into the release binaries and enabled by default.The cri plugin has reached GA status, representing that it is:Feature completeWorks with Kubernetes 1.10 and abovePasses all CRI validation tests .Passes all node e2e tests .Passes all e2e tests .See results on the containerd k8s test dashboard [H4] Validating Your cri Setup A Kubernetes incubator project, cri-tools , includes programs for exercising CRI implementations. More importantly, cri-tools includes the program critest which is used for running CRI Validation Testing . [H4] CRI Guides Installing with Ansible and KubeadmFor Non-Ansible Users, Preforming a Custom Installation Using the Release Tarball and KubeadmCRI Plugin Testing GuideDebugging Pods, Containers, and Images with crictlConfiguring cri PluginsConfiguring containerd [H3] Communication For async communication and long-running discussions please use issues and pull requests on the GitHub repo. This will be the best place to discuss design and implementation.For sync communication catch us in the #containerd and #containerd-dev Slack channels on Cloud Native Computing Foundation’s (CNCF) Slack - cloud-native.slack.com. Everyone is welcome to join and chat. Get Invite to CNCF Slack.Join our next community meeting hosted on Zoom. The schedule is posted on the CNCF Calendar (search ‘containerd’ to filter). [H3] Security audit Security audits for the containerd project are hosted on our website. Please see the security page at containerd.io for more information. [H3] Reporting security issues Please follow the instructions at containerd/project [H2] Licenses The containerd codebase is released under the Apache 2.0 license . The README.md file and files in the “docs” folder are licensed under the Creative Commons Attribution 4.0 International License. You may obtain a copy of the license, titled CC-BY-4.0, at http://creativecommons.org/licenses/by/4.0/ . [H2] Project details containerd is the primary open source project within the broader containerd GitHub organization. However, all projects within the repo have common maintainership, governance, and contributing guidelines which are stored in a project repository commonly for all containerd projects.Please find all these core project documents, including the:Project governance ,Maintainers ,and Contributing guidelinesinformation in our containerd/project repository. [H2] Adoption Interested to see who is using containerd? Are you using containerd in a project? Please add yourself via pull request to our ADOPTERS.md file.
7988 chars
🛡️ Trust Signals — reviews, proof links, trust-theatre flag (Trust & Proof)
0Review mentions (all pages)
0External proof links (all pages)
| Page | Reviews | Proof links |
|---|---|---|
| / (home) | 0 | 0 |
| /docs/2.3/ | 0 | 0 |
| /docs/2.2/ | 0 | 0 |
| /docs/2.1/ | 0 | 0 |
🔗 Identity & Technical Layer — schema JSON-LD: identity chains, entity gaps (Identity & Authority)
Homepage — no schema detected (entity gap)
/docs/2.3/ — no schema detected (entity gap)
/docs/2.2/ — no schema detected (entity gap)
/docs/2.1/ — no schema detected (entity gap)
Your Diagnosis
Before revealing the machine’s verdict, predict the BS score for each signal. Higher = more BS (more fluff, less verifiable substance). Drag each slider, then submit to compare your judgment against the engine.
Information Density
0 / 30
Read the Narrative & headings: do hard facts (prices, dates, numbers) outweigh fluff power-words?
Semantic Coherence
0 / 20
Compare the homepage promise against the sub-page reality. Do they hold the same line?
Trust & Proof
0 / 20
Weigh review mentions against actual external proof links. Claims without verification = theatre.
Commodity Fingerprint
0 / 15
Check headings & narrative against the industry clichés in the setup above.
Identity & Authority
0 / 15
Inspect the schema: is there real Organization/Person identity with sameAs links, or gaps?
Your predicted BS score
0 / 100
Stuck? Reveal the heuristic lens — how the deterministic page-auditor reads each signal (no AI, pure pattern rules)
These are the structural rules a local, deterministic auditor applies — the same lens you can use to judge each signal. They describe what to look for, not this company’s result.
Information Density
Classify each sentence as substantive or hollow. Grounding markers — numbers, currencies, dates, technical units, named entities — outweigh marketing adjectives. When fluff sits right next to hard evidence, the fluff is forgiven.
Semantic Alignment
Pull the main entities out of the H1, then check whether they actually recur through the body. A page that announces one thing and then talks about another drifts. Headings with no real sentences underneath read as pseudo-substance.
Trust & Proof
Count trust words (review, testimonial, rating, verified) against real outbound proof links (Google, Trustpilot, Clutch, G2, Yelp). Lots of trust language with zero verification links is trust theatre. Unlinked logo galleries count against it.
Commodity Fingerprint
Look at how much sentence length varies. Natural writing varies its rhythm; templated or mass-produced copy is statistically uniform. Very low variation reads as commodity content — unless unique named entities break the pattern.
Identity & Authority
Inspect the JSON-LD. Is there an Organization or Person schema, and does it carry sameAs links to real external profiles (LinkedIn, socials)? Missing schema or no identity declaration signals an anonymous entity.
Want to apply this lens yourself? The free BS Indicator Chrome extension runs these heuristic checks live on any page. Bear in mind it is a single-page, deterministic tool — it relies only on pattern rules for the page in front of it and does not perform the cross-page semantic correlation this audit uses, so its readout is a starting lens, not the full verdict.
B
BS Level
Software, SaaS & Tech Products
33.2 Avg BS
Based on 1130 businesses audited.
✓ Less BS than average
containerd has 27.2 points less BS than the average for Software, SaaS & Tech Products.
BS Detector
Software, SaaS & Tech Products BS: containerd (containerd.io)
https://containerd.io
📍 Industry: Software, SaaS & Tech Products
6
BS / 100
This is a benchmark for low-BS technical communication, prioritizing utility over conversion. It is a pure infrastructure site that assumes a high level of user competence and provides the specific evidence required for technical adoption. The only minor flaw is the preservation of a 7-year-old graduation notice as the primary homepage announcement.
Info Density
Power-words vs. Substance ratio.
2
7% BS
Semantic Coherence
Homepage promise vs. Sub-page reality.
0
0% BS
Trust & Proof
Verifiable evidence vs. Trust Theatre.
1
5% BS
Commodity Fingerprint
Detection of industry clichés/templates.
1
7% BS
Identity & Authority
Expert verifiability & Schema depth.
2
13% BS
Update the homepage hero announcement to reflect the current versioning and recent 2.x milestones rather than the 2019 graduation. Implement Organization and SoftwareApplication schema to improve machine-readable identity. Include direct links from the Adopters logo wall to specific documentation or external case studies where containerd is cited as the runtime. Add a dedicated Security page summary to the homepage to bridge the gap between the hero and the footer security links.
The website perfectly aligns with the Software, SaaS and Tech Products category, specifically focusing on cloud-native infrastructure and container runtimes. The content is deeply technical, focusing on OCI specifications, daemon availability for Linux and Windows, and integration with the Cloud Native Computing Foundation (CNCF).
“The exceptionally low score of 6 is driven by the total lack of marketing fluff (0 points in Semantic Coherence) and the high specificity of the technical content. Minor points were added for the absence of structured data (Identity) and the presence of stale 2019 news as a primary signal, alongside standard but justified industry jargon.”
Verified Analysis Date: May 26, 2026
© 1EuroSEO Independent Evaluator — Non-Sponsored Result
Analysis Disclosure & Source Attribution
This training module utilizes a snapshot of public data from containerd, captured on May 26, 2026, to demonstrate how machine logic evaluates different types of business narratives.
Purpose: This data is presented under “Fair Use” / “Educational Exception” for the purpose of forensic semantic analysis, allowing users to compare human intuition against machine-generated evaluations.
Notice to containerd: This analysis is part of a non-adversarial audit conducted by 1 Euro SEO. The results provided by 1EuroSEO are intended as professional feedback to help improve any website’s machine-readability and authority signals. The 1EuroSEO BS Detection Tool is a free tool, and anyone can test any company to see how their content is interpreted by AI models.
Any company can use the insights for free and improve its voice by comparing it to industry clichés or competitors. When a company has updated its content, it can always submit a new audit request, which will be reflected in a new current score.
To all users: You are encouraged to visit the live site at https://containerd.io to view the most current version of its content and learn from the source what this company is about and what it offers.