Status: Release Candidate publication review
Verdict: BLOCKED
WarblerJS has an operational engineering release gate and RC metadata for the publishable foundation packages. All package-local typechecks and tests pass through the repository package gate, and Playground passes unified verification.
Public publication is blocked by Critical release requirements that cannot be resolved without project-owner action or controlled CI evidence:
- Approved root license text is missing.
- Security disclosure channel approval is not recorded.
- Source-first package entries for Compiler, Runtime, and HTTP require explicit RC approval or a build-output packaging pass.
- Compiler, Runtime, and HTTP do not currently define clean package build scripts.
The root package remains private and acts only as the monorepo orchestrator. It owns verification, release validation, documentation, and CI wiring.
Current release commands:
bun run verifybun run benchmarkbun run release:validatebun run release:validate:publication
| Path | Package | Classification | Status |
|---|---|---|---|
packages/core |
@warbler/core |
Publishable | RC metadata prepared; blocked by missing approved root license text. |
packages/compiler |
@warbler/compiler |
Publishable | RC metadata prepared; source-first packaging requires approval. |
packages/runtime |
@warbler/runtime |
Publishable | RC metadata prepared; source-first packaging requires approval. |
packages/http |
@warbler/http |
Publishable | RC metadata prepared; source-first packaging requires approval. |
packages/ai |
@warbler/ai |
Verified package | Package-local typecheck and tests pass. |
packages/framework |
@warbler/framework |
Verified package | Package-local typecheck and tests pass. |
playground |
warbler-playground |
Example-only | Must remain an integration consumer. |
All publishable manifests use:
- version
0.1.0-rc.0 - ESM package type
- explicit export maps
sideEffects: false- public npm access metadata
- repository, homepage, bugs, engines, and keyword metadata
Root remains private. Playground remains outside the production publication order.
Versioning policy exists in docs/VERSIONING.md.
Current policy:
- synchronized RC package version:
0.1.0-rc.0 - SemVer for public releases
- RC versions are allowed to change before stable release
- breaking changes require architecture and release-owner review
Stable cadence remains a future owner decision before 1.0.0.
Package manifests declare MIT.
Critical blocker: root LICENSE is missing. No legal text was invented. Public publication must not proceed until the project owner adds approved license text or changes package license metadata.
Third-party dependency licensing appears minimal from current manifests:
- root dev dependency:
@types/bun - package dev dependency: TypeScript and Bun types
- production internal dependencies only among Warbler packages
Formal third-party notice requirements remain subject to license-owner review.
Public API tests exist for Core, Compiler, Runtime, HTTP, and Playground boundaries.
Package exports are explicit. Internal subpaths are not package exports. HTTP now exposes ./package.json intentionally for package metadata inspection.
Core has build output under dist and publishes JS plus declarations.
Compiler, Runtime, and HTTP currently use source TypeScript runtime entry points and do not define package build scripts. TypeScript declaration output can be generated by tsc, but package manifests still use source-first entry points. This is a High RC limitation unless release owners approve source-first Bun package publication.
Verified command:
bun run verifyResult: passing.
The gate covers repository lint and format checks, all package typechecks, all package tests, Runtime certification, HTTP security/regression, Playground, production build validation, and repository validation.
Root SECURITY.md exists, but the reporting channel is a placeholder pending owner approval.
HTTP security, OWASP, fuzz, and regression tests are wired through package and repository gates. Runtime conformance and public snapshot security tests exist.
Critical blocker: public release requires an approved private vulnerability reporting channel.
bun run benchmark passes benchmark smoke validation.
Benchmark baseline marker artifacts exist:
packages/compiler/benchmarks/baseline.ci.jsonpackages/runtime/benchmarks/baseline.ci.jsonpackages/http/benchmarks/baseline.ci.json
Repository release documents exist:
CHANGELOG.mdCONTRIBUTING.mdSECURITY.mdCODE_OF_CONDUCT.mdRELEASE_CHECKLIST.mdRELEASE_NOTES_TEMPLATE.mddocs/VERSIONING.mddocs/KNOWN_LIMITATIONS.mddocs/PUBLICATION_ORDER.mddocs/VERIFICATION.mddocs/RELEASE_GATE_CHECKLIST.md
Package READMEs exist for the publishable packages.
Permanent tooling exists at scripts/release/publication-validation.ts.
The validator creates package archives in a temporary directory and attempts a temporary external Bun consumer import through documented public entry points. The final release result remains blocked while Critical blockers are present.
The publication validator inspects packed archives for:
- required package metadata
- README presence
- declaration presence
- executable source or JavaScript presence
- forbidden audit/test/security/benchmark content
- source map leakage
- secret-like file names
Archives must not publish tests, fuzz suites, benchmarks, internal audit reports, environment files, keys, or source maps.
Current supply-chain posture:
bun.lockexists and frozen install passes.- CI runs verification before benchmark and release gates.
publishConfig.provenanceis set on publishable packages.- Ordinary CI does not publish packages.
Remaining owner decisions:
- protected release branch policy
- signed tag requirement
- npm two-factor policy
- automation token scope
- release artifact retention policy
See docs/KNOWN_LIMITATIONS.md.
| Severity | Blocker | Required resolution |
|---|---|---|
| Critical | Missing approved root LICENSE |
Add owner-approved license text or update package license metadata. |
| Critical | Security disclosure channel not approved | Enable or document approved private reporting. |
| High | Source-first package entries for some packages | Approve source-first RC publication or add build-output package entries. |
| High | Missing clean build scripts for some packages | Approve source-first/no-build RC publication or add build scripts. |
- Approve license text.
- Approve vulnerability reporting channel.
- Approve synchronized versioning through RC.
- Approve source-first package publication or require build-output publication.
- Approve benchmark baseline environment and thresholds.
- Approve npm tag, expected to be
nextfor RC.
See docs/PUBLICATION_ORDER.md.
Required order:
@warbler/core@warbler/compiler@warbler/runtime@warbler/http
BLOCKED
The repository is close: engineering verification passes and RC metadata is prepared. Publication must not proceed until Critical blockers are resolved or explicitly approved as acceptable Release Candidate limitations by the project owner.