This command is recorded from the source ecosystem and resolves the registry's latest release. The fixed release shown on this page should be inspected before adoption.
This automated, non-executing scan is bound to this release hash. It is not a safety certification and may contain false positives or false negatives.
Status
completed
Coverage
full text content
Files
5 / 5 inspected as text
Checked
10/12/2026, 6:02:01 AM
Scanner
0.1.3
Policy
1.0.3
2 inferred permission indicators
network access — automatically inferred
filesystem write — automatically inferred
6 dependency and API indicators
api: attacker
api: clawhub.ai
api: lg-data.cc
api: open.feishu.cn
api: privora.cn
api: user
External clawhub result: clean
This is registry-supplied evidence for the recorded release, not an independent SkillVetAI scan. Check the canonical source for the full report, scanner versions, scope, and current moderation state.
Evidence checked
10/12/2026, 3:38:28 AM
Release binding
Matches this record
vt: clean
skillspector: suspicious
llm: clean
Recorded files
The catalog stores hashes and an inventory summary for change detection. It does not republish the package contents.
## v1.0.8 · 2026-10-10 Documentation follow-up to the platform change for #1797 (Java + Node tiers; no script change). - **The `maxStaleSeconds` gate row no longer tells you to pass `90000`.** The platform now derives the default staleness threshold from the asset grain when a rule carries no `maxStaleSeconds`: a daily-grain asset is stale only after a full trading day's expected landing has been missed (weekends and long holidays do not trip it); every other asset keeps the 1800-second default. A fixed `90000` could not express weekends or holidays and would skip a healthy daily rule over them. An explicit `maxStaleSeconds` still always wins. - `metric.alert.evaluate-now` (and the saved-rule dry run) now also return a read-only `freshness` object (`timestamp`, `ageSeconds`, `grain`, `wouldBeSkippedStale`, `staleReason`); `wouldTrigger` is unchanged. Treat `wouldTrigger:true` together w…
Release security diff
mediumCompared fixed releases 1.0.7 and 1.0.8; 0 finding and 0 permission indicators were added.
Both fixed releases were scanned under the current scanner and policy, so finding, permission and dependency changes are available.
Change reasons and limitations
file surface changed
content hash changed
Observed release history
These older immutable releases were observed by prior successful syncs. They remain recorded when a newer release becomes current.