Add optional Shipgate scan for guardrails quickstart#2
Open
pengfei-threemoonslab wants to merge 1 commit into
Open
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Problem
The Guardrails quickstart uses
SerperDevTool()for external web search, but there is no lightweight release-readiness recipe for reviewing that tool surface without running the notebook.Why static/local-first
This adds an optional scoped Agents Shipgate manifest plus a local tool inventory for the notebook. Agents Shipgate reads local metadata only; it does not run the notebook, call Serper, make LLM calls, execute agents, or upload source.
Command run
For maintainers using the published package, the README shows:
Result summary
Maintainer-safe note
This is docs/sample-manifest only. It does not add repo-wide CI and does not commit generated
agents-shipgate-reports/output.