1. User installs extension and configures Hister server URL in options. 2. Extension injects content scripts to capture page data. 3. Extension sends page data to the configured Hister API. 4. User accesses history via the Hister web interface.

Target users: Privacy-conscious users / Self-hosted enthusiasts / Researchers

The extension relies on a destination service (Hister server) which is not included in the source package. The analysis assumes the server requires authentication based on the extension's configuration requirements.

Monetization

No paid features detected

The extension is free and open-source (GitHub: asciimoo/hister). There is no code related to subscriptions, payments, or premium features within the extension. The 'pro' keyword matches in the static analysis were false positives (e.g., 'pro' in 'properties' in CSS, 'pro' in 'prototype' in JS).

Confidence: 95
Payment platform: --
Source: AI / High
Login required: Yes
Reason: The extension is a companion client for a self-hosted 'Hister' server. It requires the user to configure a server URL and authenticate via cookies or tokens. The extension itself does not have a login UI, but the core functionality (indexing web history) is impossible without an account/session on the destination Hister service. The options page explicitly instructs users to 'Make sure you are logged in to the Hister web app' to fetch cookies.

Permission risk

High-risk permissions

This estimate uses declared permissions and host permissions to assess access scope and sensitivity.

扩展能力较强：tabs、storage、webRequest
主机权限覆盖范围较宽

Publisher

asciimoo

Independent publisher

Email: [email protected]
Phone: --
Address: --

Public contact fields are shown above. Developer portfolio pages are available on paid accounts.

View developer portfolio

Permissions

Host access