dataparity@0.1.0
VERIFIED· install onlyPublisher claims: "Enables AI agents to compare two tables across the same or different databases and report what changed, which columns changed, and where changes concentrate, plus source/table discovery and schema description. Runs four read-only tools that take source names rather than connection strings, returning a stable JSON contract with a risk verdict." Observed in sandbox: no network, touches nothing outside the project, writes no memory.
Coverage
Nothing executable in the bundle ran; the trace covers the install step only.- Tested
- every file read, file written and host contacted by what ran
- Not tested
- use of the skill by an agent
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
DATAPARITY_PG_CONNECTION_STRINGDATAPARITY_TEST_MYSQL_PASSWORDConfiguration, not credentials: BENCH_CHANGED, BENCH_ROWS, DATAPARITY_CONFIG, DATAPARITY_TEST_MYSQL_DB, DATAPARITY_TEST_MYSQL_HOST, DATAPARITY_TEST_MYSQL_PORT, DATAPARITY_TEST_MYSQL_USER, DATAPARITY_TEST_PG- Where it talks to
- no vendor host named in the code
- What the honeypot saw
- no credential files read · no network
- What we could not test
- use of the skill by an agent
Connect it with a scoped credential, under the guard. It asks for DATAPARITY_PG_CONNECTION_STRING, DATAPARITY_TEST_MYSQL_PASSWORD and talks to its vendor. Give the credential to the guard, not the server: the value never enters the server's environment and only travels to the host you bind. What the tools do with a real credential was not observed.
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 (1 scenario; nothing executable in the bundle ran; the trace covers the install step only) on 2026-11-12 and scored it 89/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 · 1 scenarios · 0 deviationsStatic findings
console.log(`attached Postgres in DuckDB in ${Date.now() - t} ms`);Fix: Remove the call, or declare the host in frontmatter and explain in the README what is sent and why.// Only run when invoked directly (including via npm/npx bin symlinks), not when imported by a test.Fix: Pin versions and sources; vendor anything fetched at install time.console.log(`generating ${ROWS.toLocaleString('en-US')} rows in Postgres...`);Fix: Remove the call, or declare the host in frontmatter and explain in the README what is sent and why.await checkAsync('CLI: runs when invoked via a symlink (as npx / npm bin installs it)', async () => {Fix: Pin versions and sources; vendor anything fetched at install time.Cost to the agent
Tokens estimated at four characters each. Skills load their instruction text when triggered; the figure is what that costs.
Known vulnerabilities
Vulnerability advisories (OSV) cover npm and PyPI packages; this registry has no advisory database.