Repository navigation
parmana-server: point repository at the Apache-2.0 parmana-core - #385
Conversation
carloshvp
left a comment
carloshvp
left a comment
There was a problem hiding this comment.
Reviewed exact head b8800e83cfe66a6407d9926fb81d91bef7a859c5 in an isolated checkout.
The manifest now points to the public parmana-core repository, whose primary LICENSE file declares Apache-2.0, and the generated marketplace catalog reflects that exact URL. I verified the repository/license directly and ran integration manifest validation, compatibility checks, generated-index/catalog checks and diff whitespace checks; all passed. The change is limited to the repository pointer and generated metadata, with no new tier promotion or runtime behavior. No blocking finding within that scope; the remaining hosted checks and maintainer gate are separate.
Reviewed with OpenAI Codex.
|
Rebased branch on main, CI green. |
Record that the AgenTrust integration manifest now points at parmana-core (Apache-2.0). Reported merged on 2026-10-29; not independently verified from this repository. Signed-off-by: Pavan Dev Singh Charak <charak1987@gmail.com>
docs: note agentrust-io/integrations#385 repository pointer
The integration is Apache-2.0 and pins the public parmana 1.6.0 SDK, so its manifest should link the open-source repository, parmana-core, instead of the proprietary parmana repository. This is a one-line change to integrations/parmana-server/integration.yaml.