Azle Nears 1.0 as Demergent Labs Calls for Community Security Review

Demergent Labs has announced that Azle, its TypeScript CDK for the Internet Computer, has reached the release candidate stage and is edging closer to version 1.0. The milestone signals growing confidence that Azle can be relied upon as a production-ready toolkit for developers building on ICP.

Jordan Last, who leads Demergent Labs and has been building both Azle and Kybra since 2022 under a DFINITY grant, is now inviting the developer community to participate in a security review. The team has already begun extensive internal checks, but Last says outside eyes are crucial before the final release.

The invitation is open to anyone willing to contribute, regardless of depth or technical capacity. Those who take part are asked to follow Azle’s official security policy, keeping sensitive findings private until they can be addressed. While no monetary rewards are being offered, Demergent Labs is open to crediting contributors in the Azle GitHub repository, either by name or anonymously, once reviews are completed and findings resolved.

Last emphasised that the team is prepared to work closely with volunteers, guiding them through the codebase and answering questions. For developers curious about the inner workings of CDKs and SDKs, he sees it as a chance for direct engagement and hands-on experience.

Azle’s source code and documentation are available publicly, with particular focus on the stable mode components that underpin much of its functionality. Interested contributors are encouraged to reach out to Last through email or his social channels for further collaboration.

The move reflects an open-source ethos that Demergent Labs has maintained throughout the development of its tools. While the lack of formal bug bounty incentives may limit participation, the project’s transparent approach and promise of recognition are aimed at encouraging developers who want to shape a tool they may themselves depend on.

As Azle approaches its 1.0 release, the coming weeks will determine how robust the community-driven security checks prove to be. For the developers behind it, the process is less about polish and more about ensuring that when Azle finally arrives in production form, it can withstand the scrutiny of the wider ICP ecosystem.