synrc/rpc

This system is an Erlang-based RPC framework that generates serialization and validation code for multiple languages, including JavaScript, Swift, and Google Protobuf, from Erlang type specifications. It provides a core code generation engine alongside a BEAM protocol decoder and encoder library for Swift. The project also includes documentation and sample implementations to demonstrate the integration of these generated components.

New HTML documentation pages have been added for the bert\_google, bert\_javascript, bert\_swift, and bert\_validator modules, providing user-facing descriptions of their respective encoder/decoder capabilities for GRPC, JavaScript, Swift, and Erlang.

man · high confidence

This change introduces the initial version of the RPC project, an Erlang-based SDK that generates encode/decode code for JavaScript, Swift, and Google Protobuf from Erlang HRL type specifications. The release includes the core generator modules (bert\_javascript, bert\_google, bert\_validator), a Travis CI configuration for Erlang 20-23, and a static website (index.html) with documentation and samples. It also sets up standard repository metadata including .gitignore, .gitattributes, LICENSE, and CNAME.

(repo-wide) · high confidence

This change introduces the core Bert RPC application, providing a parse-transform-based system that automatically generates serialization, validation, and client-side model code for Erlang records. The framework now supports generating JavaScript encoders/decoders (bert\_javascript), Swift models and decoders (bert\_swift), and Google Protobuf definitions (bert\_google) from Erlang source. It also includes a bert\_validator module that generates compile-time validation logic for record fields, and a bert\_sample demonstrating the integration. The application is initialized via the bert supervisor and is versioned at 4.11.1.

src · high confidence

This change adds the \macbert\ library to the private section, providing Swift-based serialization and deserialization for the BEAM (Erlang) protocol. The implementation includes model classes for standard response types (\ok\, \error\, \io\), a \Decoder\ to parse incoming BEAM tuples into these models, and an \Encoder\ to serialize application objects (such as \Auth\, \Confirm\, and \Contact\) into BEAM format. The library also features a type specification system (\TypeSpec\) for handling various BEAM data types like atoms, binaries, and lists, along with corresponding test specifications to validate the parsing logic.

priv · high confidence

Added \include/bert.hrl\ and \include/sample.hrl\ to the project. The \bert.hrl\ header defines the \DISDEF\ macro and configuration paths for JavaScript, Java, Swift, Google Protobuf, and Erlang assets via application environment variables. The \sample.hrl\ header introduces a comprehensive set of type definitions and record structures for the application's domain model, including records for Messages, Auth, Services, Members, Rooms, Contacts, Rosters, and Profiles, along with associated status and type enums.

include · high confidence

The initial implementation files for the macbert module have been removed, including Model.swift, Parser.swift, Spec.swift, and main.swift. This deletes the early data model definitions, the BEAM term parser logic, and the entry point that executed the initial test suite.

macbert · high confidence

Written by watchdog.canine.dev from the codebase's own history, inside the signed delivery this page is composed from.

• CAI 50 → 48 (-2.7)
• Rubric changed (rubric-2026.09.12 → rubric-2026.09.18) — scores are not directly comparable.

• Code Health 100 → 100 (+0.0)
• Architecture 100 → 100 (+0.0)
• Maturity 56 → 56 (+0.0)
• Readiness 61 → 45 (-15.8)
• Security 65 → 74 (+8.8)
• Accessibility 35 → 35 (+0.0)

• Coverage not measured — no coverage collector is wired up
• Documentation: no architecture or design documentation (README.md)

Written by watchdog.canine.dev from the codebase's own history, inside the signed delivery this page is composed from.

synrc/rpc was measured the same way every project in this corpus was: the same rubric, at a pinned commit, with the result published in full. Point a surveyor at a repository you know and see whether you agree with it.