@nextclaw/channel-plugin-feishu No license 44 versions

@nextclaw/channel-plugin-feishu

npm

44

Versions

—

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

peiiii

Accepted risks

Findings the reviewer chose to accept rather than block on.

Source	Rule	Reason	Accepted by	When
bogus-package	bogus-package	AI (bogus-package): Small scoped plugin in active @nextclaw ecosystem; sparse metadata is consistent with internal/plugin packages.	ai	2026/05/07
semgrep	semgrep:etc-passwd-access	AI (semgrep): Reference is in a test asserting the function rejects path traversal — not credential harvesting.	ai	2026/05/02
semgrep	semgrep:shady-links-raw-ip	AI (semgrep): 127.0.0.1 used in a test helper for a local server — not an exfiltration endpoint.	ai	2026/05/02
semgrep	semgrep:base64-decode	AI (semgrep): Decoding base64 image data into a buffer for docx processing — standard pattern, no obfuscation.	ai	2026/05/02

Versions (showing 44 of 44)

Version	Deps	Published
0.2.32	4 / 0	2026-05-13
0.2.31	4 / 0	2026-05-13
0.2.30	4 / 0	2026-05-12
0.2.29	4 / 0	2026-05-07
0.2.28	4 / 0	2026-04-23
0.2.27	4 / 0	2026-04-19
0.2.26	4 / 0	2026-04-18
0.2.25	4 / 0	2026-04-17
0.2.24	4 / 0	2026-04-14
0.2.23	4 / 0	2026-03-31
0.2.22	4 / 0	2026-03-30
0.2.21	4 / 0	2026-03-26
0.2.20	4 / 0	2026-03-26
0.2.19	4 / 0	2026-03-24
0.2.18	4 / 0	2026-03-24
0.2.17	4 / 0	2026-03-24
0.2.16	4 / 0	2026-03-24
0.2.15	4 / 0	2026-03-24
0.2.14	5 / 0	2026-03-24
0.2.13	1 / 0	2026-03-24
0.2.12	1 / 0	2026-03-23
0.2.11	1 / 0	2026-03-23
0.2.10	1 / 0	2026-03-23
0.2.8	1 / 0	2026-03-22
0.2.7	1 / 0	2026-03-21
0.2.6	1 / 0	2026-03-21
0.2.5	1 / 0	2026-03-19
0.2.4	1 / 0	2026-03-19
0.2.3	1 / 0	2026-03-19
0.2.2	1 / 0	2026-03-19
0.2.1	1 / 0	2026-03-19
0.2.0	1 / 0	2026-03-18
0.1.12	1 / 0	2026-03-17
0.1.11	1 / 0	2026-03-12
0.1.10	1 / 0	2026-03-12
0.1.9	1 / 0	2026-03-11
0.1.8	1 / 0	2026-03-10
0.1.7	1 / 0	2026-03-09
0.1.6	1 / 0	2026-03-02
0.1.5	1 / 0	2026-02-23
0.1.4	1 / 0	2026-02-23
0.1.2	1 / 0	2026-02-21
0.1.1	1 / 0	2026-02-19
0.1.0	1 / 0	2026-02-19

v0.2.32

1 finding

LOW No provenance attestation provenance

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

v0.2.31

1 finding

LOW No provenance attestation provenance

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

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

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

2 findings

HIGH etc-passwd-access: src/external-keys.test.ts:10 semgrep

Accessing /etc/passwd or /etc/shadow — credential harvesting on Linux 8 | 9 | it("rejects traversal and path separator patterns", () => { > 10 | expect(normalizeFeishuExternalKey("../etc/passwd")).toBeUndefined(); 11 | expect(normalizeFeishuExternalKey("a/../../b")).toBeUndefined(); 12 | expect(normalizeFeishuExternalKey("a\\..\\b")).toBeUndefined();

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

2 findings

HIGH etc-passwd-access: src/external-keys.test.ts:10 semgrep

Accessing /etc/passwd or /etc/shadow — credential harvesting on Linux 8 | 9 | it("rejects traversal and path separator patterns", () => { > 10 | expect(normalizeFeishuExternalKey("../etc/passwd")).toBeUndefined(); 11 | expect(normalizeFeishuExternalKey("a/../../b")).toBeUndefined(); 12 | expect(normalizeFeishuExternalKey("a\\..\\b")).toBeUndefined();

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

2 findings

HIGH etc-passwd-access: src/external-keys.test.ts:10 semgrep

Accessing /etc/passwd or /etc/shadow — credential harvesting on Linux 8 | 9 | it("rejects traversal and path separator patterns", () => { > 10 | expect(normalizeFeishuExternalKey("../etc/passwd")).toBeUndefined(); 11 | expect(normalizeFeishuExternalKey("a/../../b")).toBeUndefined(); 12 | expect(normalizeFeishuExternalKey("a\\..\\b")).toBeUndefined();

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

2 findings

HIGH etc-passwd-access: src/external-keys.test.ts:10 semgrep

Accessing /etc/passwd or /etc/shadow — credential harvesting on Linux 8 | 9 | it("rejects traversal and path separator patterns", () => { > 10 | expect(normalizeFeishuExternalKey("../etc/passwd")).toBeUndefined(); 11 | expect(normalizeFeishuExternalKey("a/../../b")).toBeUndefined(); 12 | expect(normalizeFeishuExternalKey("a\\..\\b")).toBeUndefined();

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

2 findings

HIGH etc-passwd-access: src/external-keys.test.ts:10 semgrep

Accessing /etc/passwd or /etc/shadow — credential harvesting on Linux 8 | 9 | it("rejects traversal and path separator patterns", () => { > 10 | expect(normalizeFeishuExternalKey("../etc/passwd")).toBeUndefined(); 11 | expect(normalizeFeishuExternalKey("a/../../b")).toBeUndefined(); 12 | expect(normalizeFeishuExternalKey("a\\..\\b")).toBeUndefined();

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

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

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

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

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

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

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

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

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

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.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.2.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.2.12

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

v0.2.10

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.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.2.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.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.12

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.

v0.1.10

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