A single timeline of what’s queued for the next release and what shipped historically —
cross-referencing CHANGELOG.md (the authoritative record of what changed) against
git tags (when it was actually released).
@owasp-webshield/core / @owasp-webshield/reactFull contents are in CHANGELOG.md’s [1.0.0] entry; in short:
createOwlClient() + <OwlProvider> — convenience wrappers collapsing manual manager
wiring and 4-level provider nesting into one call/component each.CryptoManager.Live on npm:
@owasp-webshield/core@1.0.0 — tag core-v1.0.0, published via .github/workflows/release.yml.React adapter: @owasp-webshield/react@1.0.0 — tag react-v1.0.0, published via .github/workflows/release-react-adapter.yml, first-ever publish for this package.
.github/workflows/release-owl-todo-app.yml, an anonymous netlify-cli deploy --allow-anonymous on every push to main (no Netlify account/secrets needed). Caveat: the URL changes on every deploy since no site is linked (see docs/todo-app-deployment.md) — a permanent “Try it live” README badge isn’t viable until that’s switched to an authenticated, pinned-site deploy..d.ts ships today despite "typescript" in package.json keywords.@owasp-webshield/vue/@owasp-webshield/angular under the current naming scheme.A browser-safe package . root for real encryption — today CryptoManager is a throwing stub in the browser build
docs/github-actions-security-gate.md currently documents a pattern, not a reusable action; owl-enabled-node-secrets-app’s NpmAuditProvider (a real npm audit-backed DependencyRiskScanner provider) is a candidate to upstream into the core package, since today DependencyRiskScanner ships with no built-in provider at all.