@nextclaw/core No license 51 versions

@nextclaw/core

npm

51

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
dependencies	unvetted-dep:dingtalk-stream	AI (dependencies): Legitimate DingTalk messaging SDK; expected dependency for a multi-channel agent framework.	ai	2026/05/02
dependencies	unvetted-dep:node-telegram-bot-api	AI (dependencies): Well-known Telegram bot SDK; expected dependency for a multi-channel agent framework.	ai	2026/05/02
phantom-deps	phantom-dep:dotenv	AI (phantom-deps): Declared in dependencies; referenced in config files as expected for a runtime core package.	ai	2026/04/28
phantom-deps	phantom-dep:chokidar	AI (phantom-deps): Declared in dependencies; file-watching use in a runtime core is expected.	ai	2026/04/28
typosquat	typosquat.levenshtein:cors	AI (typosquat): @nextclaw/core is a scoped package in its own namespace; Levenshtein match to 'cors' is a false positive.	ai	2026/04/28
phantom-deps	phantom-dep:socket.io-msgpack-parser	AI (phantom-deps): Declared in dependencies; optional parser likely loaded conditionally.	ai	2026/04/28
phantom-deps	phantom-dep:commander	AI (phantom-deps): Declared in dependencies; CLI tooling use in a runtime core is expected.	ai	2026/04/28
phantom-deps	phantom-dep:pino	AI (phantom-deps): Declared in dependencies; likely used via config/dynamic import in a runtime framework.	ai	2026/04/28

Versions (showing 51 of 116)

View all versions

Version	Deps	Published
0.14.1	12 / 5	2026-06-06
0.13.9	12 / 5	2026/06/03
0.13.8	12 / 5	2026-06-03
0.13.7	12 / 5	2026-06-03
0.13.6	12 / 5	2026-06-03
0.13.5	12 / 5	2026-06-02
0.13.4	12 / 5	2026-06-02
0.13.3	12 / 5	2026-06-02
0.13.2	12 / 5	2026-06-02
0.13.1	12 / 5	2026-06-01
0.13.0	12 / 5	2026-05-29
0.12.27	12 / 5	2026-05-29
0.12.26	12 / 5	2026-05-28
0.12.25	12 / 5	2026-05-28
0.12.24	12 / 5	2026-05-24
0.12.23	12 / 5	2026-05-23
0.12.22	12 / 5	2026-05-23
0.12.21	12 / 5	2026-05-22
0.12.20	12 / 5	2026-05-22
0.12.19	12 / 5	2026-05-19
0.12.18	12 / 5	2026-05-19
0.12.17	12 / 5	2026-05-16
0.12.16	12 / 5	2026-05-13
0.12.15	12 / 5	2026-05-13
0.12.14	12 / 5	2026-05-12
0.12.13	11 / 5	2026-05-07
0.12.12	11 / 5	2026-04-25
0.12.11	11 / 5	2026-04-23
0.12.10	11 / 5	2026-04-19
0.12.9	11 / 5	2026-04-18
0.12.8	11 / 5	2026-04-17
0.12.7	11 / 5	2026-04-17
0.12.6	11 / 5	2026-04-14
0.12.5	11 / 5	2026-04-12
0.12.4	11 / 5	2026-04-12
0.12.3	11 / 5	2026-04-09
0.12.2	11 / 5	2026-04-08
0.12.1	11 / 5	2026-04-07
0.12.0	11 / 6	2026-04-06
0.11.17	11 / 6	2026-04-04
0.11.16	11 / 6	2026-04-02
0.11.15	11 / 6	2026-04-01
0.11.14	11 / 6	2026-03-31
0.11.13	11 / 6	2026-03-31
0.11.12	11 / 6	2026-03-31
0.11.11	11 / 6	2026-03-30
0.11.10	11 / 6	2026-03-30
0.11.9	11 / 6	2026-03-30
0.11.8	11 / 6	2026-03-30
0.11.7	11 / 6	2026-03-30
0.11.6	11 / 6	2026-03-29

v0.14.1

1 finding

LOW No provenance attestation provenance

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

v0.13.9

1 finding

LOW No provenance attestation provenance

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

v0.13.8

1 finding

LOW No provenance attestation provenance

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

v0.13.7

1 finding

LOW No provenance attestation provenance

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

v0.13.6

1 finding

LOW No provenance attestation provenance

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

v0.13.5

1 finding

LOW No provenance attestation provenance

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

v0.13.4

1 finding

LOW No provenance attestation provenance

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

v0.13.3

1 finding

LOW No provenance attestation provenance

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

v0.13.2

1 finding

LOW No provenance attestation provenance

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

v0.13.1

1 finding

LOW No provenance attestation provenance

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

v0.13.0

1 finding

LOW No provenance attestation provenance

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

v0.12.27

1 finding

LOW No provenance attestation provenance

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

v0.12.26

1 finding

LOW No provenance attestation provenance

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

v0.12.25

1 finding

LOW No provenance attestation provenance

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

v0.12.24

1 finding

LOW No provenance attestation provenance

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

v0.12.23

1 finding

LOW No provenance attestation provenance

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

v0.12.22

1 finding

LOW No provenance attestation provenance

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

v0.12.21

1 finding

LOW No provenance attestation provenance

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

v0.12.20

1 finding

LOW No provenance attestation provenance

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

v0.12.19

1 finding

LOW No provenance attestation provenance

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

v0.12.18

1 finding

LOW No provenance attestation provenance

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

v0.12.17

1 finding

LOW No provenance attestation provenance

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

v0.12.16

1 finding

LOW No provenance attestation provenance

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

v0.12.15

1 finding

LOW No provenance attestation provenance

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

v0.12.14

1 finding

LOW No provenance attestation provenance

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

v0.12.13

1 finding

LOW No provenance attestation provenance

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

v0.12.12

2 findings

HIGH typosquat.levenshtein: Possible typosquat of 'cors' typosquat

Package name '@nextclaw/core' is 1 edit(s) away from popular package 'cors'.

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

1 finding

LOW No provenance attestation provenance

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

v0.12.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.12.7

1 finding

LOW No provenance attestation provenance

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

v0.12.6

1 finding

LOW No provenance attestation provenance

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

v0.12.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.12.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.12.3

1 finding

LOW No provenance attestation provenance

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

v0.12.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.12.1

1 finding

LOW No provenance attestation provenance

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

v0.12.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.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.11.16

1 finding

LOW No provenance attestation provenance

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

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

1 finding

LOW No provenance attestation provenance

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

v0.11.12

1 finding

LOW No provenance attestation provenance

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

v0.11.11

1 finding

LOW No provenance attestation provenance

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

v0.11.10

1 finding

LOW No provenance attestation provenance

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

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