Web3 · Smart Contract Audit

Pummel Health Security Audits

softstack has completed 2 smart contract audits for Pummel Health between May 2019 and September 2022. Every report is published in the softstack public audit archive.

Key facts

Client
Pummel Health
Audits completed
2
First audited
Latest audit
Chains
Ethereum
Languages
Solidity, C++

About the project

PUML Better Health is an Australian wellness platform that rewards people for completing fitness and healthy-habit challenges. Its mobile app tracks steps, hydration, sleep, meditation and gratitude activity, with team leaderboards used in corporate wellness programmes. Participants earn rewards redeemable for gift cards and partner products, or for PUMLx, an ERC-20 utility token.

Findings

Combined across all 2 reviews softstack has completed for Pummel Health. Each report is broken out below.

0Critical
0High
0Medium
0Low
0Informational

Reports

Newest first. Every report covers its own scope and commit.

  1. PUML Better Health PUMLx Token smart contract audit

    PDF
    0Critical
    0High
    0Medium
    0Low
    0Informational

    No security findings reported.

  2. PUML token smart contract audit

    PDF

    Severity breakdown is in the published report.

    ScopeSource repositorygithub.com/EOSIO/eosio.contracts

    Components reviewed

    1 module
    1. See the published report for the file list

About this engagement

A smart contract audit reviews on-chain code for flaws an attacker could exploit. Engineers trace how assets move through the contracts, check who can call privileged functions, and test the arithmetic, external calls and upgrade paths. Each finding is rated by severity, and fixes are re-checked before the final report.

How softstack runs smart contract audits

Methodology

Review process

  1. Scoping and threat modelling

    The commit hash is frozen and the attack surface is mapped: asset flows, trust assumptions, privileged roles and the external systems the code depends on.

  2. Automated analysis

    Static analysers sweep the full codebase to surface known weakness patterns, unreachable states and deviations from established conventions.

  3. Manual code review

    Independent engineers read the code line by line, concentrating on business logic, access control, arithmetic and the handling of external calls.

  4. Adversarial testing

    Property-based fuzzing and invariant tests attack the assumptions the protocol relies on, targeting states that ordinary unit tests never reach.

  5. Reporting

    Every finding is documented with a severity rating, its impact, the steps to reproduce it and a concrete remediation the team can act on.

  6. Remediation verification

    Submitted fixes are re-reviewed against the original finding, and the final report records the resolved state of each one.

Standards and references

  • SWC RegistrySmart Contract Weakness Classification
  • CWECommon Weakness Enumeration

FAQ

Pummel Health was audited by softstack GmbH, a German Web3 security and software company based in Flensburg and certified to ISO/IEC 27001 by TÜV SÜD. softstack has completed 2 smart contract audits for Pummel Health between May 2019 and September 2022. The published reports are linked on this page and in the softstack public audit archive.

2 separate reviews, the first in May 2019 and the most recent in September 2022. Each one covers its own scope and commit, and is listed individually on this page.

0 findings across all 2 reviews: none. 0 of 0 were resolved or mitigated before the final reports.

Each report covers the code as it stood at the commit it names, the most recent in September 2022. Any code changed after that point is outside the reviewed scope.

Related audits

Browse all security audits

Disclaimer

This audit represents a point-in-time security assessment of the reviewed codebase and is intended for informational purposes only. While Softstack applies industry-standard security review methodologies, no audit can guarantee the absence of vulnerabilities, bugs, or other security risks. This report does not constitute financial, legal, regulatory, or investment advice, nor does it endorse the project, its business model, products, or services. Security is an ongoing process, and we strongly recommend conducting a new assessment following any material code changes or at least every 6 months to address newly emerging threats, vulnerabilities, and ecosystem developments.