@tokenharbor/halyard
Halyard — an agent harness wired to Token Harbor. Built on DeepSeek Harness.
This report shows the evidence for @tokenharbor/halyard@0.2.6. 4 of 7 known versions are blocked or flagged. The newest version, 0.2.11, is allowed. See all versions.
AI Security Review
scanned 2mo ago · by lpm-firewall-aiThe concrete postinstall rewrite of a foreign AI-agent dependency is sufficient for blocking under the install-control-surface policy. The observed gateway credential use does not independently establish exfiltration.
Decision evidence
public snapshot- Install lifecycle runs a rebranding script.
- That script rewrites files in the foreign @deepseek-ai dependency tree.
- It replaces the upstream web UI favicon and injects branding CSS.
- No covert credential harvesting found; API key use is for the declared Token Harbor gateway.
- Network authentication is invoked through explicit CLI login/debug paths.
Source & flagged code
7 flagged · loading sourcePackage defines install-time lifecycle scripts.
package.jsonView on unpkgInstall-time lifecycle script is not statically allowlisted and needs review.
package.jsonView on unpkgFindings
Affected versions and remediation
This report applies to @tokenharbor/halyard@0.2.6.
The versions list below shows the verdict for each recorded version.
- Avoid installing @tokenharbor/halyard@0.2.6. Remove it from direct dependencies and check your lockfile for transitive copies.
- Choose an independently verified alternative or release. This report does not establish that other versions are safe.
- If this version ran, investigate the affected machine and build environment. Rotate credentials it could access and rebuild from a trusted environment.
Evidence last updated: .
Think this verdict is wrong? Dispute it on GitHub or read how reports are produced.