@easbot/note MIT 31 versions

@easbot/note

npm Repository Homepage

Note Knowledge Base - 非结构化记忆和文档知识库管理系统，支持混合搜索（向量+FTS+图）和 LLM 驱动的知识摄取

31

Versions

MIT

License

No

Install Scripts

Missing

Provenance

Supply chain provenance

Status for the latest visible version.

No SLSA provenance npm registry signatures No source commit

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

jallenhou

Keywords

easbotknowledge-basevector-searchfull-text-searchgraph-databasehybrid-searchdocument-ingestionentity-extractionllmembeddingsqliterag

Accepted risks

Findings the reviewer chose to accept rather than block on.

Source	Rule	Reason	Accepted by	When
phantom-deps	phantom-dep:@ai-sdk/openai-compatible	AI (phantom-deps): Imported dynamically via config-driven provider selection; stable pattern for this package.	ai	2026/05/12
phantom-deps	phantom-dep:@easbot/ollama-sdk	AI (phantom-deps): Internal monorepo dependency; same-org scope indicates intentional shared reference.	ai	2026/05/12
phantom-deps	phantom-dep:@easbot/local-model-sdk	AI (phantom-deps): Internal monorepo dependency; same-org scope indicates intentional shared reference.	ai	2026/05/12
phantom-deps	phantom-dep:@ai-sdk/anthropic	AI (phantom-deps): Imported dynamically via config-driven provider selection; stable pattern for this package.	ai	2026/05/12
phantom-deps	phantom-dep:@ai-sdk/provider-utils	AI (phantom-deps): Imported dynamically via config-driven provider selection; stable pattern for this package.	ai	2026/05/12
typosquat	typosquat.levenshtein:got	AI (typosquat): Scoped @easbot/note is not impersonating 'got'; edit-distance match is spurious.	ai	2026/05/06
typosquat	typosquat.levenshtein:vite	AI (typosquat): Scoped @easbot/note is not impersonating 'vite'; edit-distance match is spurious.	ai	2026/05/06

Versions (showing 31 of 31)

Version	Deps	Published
0.2.30	13 / 8	2026-06-03
0.2.28	13 / 8	2026-06-03
0.2.27	13 / 8	2026-06-02
0.2.26	13 / 8	2026-05-31
0.2.25	13 / 8	2026-05-31
0.2.24	13 / 8	2026-05-30
0.2.23	13 / 8	2026-05-27
0.2.22	13 / 8	2026-05-26
0.2.21	13 / 8	2026-05-25
0.2.20	13 / 8	2026-05-24
0.2.19	13 / 8	2026-05-23
0.2.18	13 / 8	2026-05-23
0.2.16	13 / 8	2026-05-23
0.2.15	13 / 8	2026-05-23
0.2.14	13 / 8	2026-05-22
0.2.13	13 / 8	2026-05-21
0.2.11	13 / 8	2026-05-19
0.2.10	13 / 8	2026-05-17
0.2.9	13 / 8	2026-05-17
0.2.7	12 / 8	2026-05-17
0.2.6	12 / 8	2026-05-16
0.2.5	12 / 8	2026-05-15
0.2.4	12 / 8	2026-05-13
0.2.3	12 / 8	2026-05-13
0.2.2	12 / 8	2026-05-13
0.2.1	12 / 8	2026-05-04
0.2.0	12 / 8	2026-05-03
0.1.15	12 / 8	2026-05-02
0.1.14	12 / 8	2026-04-28
0.1.13	12 / 8	2026-04-23
0.1.11	12 / 8	2026-04-23

v0.2.30

1 finding

LOW No provenance attestation provenance

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

v0.2.28

1 finding

LOW No provenance attestation provenance

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

v0.2.27

1 finding

LOW No provenance attestation provenance

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

v0.2.26

1 finding

LOW No provenance attestation provenance

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

v0.2.25

1 finding

LOW No provenance attestation provenance

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

v0.2.24

1 finding

LOW No provenance attestation provenance

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

v0.2.23

1 finding

LOW No provenance attestation provenance

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

v0.2.22

1 finding

LOW No provenance attestation provenance

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

v0.2.21

1 finding

LOW No provenance attestation provenance

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

v0.2.20

1 finding

LOW No provenance attestation provenance

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

v0.2.19

1 finding

LOW No provenance attestation provenance

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

v0.2.18

1 finding

LOW No provenance attestation provenance

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

v0.2.16

1 finding

LOW No provenance attestation provenance

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

v0.2.15

1 finding

LOW No provenance attestation provenance

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

v0.2.14

1 finding

LOW No provenance attestation provenance

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

v0.2.13

1 finding

LOW No provenance attestation provenance

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

v0.2.11

1 finding

LOW No provenance attestation provenance

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

v0.2.10

1 finding

LOW No provenance attestation provenance

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

v0.2.9

1 finding

LOW No provenance attestation provenance

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

v0.2.7

1 finding

LOW No provenance attestation provenance

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

v0.2.6

1 finding

LOW No provenance attestation provenance

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

v0.2.5

2 findings

HIGH Missing gitHead — previous versions had it provenance

This version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: jallenhou.

LOW No provenance attestation provenance

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

v0.2.4

2 findings

HIGH Missing gitHead — previous versions had it provenance

This version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: jallenhou.

LOW No provenance attestation provenance

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

v0.2.3

2 findings

HIGH Missing gitHead — previous versions had it provenance

This version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: jallenhou.

LOW No provenance attestation provenance

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

v0.2.2

2 findings

HIGH Missing gitHead — previous versions had it provenance

This version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: jallenhou.

LOW No provenance attestation provenance

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

v0.2.1

1 finding

LOW No provenance attestation provenance

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

v0.2.0

1 finding

LOW No provenance attestation provenance

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

v0.1.15

1 finding

LOW No provenance attestation provenance

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

v0.1.14

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.13

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.11

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.