T08 · Insecure Dependencies
- Location
README.md:15- Finding
Execution of an Unpinned npm Installer
- Content
View full analysis
- Remediation
View remediation
Security audit
Security checks for vulnerabilities and agentic risk
This appears to be a genuine diet-tracking skill, but it stores personal health data and uses mutable external code without enough scoping or user control.
Before installing, pin the ClawHub installer version, avoid running install commands as administrator/root, grant the agent access only to the FitDietKernel directory, review profile/log contents for sensitive health data, and require confirmation before any food_registry.json or log writes. Prefer a bundled or pinned Chart.js build with integrity checks, and provide clear controls to delete locally stored weight and diet history.
README.md:15Execution of an Unpinned npm Installer
desktop-app.html:7Unpinned Third-Party JavaScript Executes in the Application Context
README.md:198Third-Party Tracking Request Embedded in Project Documentation
The declared purpose is diet calculation, but the detected behavior includes reading local logs, extracting sleep data, and generating weekly report files. This mismatch is dangerous because users may consent to a nutrition helper without realizing it also processes broader personal activity data and writes derived reports, increasing privacy and data-handling risk.
Hidden instructions were detected in comments or invisible text. These could contain malicious directives. Manual review is recommended.
<div class="subtitle">Kernel v1.0</div>
</header>
<!-- 今日状态 -->
<div class="today-card">
<div class="today-header">
<div class="day-label" id="dayLabel">周三 · 高碳日</div>
The README instructs users to run npx clawhub@latest install fitdietkernel, which pulls and executes the latest published package version at install time. Using a moving tag for a package that is executed locally creates a supply-chain risk: if the package or one of its dependencies is compromised, users may run attacker-controlled code during installation.
The skill explicitly tells the AI to generate logs/YYYY-MM-DD.md daily records, creating persistent files on disk, but the README does not clearly warn users that the assistant will write and retain personal health/diet data locally. In this skill context, the stored content may include sensitive lifestyle and body metrics, so silent persistence increases privacy and data exposure risk.
The skill instructs the AI to read from a local knowledge-base path and references modifying local data files, but it does not declare any explicit tool scope or permission boundaries. That creates an implicit file-access expectation, which can lead to overbroad local file reads or writes if the hosting agent grants filesystem tools by default.
The usage instructions tell users to modify a local profile file and provide its filesystem path to the AI, but they do not warn about exposing personal health or system-path information. Because profile data and local logs may contain sensitive health metrics and other private details, this can lead to unnecessary disclosure to the model or unintended file access.
The only natural-language description in the manifest is written in Chinese, with no indication that users can select another language or that the skill is intentionally region-specific. This may violate language/locale policy if the skill is presented in a multilingual environment without explicit opt-in or justification.
The skill embeds Chinese-only natural-language strings throughout the interface and comments, with no option for user language selection or explanation that the tool is intended only for a Chinese-speaking audience. This can violate language/locale policy when a specific language is forced without user opt-in.
The document is declared as zh-CN and the interface text is written in Chinese, while date formatting is also explicitly forced to zh-CN. This imposes a specific language/locale on users without any visible opt-in or explanation that the skill is intentionally region-specific.
The page loads Chart.js from a third-party CDN at runtime, which introduces a software supply-chain dependency unrelated to a simple personal diet/weight tracker. If the CDN, package, or network path is compromised, arbitrary JavaScript would execute in the app context and gain access to DOM data and locally stored weight history.
The app stores personal health-related data (current weight and history) in localStorage without any visible notice, retention policy, or user consent. localStorage is readable by any script running in the page, so the external CDN script materially increases the exposure of this data if compromised.
The skill's natural-language UI labels, placeholders, date formatting, and comments are presented in Chinese throughout, with no opt-in, language selection, or documented region-specific justification. This creates a language/locale policy concern because the skill effectively enforces one language for all users.
The file presents all operational instructions in Chinese and uses imperative language such as 'AI 必须严格遵守' without indicating that the user can opt into another language or that the skill is intentionally restricted to a Chinese-speaking context. Under the policy, forcing a specific language without opt-in is a natural-language policy concern.
The skill explicitly instructs the AI to automatically update food_registry.json from natural-language input, but it does not require explicit user confirmation, validation, or any audit boundary before modifying stored data. In an agent setting, this creates an unauthorized state-change risk: ambiguous or adversarial phrasing could poison the knowledge base, corrupt nutrition calculations, or cause persistent bad recommendations in future interactions.
This file contains user-facing natural-language instructions exclusively in Chinese, and there is no opt-in, alternative language, or justification that the content is intended only for a Chinese-speaking audience. Under the policy, forcing a specific language without user choice is a natural-language policy violation.
The only user-facing description in the manifest is written in Chinese, which may imply a fixed language/locale experience. The file does not mention that users can choose another language or that the locale restriction is intentional and justified.
The manifest describes a skill for fitness and diet knowledge assistance, specifically precise diet calculations such as carb cycling, keto, bulking, and cutting. This file instead reads markdown logs and generates/saves a weekly report branded as "BioContext-Kernel," which is a broader journaling/reporting workflow rather than a direct diet-calculation capability.
The top-level documentation says "BioContext-Kernel Report Generator" and the generated report footer also states it was automatically generated by "BioContext-Kernel". This actively points to a different tool identity and intent than the manifest's fitdietkernel fitness/diet knowledge-base purpose.
The module docstring states in Chinese that it automatically converts logs into a structured weekly report, and the generated report strings are also hard-coded in Chinese. This indicates a fixed language/locale behavior with no user opt-in or configurable language selection, which is a natural-language policy violation under the locale rule.
The entire skill description and example prompt are written only in Chinese, with no indication that users may interact in another language or opt into this locale. Under the policy, forcing a specific language without user choice can be a natural-language policy violation unless the locale restriction is explicitly justified.
The manifest description only says this is a 'personal knowledge base for fitness diet,' which describes a broad topic area rather than specific activation triggers or usage boundaries. In a manifest file, this lack of specificity can make invocation conditions ambiguous and increase the chance of unintended matching for general health or diet-related requests.
This code persists user health-related data to fitdiet_data.json, but there is no confirmation prompt, print/log message, or explanatory comment/docstring disclosing that the data is being saved locally. For a code file, local file writes involving personal data should have some visible disclosure unless clearly documented elsewhere.
The code explicitly formats timestamps using the zh-CN locale, which enforces a specific locale presentation regardless of user preference. Under the policy, locale constraints should either be user-selectable or clearly justified as region-specific.
When saving weight history, the code serializes dates using toLocaleDateString('zh-CN'), forcing Chinese locale formatting into persisted data. This is another user-visible locale restriction without opt-in or stated justification.
The skill saves weight and meal-tracking data to a local JSON file, but the code provides no visible notice, confirmation, or explanatory comment near the write operation. For a code file, file writes affecting personal data should have some form of user disclosure unless clearly documented elsewhere.