Merge branch 'main' into perf/zkp-ipa-optimization

Author: SurbhiAgarwal1

.github/workflows/scorecard.yml

@@ -0,0 +1,56 @@
+name: "OpenSSF Scorecard"
+
+# The README Scorecard badge is intentionally NOT added yet: api.scorecard.dev only
+# serves data for a repository after this workflow has run on the default branch with
+# publish_results: true. Until then the badge renders "invalid repo path". Add
+#   https://api.scorecard.dev/projects/github.com/LFDT-Panurus/panurus/badge
+# to the README badge row once the first run on `main` has completed.
+
+on:
+  # Re-run when branch protection changes, since Branch-Protection is a scored check.
+  branch_protection_rule:
+  schedule:
+    - cron: '27 6 * * 1'
+  push:
+    branches: [ "main" ]
+
+# Least privilege by default; the job below elevates only what it needs.
+permissions: read-all
+
+jobs:
+  analysis:
+    name: Scorecard analysis
+    runs-on: ubuntu-latest
+    permissions:
+      # Required to upload the results to code-scanning.
+      security-events: write
+      # Required by publish_results, which signs the results for the public API
+      # that serves the README badge.
+      id-token: write
+
+    steps:
+      - name: "Checkout code"
+        uses: actions/checkout@v4
+        with:
+          persist-credentials: false
+
+      - name: "Run analysis"
+        uses: ossf/scorecard-action@v2.4.4
+        with:
+          results_file: results.sarif
+          results_format: sarif
+          # Must stay true: without it the api.securityscorecards.dev endpoint
+          # serves no data and the README badge renders "invalid repo path".
+          publish_results: true
+
+      - name: "Upload artifact"
+        uses: actions/upload-artifact@v4
+        with:
+          name: SARIF file
+          path: results.sarif
+          retention-days: 5
+
+      - name: "Upload to code-scanning"
+        uses: github/codeql-action/upload-sarif@v4
+        with:
+          sarif_file: results.sarif

.golangci.yml

@@ -16,6 +16,7 @@ linters:
     - govet # Vet examines Go source code and reports suspicious constructs. It is roughly the same as 'go vet' and uses its passes. [auto-fix]
     - importas # Enforces consistent import aliases. [auto-fix]
     - intrange # Intrange is a linter to find places where for loops could make use of an integer range. [auto-fix]
+    - ireturn # Accept Interfaces, Return Concrete Types.
     - loggercheck # Checks key value pairs for common logger libraries (kitlog,klog,logr,slog,zap).
     - lll # Reports long lines. [fast]
     - mirror # Reports wrong mirror patterns of bytes/strings usage. [auto-fix]
@@ -90,6 +91,25 @@ linters:
         - github.com/prometheus/client_golang/prometheus.Counter
         - github.com/prometheus/client_golang/prometheus.Gauge
         - github.com/prometheus/client_golang/prometheus.Histogram
+        # Third-party interfaces we are obliged to return: either the signature is fixed by an
+        # interface we implement (Pagination, bccsp.Key, KeyStore) or it is the framework's own
+        # constructor convention (view.View, view.Session). Returning a concrete type instead is
+        # not an option in these cases, so allow them rather than carry a nolint at every site.
+        - github.com/hyperledger-labs/fabric-smart-client/platform/common/driver.Pagination
+        - github.com/hyperledger-labs/fabric-smart-client/platform/view/view.View
+        - github.com/hyperledger-labs/fabric-smart-client/platform/view/view.Session
+        - github.com/hyperledger/fabric-lib-go/bccsp.Key
+        - github.com/hyperledger/fabric-lib-go/bccsp.BCCSP
+        - github.com/hyperledger/fabric-lib-go/bccsp.HashOpts
+        - github.com/IBM/idemix/bccsp/types.BCCSP
+        - github.com/IBM/idemix/bccsp/types.KeyStore
+        - go.opentelemetry.io/otel/trace.Span
+        - github.com/hyperledger/fabric-lib-go/common/metrics.Gauge
+        - github.com/hyperledger/fabric-lib-go/common/metrics.Histogram
+        - github.com/hyperledger-labs/fabric-smart-client/platform/common/driver.ConfigService
+        - github.com/hyperledger-labs/fabric-smart-client/integration/nwo/api.ViewClient
+        - github.com/hyperledger-labs/fabric-smart-client/integration/nwo/api.Platform
+        - github.com/hyperledger-labs/fabric-smart-client/integration/nwo/api.Context
     lll:
       # Max line length, lines longer will be reported.
       line-length: 240

ADOPTERS.md

@@ -0,0 +1,45 @@
+[//]: # (SPDX-License-Identifier: CC-BY-4.0)
+
+# Adopters
+
+This file lists organizations and projects using Panurus, together with a publicly verifiable
+reference for each entry.
+
+## Are you using Panurus?
+
+Please add yourself. Adopter lists help the community understand where Panurus is deployed, guide
+roadmap priorities, and give new users confidence in the project.
+
+To be added:
+
+1. Open a pull request editing this file.
+2. Add a row to the table below.
+3. Include a **publicly verifiable reference** — a link to an announcement, blog post, paper, press
+   release, conference talk, or public repository. Entries without a public reference cannot be
+   accepted, as required by the
+   [LFDT project consistency guidelines][lfdt-consistency].
+4. Only add your organization if you are authorized to do so on its behalf.
+
+If you would rather not be listed publicly but are happy for the maintainers to know, say so in a
+[GitHub Discussion](https://github.com/LFDT-Panurus/panurus/discussions) instead.
+
+## Adopters
+
+| Organization / Project | Type of use | Status | Reference |
+|------------------------|-------------|--------|-----------|
+
+_No adopters are listed yet. Entries require a publicly verifiable reference — see above._
+
+**Status** is one of:
+
+- **Production** — deployed in a production environment.
+- **Pilot** — deployed in a limited pilot or proof of concept.
+- **Evaluating** — under active evaluation.
+
+<!--
+Example row:
+
+| Example Bank | Tokenized deposits on Fabric | Pilot | https://example.org/press/tokenized-deposit-pilot |
+-->
+
+[lfdt-consistency]: https://github.com/LF-Decentralized-Trust/governance/blob/main/tac/guidelines/project-consistency-guidelines.md

CODE_OF_CONDUCT.md

@@ -1,7 +1,7 @@
 Code of Conduct Guidelines
 ==========================
 
-Please review the Hyperledger [Code of Conduct](https://www.lfdecentralizedtrust.org/code-of-conduct)
+Please review the LF Decentralized Trust [Code of Conduct](https://www.lfdecentralizedtrust.org/code-of-conduct)
 before participating. It is important that we keep things civil.
 
 <a rel="license" href="http://creativecommons.org/licenses/by/4.0/"><img alt="Creative Commons License" style="border-width:0" src="https://i.creativecommons.org/l/by/4.0/88x31.png" /></a><br />This work is licensed under a <a rel="license" href="http://creativecommons.org/licenses/by/4.0/">Creative Commons Attribution 4.0 International License</a>.

MAINTAINERS.md

@@ -1,29 +1,91 @@
-Maintainers
-===========
+[//]: # (SPDX-License-Identifier: CC-BY-4.0)
 
-**Active Maintainers**
+# Maintainers
 
-| Name               | GitHub                               | Chat        | email                       |
-|--------------------|--------------------------------------|-------------|-----------------------------|
-| Angelo De Caro     | [adecaro][adecaro]                   | adecaro     | <adc@zurich.ibm.com>        |
-| Kaoutar Elkhiyaoui | [KElkhiyaoui][KElkhiyaoui]           | KElkhiyaoui | <kao@zurich.ibm.com>        |
-| Arne Rutjes        | [arner][arner]                       | arner       | <arne.rutjesISC@nl.ibm.com> |
-| Alexandros Filios  | [alexandrosfilios][alexandrosfilios] | lio         | <alexandros.filios@alumni.ethz.ch> |
-| Akram Bitar        | [AkramBitar][AkramBitar]             | akrambitar  | <akram@il.ibm.com>        |
+Changes to either list below are made by pull request against this file. After such a pull request
+is merged, the corresponding GitHub team (`panurus-maintainers`) must be updated manually to match.
 
-**Emeritus Maintainers**
+## Active Maintainers
 
-| Name | GitHub | Chat | email
-|------|--------|------|----------------------
-| Alessandro Sorniotti | [ale-linux][ale-linux] | aso | <ale.linux@sopit.net>
-| Elli Androulaki | [elli-androulaki][elli-androulaki] | elli-androulaki | <lli@zurich.ibm.com>
-| Mathilde Ffrench | [mffrench][mffrench] | mffrench | <mathilde.ffrench@fr.ibm.com>
+| Name | GitHub ID | Scope | LFID | Discord ID | Email | Company Affiliation |
+|------|-----------|-------|------|------------|-------|---------------------|
+| Angelo De Caro | [adecaro][adecaro] | Maintainer | | adecaro | <adc@zurich.ibm.com> | IBM |
+| Kaoutar Elkhiyaoui | [KElkhiyaoui][KElkhiyaoui] | Maintainer | | KElkhiyaoui | <kao@zurich.ibm.com> | IBM |
+| Arne Rutjes | [arner][arner] | Maintainer | | arner | <arne.rutjesISC@nl.ibm.com> | IBM |
+| Alexandros Filios | [alexandrosfilios][alexandrosfilios] | Maintainer | | lio | <alexandros.filios@alumni.ethz.ch> | Independent |
+| Akram Bitar | [AkramBitar][AkramBitar] | Maintainer | | akrambitar | <akram@il.ibm.com> | IBM |
+
+## Emeritus Maintainers
+
+| Name | GitHub ID | Scope | LFID | Discord ID | Email | Company Affiliation |
+|------|-----------|-------|------|------------|-------|---------------------|
+| Alessandro Sorniotti | [ale-linux][ale-linux] | Maintainer | | aso | <ale.linux@sopit.net> | IBM |
+| Elli Androulaki | [elli-androulaki][elli-androulaki] | Maintainer | | elli-androulaki | <lli@zurich.ibm.com> | IBM |
+| Mathilde Ffrench | [mffrench][mffrench] | Maintainer | | mffrench | <mathilde.ffrench@fr.ibm.com> | IBM |
+
+## Scopes
+
+Panurus uses a single maintainer scope covering the whole repository.
+
+| Scope | Definition | GitHub Role | GitHub Team |
+|-------|------------|-------------|-------------|
+| Maintainer | Maintainer for the entire repository | Maintain | `panurus-maintainers` |
+
+## Maintainer Duties
+
+Maintainers are expected to:
+
+- Review and merge pull requests, and keep CI green.
+- Triage incoming issues.
+- Participate in project calls and technical discussions.
+- Contribute to the mid-year project update and annual review filed with the LFDT TAC.
+- Mentor contributors working toward maintainership.
+
+Members of the security team carry the additional responsibilities described in
+[SECURITY.md](SECURITY.md).
+
+## How to Become a Maintainer
+
+Candidates for maintainership are expected to have:
+
+- a sustained history of substantive contributions to Panurus — code, review, documentation, or
+  release engineering,
+- demonstrated good judgement in code review, and
+- familiarity with the project's architecture and contribution process
+  (see [CONTRIBUTING.md](CONTRIBUTING.md)).
+
+The process is:
+
+1. An existing active maintainer sponsors the candidate.
+2. The sponsor opens a pull request adding the candidate to the **Active Maintainers** table above,
+   with a justification in the pull request description summarising the candidate's contributions.
+3. Current active maintainers have **two weeks** to review and raise objections.
+4. Approval requires a majority of active maintainers, with no sustained objection.
+5. Once merged, the `panurus-maintainers` GitHub team is updated to grant access.
+
+An emeritus maintainer may return to active status by the same process, without requiring a new
+sponsor.
+
+## How Maintainers are Removed or Moved to Emeritus Status
+
+A maintainer may be moved to emeritus status:
+
+- **At their own request** — open a pull request moving your row to the **Emeritus Maintainers**
+  table. This needs no further approval.
+- **Through inactivity** — a maintainer with no meaningful contribution or review activity for
+  **twelve months** may be proposed for emeritus status.
+- **For conduct** — a violation of the [Code of Conduct](CODE_OF_CONDUCT.md) may result in removal.
+
+Proposals follow the same path as additions: a pull request against this file with a justification,
+a two-week comment window, and approval by a majority of active maintainers. Moving to emeritus
+status is not a judgement on past contributions; it reflects current activity, and the door back is
+described above.
 
-[elli-androulaki]: https://github.com/elli-androulaki
 [adecaro]: https://github.com/adecaro
 [KElkhiyaoui]: https://github.com/KElkhiyaoui
-[mffrench]: https://github.com/mffrench
-[ale-linux]: https://github.com/ale-linux
 [arner]: https://github.com/arner
 [alexandrosfilios]: https://github.com/alexandrosfilios
-[AkramBitar]: https://github.com/AkramBitar
+[AkramBitar]: https://github.com/AkramBitar
+[ale-linux]: https://github.com/ale-linux
+[elli-androulaki]: https://github.com/elli-androulaki
+[mffrench]: https://github.com/mffrench

README.md

@@ -4,6 +4,7 @@
 
 <p align="center">
   <a href="LICENSE"><img src="https://img.shields.io/badge/license-Apache%202-blue" alt="License"></a>
+  <a href="https://www.bestpractices.dev/projects/7176"><img src="https://www.bestpractices.dev/projects/7176/badge" alt="OpenSSF Best Practices"></a>
   <a href="https://goreportcard.com/badge/github.com/LFDT-Panurus/panurus"><img src="https://goreportcard.com/badge/github.com/LFDT-Panurus/panurus" alt="Go Report Card"></a>
   <a href="https://github.com/LFDT-Panurus/panurus/actions/workflows/tests.yml"><img src="https://github.com/LFDT-Panurus/panurus/actions/workflows/tests.yml/badge.svg?branch=main" alt="Tests"></a>
   <a href="https://github.com/LFDT-Panurus/panurus/actions/workflows/codeql-analysis.yml"><img src="https://github.com/LFDT-Panurus/panurus/actions/workflows/codeql-analysis.yml/badge.svg?branch=main" alt="CodeQL"></a>
@@ -15,8 +16,14 @@ Panurus provides a collection of APIs and services that streamline development f
 # Useful Links
 
 - [`Documentation`](docs/README.md): The entry point for Panurus documentation.
+- [`Releases`](https://github.com/LFDT-Panurus/panurus/releases): Current and past releases, with
+  release notes. The latest release is always at
+  [`releases/latest`](https://github.com/LFDT-Panurus/panurus/releases/latest).
 - [`Development`](docs/development/development.md): All about the development guidelines.
 - [`Contributing`](CONTRIBUTING.md): How to contribute to the project.
+- [`Adopters`](ADOPTERS.md): Who is using Panurus. **Using Panurus? Please add yourself to
+  [`ADOPTERS.md`](ADOPTERS.md)** — it helps the community understand where the project is deployed.
+- [`Security`](SECURITY.md): How to report a security vulnerability.
 - [`Fabric Samples`](https://github.com/hyperledger/fabric-samples/tree/main/token-sdk) Panurus sample application is the
   quickest way to get a full network running with a REST API to issue, transfer and redeem tokens right away.
 - [`Benchmarks`](./docs/drivers/benchmark/benchmark.md): Benchmark guidelines and reports.
@@ -30,7 +37,7 @@ Panurus provides a collection of APIs and services that streamline development f
 
 # Additional Resources
 
-- (March 17, 2022) [`Hyperledger in-Depth: Tokens in Hyperledger Fabric: What’s possible today and what’s coming`](https://www.hyperledger.org/learn/webinars/hyperledger-in-depth-tokens-in-hyperledger-fabric-whats-possible-today-and-whats-coming):
+- (March 17, 2022) [`Hyperledger in-Depth: Tokens in Hyperledger Fabric: What’s possible today and what’s coming`](https://lfdecentralizedtrust.org/learn/webinars/hyperledger-in-depth-tokens-in-hyperledger-fabric-whats-possible-today-and-whats-coming):
   Tokenizing the physical world is a hot blockchain topic in the industry, especially as it relates to the 
   trade of tokens as a basis of new forms of commerce. In this Hyperledger Foundation member webinar, 
   the IBM Research team describes in this webinar what tokenization use cases are possible with Hyperledger Fabric today,