flieber@0.1.17
VERIFIED· not startedPublisher claims: "Work with your Flieber account from the terminal or your AI assistant: sales, forecast, inventory, replenishment and more." Observed in sandbox: no network, touches nothing outside the project, writes no memory.
Coverage
Not started: dependency install failed; the server itself was not observed.- Tested
- the dependency install step · every file read, file written and host contacted by what ran
- Not tested
- server startup · the tool list · tool behavior
What this means for the label: Verified here covers what ran. The server's tools were not exercised with a real credential, so nothing about their behavior is asserted; the credential summary below says what to do with that.
Before you give it your token
- It will ask for
- no credential variables read in the code
- Where it talks to
- flieber.com, flieberqa.com (its own)Also cursor.com, accounts.dev, railway.app — not the publisher's domain; check what for before connecting.
- What the honeypot saw
- no credential files read · no network
- What we could not test
- server startup · the tool list · tool behavior
Connect it under the guard. Not started: dependency install failed; the server itself was not observed. The code names no credential variable and talks to flieber.com, flieberqa.com, its own; the guard pins the network to what the honeypot saw and logs every call.
Never paste a credential into a chat, a ticket or a report, including ours. How the guard holds it.
Is [email protected] safe to install?
KillerSkills ran it in the KillerSkills honeypot sandbox (2 scenarios; not started: dependency install failed; the server itself was not observed) on 2026-11-08 and scored it 81/100 (Verified). In what ran, nothing we could detect went wrong: no undeclared network egress, no credential reads, no persistent instruction writes. What it does with a real credential was not observed; the static findings and the publisher carry the rest of the score. Summary: no network, touches nothing outside the project, writes no memory.
Behavior trace
Honeypot run · 0 s · 2 scenarios · 0 deviationsStatic findings
FLIEBER_NO_AUTO_UPDATE, a flieber that isn't a final release, or one running from a source checkout.Fix: Pin versions and sources; vendor anything fetched at install time.The app reads them from the same PostHog project as the portal (flieber-frontend `.env.qa` andFix: Stop enumerating or reading credential locations; take secrets from a declared environment variable the user sets on purpose.`.env.production` carry the portal's `phc_` keys and hosts, `flieber.app.POSTHOG_PROJECTS`), for the sameFix: Stop enumerating or reading credential locations; take secrets from a declared environment variable the user sets on purpose.done = subprocess.run(argv, capture_output=True, text=True, check=False) # noqa: S603 (argv, no shell)Fix: Build commands from fixed arguments, never from interpolated strings; prefer an API client over shelling out.# as a key would skip the OAuth write kill switch (ADR-0004).Fix: Build commands from fixed arguments; do not interpolate untrusted strings into a shell.handler runs: the item cap (per surface), the OAuth kill switch, the tenant scope, the credential, and theFix: Build commands from fixed arguments; do not interpolate untrusted strings into a shell.Cost to the agent
Tokens estimated at four characters each. The tool list is re-read by the agent on every turn, so it is the number to compare between servers that do the same job: ranked across the index.
Known vulnerabilities
No advisories in OSV for flieber@0.1.17 as of 6d ago. This is the package itself, not its dependencies.