Skip to content

Clarify security expectations for third-party Features and Templates - #758

Open
Abdurrahmaan Iqbal (abdurriq) wants to merge 3 commits into
gh-pagesfrom
docs/third-party-content-notice
Open

Abdurrahmaan Iqbal (abdurriq) wants to merge 3 commits into
gh-pagesfrom
docs/third-party-content-notice

Conversation

@abdurriq

@abdurriq Abdurrahmaan Iqbal (abdurriq) commented Nov 20, 2026 •

Copy link
Copy Markdown
Contributor

What type of PR is this?

  • Add a new dev container collection
  • Update to an existing dev container collection
  • Documentation/spec update
  • Other containers.dev site update (UX, layout, etc)

Related Issues

Related to #755, #756, and devcontainers/crawler#23.

Description

Add a prominent "Third-Party Content" notice after the introduction and before search and the catalog on the Features, Templates, and Collections pages. This makes the trust boundary visible where users discover content, rather than only after a Feature has been blocked.

The notice explains that community-contributed content is maintained by its publishers, index inclusion does not imply security review or endorsement of the code or subsequent updates, and Features and Templates can cause code to execute in a dev container environment. It advises users to use publishers they trust, review the source and configuration, and assess suitability and security risks for their environment.

No changes to crawler behavior, registration requirements, or dependencies. The disallowed-Features page from #756 is not yet on the base branch and is not included in this change.

Screenshots

The Features page is shown below; the same warning appears on Templates and Collections.

Desktop (1000px)

Desktop Features page showing the third-party content warning above search and the catalog

Mobile (390px)

Mobile Features page showing the complete third-party content warning wrapped within the viewport

Validation

  • Built the site with the locked dependencies and Jekyll 3.9.3 under Ruby 3.2 in Docker. The host Ruby 3.4 is incompatible with the locked Nokogiri version.
  • Checked the generated HTML for the notice on all three pages and verified that it precedes search.
  • Checked identical wording and placement before the catalog in all three source pages.
  • git diff --check passed.

This branch has not been deployed

No deployments
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant