← Home

@askalf/deepdive

npm Repository Homepage

A local research agent. One command, cited answer. Routes every LLM call through your own proxy (dario, Anthropic-compat, OpenAI-compat). Headless browser + pluggable search + multi-provider LLM — zero hosted dependencies.

39
Versions
MIT
License
No
Install Scripts
Verified
Provenance

Supply chain provenance

Status for the latest visible version.

SLSA provenance attestation npm registry signatures gitHead linked

Maintainers

askalf

Keywords

researchagentllmlocalclianthropicopenaiclaudesearchdeep-researchperplexity-alternativecitecitationsself-hosted

Versions (showing 39 of 39)

Version Deps Published
0.32.0 3 / 4
0.31.1 3 / 4
0.31.0 3 / 3
0.30.0 1 / 3
0.29.0 1 / 3
0.28.0 1 / 3
0.27.1 1 / 3
0.27.0 1 / 3
0.26.1 1 / 3
0.26.0 1 / 3
0.25.3 1 / 3
0.25.2 1 / 3
0.25.1 1 / 3
0.25.0 1 / 3
0.24.0 1 / 3
0.23.0 1 / 3
0.22.0 1 / 3
0.21.0 1 / 3
0.20.0 1 / 4
0.19.0 1 / 4
0.18.0 1 / 4
0.17.0 1 / 4
0.16.0 1 / 4
0.15.0 1 / 4
0.14.0 1 / 4
0.13.2 1 / 4
0.13.1 1 / 4
0.13.0 1 / 4
0.12.0 1 / 4
0.11.0 1 / 4
0.10.0 1 / 4
0.9.0 1 / 4
0.8.0 1 / 4
0.7.0 1 / 4
0.6.0 1 / 3
0.5.0 1 / 3
0.4.0 1 / 3
0.3.0 1 / 3
0.1.0 1 / 3

v0.32.0

1 finding
INFO Has SLSA provenance attestation provenance

Published via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.

v0.31.1

2 findings
INFO Has SLSA provenance attestation provenance

Published via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.

INFO Publisher changed: askalf → GitHub Actions (on 2026-07-12, now via trusted publisher with provenance) provenance

This version was published by a different npm account (GitHub Actions) than the most recent previously approved version (askalf) on 2026-07-12, but it carries Sigstore provenance attestation. This means the package moved to a trusted publisher (CI/CD with OIDC, e.g. GitHub Actions) — a supply-chain integrity improvement, not a compromise, since a stolen npm token cannot forge provenance bound to the source repository. Recorded as INFO for audit trail.

v0.31.0

1 finding
INFO Has SLSA provenance attestation provenance

Published via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.

v0.30.0

1 finding
INFO Has SLSA provenance attestation provenance

Published via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.

v0.29.0

1 finding
INFO Has SLSA provenance attestation provenance

Published via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.

v0.28.0

1 finding
INFO Has SLSA provenance attestation provenance

Published via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.

v0.27.1

1 finding
INFO Has SLSA provenance attestation provenance

Published via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.

v0.27.0

1 finding
INFO Has SLSA provenance attestation provenance

Published via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.