GitHub Actions go live on November 13th and we’re in the last 2 weeks of the beta.

Being part of the GitHub Actions beta program allowed us to create our CodeNotary commit authentication for the GitHub Actions marketplace. Now its ready and tested and everyone can use for free:

GitHub Actions GA free quantities

The following email reached us and informs about the free quantities and where to find pricing as well, if you go beyond these limits.

We wanted to let you know that these services will still be free for open source and include free quantities, and that overages will become paid services on November 13. You can continue to use these services with no changes to your existing workflows. If you’d like to use Actions and Package Registry beyond the included limits, you will need to enable overages, since we will not charge you without your consent, even if you’ve been using similar levels of service quantities during the beta programs.


The pricing page can be found here:

GitHub Actions marketplace

You can find the GitHub Action in the marketplace: CodeNotary Verify Commit

GitHub Action to verify commits

Verify the authenticity of your commits with

Using the Verify commit action, you can sign your work locally using the CodeNotary vcn command line (ie. vcn notarize git://.). This action will verify these signatures so other people will know that your commits come from a trusted source.

Whenever you release a new commit, the verification check will be triggered and everyone can be sure its trusted by the maintainer. You can simply click on every checkmark of the commit to see the details.

CodeNotary GitHub action


verify commit action integration

Create a workflow .yml file in your repositories .github/workflows directory (eg. .github/workflows/verify.yml). In your workflow you first need to checkout your repository then use this action:

name: CodeNotary

on: [push]


runs-on: ubuntu-latest

 - name: Checkout
   uses: actions/checkout@master

 - name: Verify
   uses: vchain-us/verify-action@master

For more details, see Contexts and expression syntax for GitHub Actions


See action.yml.

Available inputs

  • signerID – List of SignerID(s) (separated by space) to authenticate against. A SignerID is the signer’s public address (represented as a 40 hex characters long string prefixed with 0x).
  • org – Organization’s ID to authenticate against. Note that org takes precedence over signerID
  • path – Path to git working directory. Default to the current directory.


 - name: Verify
   uses: vchain-us/verify-action@master
     signerID: <a trusted signer ID>
     org: <a trusted organization>
     path: <path to your repository, if not the current directory>

Sign / Notarize your Git Commit

Please check the vcn repository to learn more about how you can notarize your commits, so the checks pass.


You can find the sourcecode of the GitHub action in our GitHub repository:

Metrics and Logs

(formerly, Opvizor Performance Analyzer)

VMware vSphere & Cloud

Monitor and Analyze Performance and Log files:
Performance monitoring for your systems and applications with log analysis (tamperproof using immudb) and license compliance (RedHat, Oracle, SAP and more) in one virtual appliance!

Subscribe to Our Newsletter

Get the latest product updates, company news, and special offers delivered right to your inbox.

Subscribe to our newsletter

Use Case - Tamper-resistant Clinical Trials


Blockchain PoCs were unsuccessful due to complexity and lack of developers.

Still the goal of data immutability as well as client verification is a crucial. Furthermore, the system needs to be easy to use and operate (allowing backup, maintenance windows aso.).


immudb is running in different datacenters across the globe. All clinical trial information is stored in immudb either as transactions or the pdf documents as a whole.

Having that single source of truth with versioned, timestamped, and cryptographically verifiable records, enables a whole new way of transparency and trust.

Use Case - Finance


Store the source data, the decision and the rule base for financial support from governments timestamped, verifiable.

A very important functionality is the ability to compare the historic decision (based on the past rulebase) with the rulebase at a different date. Fully cryptographic verifiable Time Travel queries are required to be able to achieve that comparison.


While the source data, rulebase and the documented decision are stored in verifiable Blobs in immudb, the transaction is stored using the relational layer of immudb.

That allows the use of immudb’s time travel capabilities to retrieve verified historic data and recalculate with the most recent rulebase.

Use Case - eCommerce and NFT marketplace


No matter if it’s an eCommerce platform or NFT marketplace, the goals are similar:

  • High amount of transactions (potentially millions a second)
  • Ability to read and write multiple records within one transaction
  • prevent overwrite or updates on transactions
  • comply with regulations (PCI, GDPR, …)


immudb is typically scaled out using Hyperscaler (i. e. AWS, Google Cloud, Microsoft Azure) distributed across the Globe. Auditors are also distributed to track the verification proof over time. Additionally, the shop or marketplace applications store immudb cryptographic state information. That high level of integrity and tamper-evidence while maintaining a very high transaction speed is key for companies to chose immudb.

Use Case - IoT Sensor Data


IoT sensor data received by devices collecting environment data needs to be stored locally in a cryptographically verifiable manner until the data is transferred to a central datacenter. The data integrity needs to be verifiable at any given point in time and while in transit.


immudb runs embedded on the IoT device itself and is consistently audited by external probes. The data transfer to audit is minimal and works even with minimum bandwidth and unreliable connections.

Whenever the IoT devices are connected to a high bandwidth, the data transfer happens to a data center (large immudb deployment) and the source and destination date integrity is fully verified.

Use Case - DevOps Evidence


CI/CD and application build logs need to be stored auditable and tamper-evident.
A very high Performance is required as the system should not slow down any build process.
Scalability is key as billions of artifacts are expected within the next years.
Next to a possibility of integrity validation, data needs to be retrievable by pipeline job id or digital asset checksum.


As part of the CI/CD audit functionality, data is stored within immudb using the Key/Value functionality. Key is either the CI/CD job id (i. e. Jenkins or GitLab) or the checksum of the resulting build or container image.

White Paper — Registration

We will also send you the research paper
via email.

CodeNotary — Webinar

White Paper — Registration

Please let us know where we can send the whitepaper on CodeNotary Trusted Software Supply Chain. 

Become a partner

Start Your Trial

Please enter contact information to receive an email with the virtual appliance download instructions.

Start Free Trial

Please enter contact information to receive an email with the free trial details.