POST: you probably don't need hardened container images when you can already secure what you have.

Open
#25 3 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
3/5
Estimated time
3-5 days
Newbie friendliness
35/100
Issue type
Documentation
Clarity
Mostly clear
Activity status
Stale
Domain
content

Research direction

Review the existing Docusaurus and Markdown-based site structure to find where blog posts are stored and how they are formatted. Define the post's scope around securing existing container images, then draft and add the article in the repository's established style; done means the post is complete and renders correctly with the site's content checks.

Written by the indexing model from the issue text.

Description

blog

From @prabhu
Blog proposal: you probably don't need hardened container images when you can already secure what you have.

Dominant language
JavaScript
Stars
9
Forks
18
PR merge metrics
No merged PRs in 30d

Getting set up

This project ships no dev container, Dockerfile or contributing guide, so setting up is up to you: start from its README, and see our first-contribution guide for the general steps.

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from aboutcode-org/www.aboutcode.org

All issues in aboutcode-org/www.aboutcode.org

Similar issues

More JavaScript issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.