@uipath/gov-tool@1.201.0
Manage UiPath governance — AOps policies, Access policies, and compliance packs.
AI Security Review
scanned 2mo ago · by lpm-firewall-aiThe static signals are explained by normal JWT parsing and authenticated API-client behavior. There are no lifecycle hooks or autonomous execution paths.
Decision evidence
public snapshot- The manifest contains no lifecycle scripts; it only exposes the bundled module.
- The flagged Base64 operation parses the payload section of a JWT, not an obscured URL.
- Authentication traffic uses a validated HTTPS authority and its OIDC token endpoint.
- No install-time execution, self-dependency, or persistence mechanism was found.
- Network and credential handling are consistent with an authenticated UiPath governance CLI.
- Policy-changing operations are registered as explicit user-invoked commands.
Source & flagged code
4 flagged · loading sourceSource decodes a Base64-obscured HTTP endpoint at runtime.
dist/tool.jsView on unpkg · L12041Authentication traffic uses a validated HTTPS authority and its OIDC token endpoint.
dist/tool.jsView on unpkg · L22394Findings
Affected versions and remediation
This report applies to @uipath/gov-tool@1.201.0.
See all versions of @uipath/gov-tool for other recorded verdicts.
- Review the evidence and your use of @uipath/gov-tool@1.201.0 before allowing it. Restrict the permissions described in this report.
- Choose an independently verified alternative or release. This report does not establish that other versions are safe.
Evidence last updated: .
Think this verdict is wrong? Dispute it on GitHub or read how reports are produced.