Security audit
Security checks for vulnerabilities and agentic risk
This skill is a small public-website scraper with expected browser automation dependencies and no evidence of hidden persistence, credential access, exfiltration, or destructive behavior.
Before installing, review and pin the npm dependencies, use a lockfile, and be aware that any future LLM-analysis implementation may send scraped abstracts to the model provider unless configured otherwise.
The skill states that scraped article abstracts will be analyzed by an LLM but does not clearly warn users that scraped content will be transmitted to an external model or service. This is dangerous because users may unknowingly send copyrighted, sensitive, access-restricted, or policy-constrained content to a third party, creating privacy, compliance, or contractual exposure.
The documentation instructs users to run npx playwright without pinning a specific package version, which can fetch whatever version is current at execution time. This creates a supply-chain risk because behavior and transitive dependencies can change unexpectedly, and a compromised or malicious upstream release could be executed in the user's environment.
The user-facing skill documentation is written entirely in Chinese, with no indication that other languages are supported or that the language choice is region-specific. Under the language/locale policy, forcing a specific language without user opt-in can be a natural-language policy violation.
The dependency uses a caret range instead of an exact pinned version, so installs may resolve to different package releases over time. This weakens supply-chain integrity and reproducibility because a later compromised or vulnerable minor/patch release could be pulled in without review.
{
"dependencies": {
"jsdom": "^28.1.0",
"playwright": "^1.58.2"
}
}
The Playwright dependency is not pinned to an exact version, allowing future installs to fetch newer matching releases automatically. Because Playwright also downloads browser binaries as part of its ecosystem, version drift increases supply-chain exposure and makes builds less deterministic.
{
"dependencies": {
"jsdom": "^28.1.0",
"playwright": "^1.58.2"
}
}
The manifest references Playwright without an exact pinned version while a known advisory exists for the package family, so it is not possible to determine from this file whether installs will resolve to an affected release. This uncertainty is dangerous because vulnerable versions may be pulled in silently depending on install time and lockfile state.
No suspicious patterns detected.