Stack preferences — choose your preferred language and framework
OWASP Top 10 coverage across Web, API, Mobile, and Client-Side categories
The beginning
How we ship at SecureCodingHub
Our release cadence is roughly monthly, but the underlying rhythm is driven by what is ready rather than the calendar. A patch release goes out when we have collected enough bug fixes, copy corrections, or small accessibility refinements to justify a deploy. A minor release usually bundles improvements to an existing area of the product, for example better feedback inside an existing challenge type or a smoother flow through the learner dashboard. A feature release is reserved for changes that materially expand what the platform can do, such as adding a new vulnerability class, supporting a new language across the challenge library, or introducing a new reporting view for security leads.
Customer feedback enters the roadmap through two channels. The first is direct conversation with security teams who use SecureCodingHub day to day; the second is structured feedback collected inside the product after a learner completes a challenge. We read every comment. Recurring patterns surface in our planning sessions and turn into concrete work items, which is why so many of the entries on this page begin with a small problem report we received the week before. To follow along as new entries appear, you can subscribe to release notes from the blog, where each significant release is mirrored as a short post with the context behind it.
What shipping means for a content-heavy product
Not every change shows up here. SecureCodingHub is a content-heavy product, which means a large share of our weekly work is about expanding and refreshing the learning material itself: new challenge languages, new vulnerability classes, and updates that track moving regulatory baselines like PCI DSS revisions or refreshed OWASP guidance. These content updates ship continuously and do not receive a version bump unless they change platform behavior in a way that a returning learner or administrator would actually notice.
If you want a fuller view of the editorial side of the roadmap, the guides library is the best place to look. The changelog focuses on platform-level changes, while the guides reflect the steady, week-by-week growth of the knowledge base behind the challenges.