@karmaniverous/jeeves-watcher BSD-3-Clause 27 versions

@karmaniverous/jeeves-watcher

npm Repository Homepage

Filesystem watcher that keeps a Qdrant vector store in sync with document changes

27

Versions

BSD-3-Clause

License

No

Install Scripts

Missing

Provenance

Supply chain provenance

Status for the latest visible version.

No SLSA provenance npm registry signatures gitHead linked

Without SLSA provenance there is no cryptographic link between this tarball and the public source — the axios compromise (March 2026) relied on exactly this gap.

Maintainers

eponymous

Keywords

filesystemwatcherqdrantvector-storeembeddingssemantic-searchdocument-indexingraglangchaingeminitypescriptcli

Accepted risks

Findings the reviewer chose to accept rather than block on.

Source	Rule	Reason	Accepted by	When
phantom-deps	phantom-dep:commander	AI (phantom-deps): Config-referenced dep; stable false positive for this package.	ai	2026/05/23
phantom-deps	phantom-dep:@langchain/qdrant	AI (phantom-deps): Config-referenced dep; stable false positive for this package.	ai	2026/05/23
maintainer-change	maintainer-removed	AI (maintainer-change): Same author org; routine maintainer cleanup, not an external takeover signal.	ai	2026/05/23
phantom-deps	phantom-dep:tiktoken	AI (phantom-deps): tiktoken referenced in config; stable false positive for this RAG/embedding package.	ai	2026/05/12
phantom-deps	phantom-dep:json5	AI (phantom-deps): json5 referenced in config files; stable false positive for this package.	ai	2026/05/12
phantom-deps	phantom-dep:hast	AI (phantom-deps): hast is a type-only/peer dep used in config; not directly imported by design.	ai	2026/05/12
phantom-deps	phantom-dep:@commander-js/extra-typings	AI (phantom-deps): extra-typings is a type-augmentation package; not directly imported at runtime by design.	ai	2026/05/12

Versions (showing 27 of 27)

Version	Deps	Published
0.17.9	31 / 24	2026-05-13
0.17.8	30 / 25	2026-05-03
0.17.7	30 / 25	2026-04-22
0.17.6	30 / 25	2026-04-15
0.17.2	30 / 25	2026-04-05
0.17.0	30 / 25	2026-04-03
0.16.3	30 / 25	2026-03-31
0.16.1	30 / 25	2026-03-30
0.14.0	30 / 25	2026-03-23
0.11.1	29 / 24	2026-03-19
0.9.9	30 / 25	2026-03-14
0.9.8	30 / 25	2026-03-14
0.9.7	30 / 25	2026-03-12
0.9.3	30 / 25	2026-03-09
0.8.2	32 / 25	2026-03-07
0.4.3	32 / 39	2026-02-23
0.4.0	32 / 39	2026-02-23
0.3.1	24 / 39	2026-02-22
0.3.0	24 / 39	2026-02-22
0.2.6	24 / 39	2026-02-22
0.2.5	24 / 39	2026-02-22
0.2.4	23 / 39	2026-02-22
0.2.3	23 / 39	2026-02-21
0.2.2	23 / 39	2026-02-21
0.2.1	23 / 39	2026-02-21
0.2.0	23 / 39	2026-02-21
0.1.0	20 / 38	2026-02-20

v0.17.9

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v0.17.8

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v0.17.7

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v0.17.6

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v0.17.2

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v0.17.0

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v0.16.3

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v0.16.1

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v0.14.0

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v0.11.1

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v0.9.9

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v0.9.8

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v0.9.7

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v0.9.3

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v0.8.2

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v0.4.3

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v0.4.0

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v0.3.1

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v0.3.0

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v0.2.6

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v0.2.5

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v0.2.4

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v0.2.3

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v0.2.2

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v0.2.1

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v0.2.0

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v0.1.0

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.