@aiready/core MIT 51 versions

@aiready/core

npm Repository Homepage

Shared utilities for AIReady analysis tools

51

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

caopeng

Keywords

aireadycode-analysisutilities

Accepted risks

Findings the reviewer chose to accept rather than block on.

Source	Rule	Reason	Accepted by	When
phantom-deps	phantom-dep:minimatch	AI (phantom-deps): Utility dep used in config/build context; stable false positive for this package.	ai	2026/05/25
typosquat	typosquat.levenshtein:cors	AI (typosquat): @aiready/core is a scoped AI code-analysis package; 'cors' similarity is coincidental and not impersonation.	ai	2026/05/20
phantom-deps	phantom-dep:tree-sitter-wasms	AI (phantom-deps): Platform-specific binary grammar package; dynamic loading pattern is expected for tree-sitter tooling.	ai	2026/05/20
phantom-deps	phantom-dep:tree-sitter-java	AI (phantom-deps): Tree-sitter language grammar; dynamically loaded, not directly imported.	ai	2026/05/20
phantom-deps	phantom-dep:tree-sitter-python	AI (phantom-deps): Tree-sitter language grammar; dynamically loaded, not directly imported.	ai	2026/05/20
phantom-deps	phantom-dep:typescript	AI (phantom-deps): Used as a library dependency for AST parsing, not just a dev tool; phantom-dep is a false positive here.	ai	2026/05/20
phantom-deps	phantom-dep:@typescript-eslint/parser	AI (phantom-deps): Used programmatically for parsing; phantom-dep heuristic misses dynamic usage.	ai	2026/05/20
phantom-deps	phantom-dep:@unit-mesh/treesitter-artifacts	AI (phantom-deps): Tree-sitter artifact bundle; dynamically loaded, expected phantom-dep pattern.	ai	2026/05/20

Versions (showing 51 of 148)

View all versions

Version	Deps	Published
0.29.10	16 / 4	2026-05-10
0.29.8	16 / 4	2026-05-05
0.29.7	16 / 4	2026-05-03
0.29.5	16 / 4	2026-04-29
0.29.4	16 / 4	2026-04-14
0.29.1	15 / 4	2026-04-12
0.29.0	15 / 4	2026-04-11
0.28.0	15 / 4	2026-04-11
0.24.27	15 / 4	2026-04-11
0.24.26	15 / 4	2026-04-08
0.24.25	15 / 4	2026-04-08
0.24.23	13 / 2	2026-04-06
0.24.22	13 / 2	2026-04-06
0.24.21	13 / 2	2026-04-06
0.24.20	13 / 2	2026-04-06
0.24.19	13 / 2	2026-04-04
0.24.18	13 / 2	2026-04-04
0.24.16	13 / 2	2026-04-01
0.24.15	13 / 2	2026-04-01
0.24.14	13 / 2	2026-03-31
0.24.13	13 / 2	2026-03-31
0.24.12	13 / 2	2026-03-31
0.24.10	13 / 2	2026-03-31
0.24.9	12 / 2	2026-03-29
0.24.8	12 / 2	2026-03-29
0.24.7	12 / 2	2026-03-29
0.24.6	12 / 2	2026-03-28
0.24.5	12 / 2	2026-03-27
0.24.4	12 / 2	2026-03-27
0.24.3	12 / 2	2026-03-27
0.24.2	12 / 2	2026-03-27
0.24.1	12 / 2	2026-03-26
0.24.0	12 / 2	2026-03-26
0.23.24	12 / 2	2026-03-25
0.23.23	12 / 2	2026-03-23
0.23.22	12 / 2	2026-03-23
0.23.21	12 / 2	2026-03-22
0.23.20	12 / 2	2026-03-22
0.23.19	12 / 2	2026-03-21
0.23.15	12 / 2	2026-03-21
0.23.14	12 / 2	2026-03-20
0.23.13	12 / 2	2026-03-20
0.23.12	12 / 2	2026-03-19
0.23.11	12 / 2	2026-03-19
0.23.10	12 / 2	2026-03-19
0.23.9	12 / 2	2026-03-19
0.23.8	12 / 2	2026-03-19
0.23.7	12 / 2	2026-03-17
0.23.6	12 / 2	2026-03-17
0.23.5	12 / 2	2026-03-17
0.23.4	12 / 2	2026-03-15

v0.29.10

1 finding

LOW No provenance attestation provenance

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

v0.29.8

2 findings

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

Package name '@aiready/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.29.7

2 findings

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

Package name '@aiready/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.29.5

2 findings

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

Package name '@aiready/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.29.4

1 finding

LOW No provenance attestation provenance

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

v0.29.1

2 findings

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

Package name '@aiready/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.29.0

1 finding

LOW No provenance attestation provenance

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

v0.28.0

1 finding

LOW No provenance attestation provenance

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

v0.24.27

1 finding

LOW No provenance attestation provenance

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

v0.24.26

1 finding

LOW No provenance attestation provenance

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

v0.24.25

1 finding

LOW No provenance attestation provenance

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

v0.24.23

2 findings

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

Package name '@aiready/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.24.22

2 findings

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

Package name '@aiready/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.24.21

1 finding

LOW No provenance attestation provenance

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

v0.24.20

1 finding

LOW No provenance attestation provenance

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

v0.24.19

2 findings

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

Package name '@aiready/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.24.18

1 finding

LOW No provenance attestation provenance

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

v0.24.16

1 finding

LOW No provenance attestation provenance

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

v0.24.15

1 finding

LOW No provenance attestation provenance

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

v0.24.14

1 finding

LOW No provenance attestation provenance

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

v0.24.13

1 finding

LOW No provenance attestation provenance

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

v0.24.12

1 finding

LOW No provenance attestation provenance

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

v0.24.10

1 finding

LOW No provenance attestation provenance

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

v0.24.9

1 finding

LOW No provenance attestation provenance

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

v0.24.8

1 finding

LOW No provenance attestation provenance

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

v0.24.7

1 finding

LOW No provenance attestation provenance

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

v0.24.6

1 finding

LOW No provenance attestation provenance

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

v0.24.5

1 finding

LOW No provenance attestation provenance

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

v0.24.4

1 finding

LOW No provenance attestation provenance

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

v0.24.3

1 finding

LOW No provenance attestation provenance

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

v0.24.2

1 finding

LOW No provenance attestation provenance

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

v0.24.1

1 finding

LOW No provenance attestation provenance

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

v0.24.0

1 finding

LOW No provenance attestation provenance

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

v0.23.24

1 finding

LOW No provenance attestation provenance

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

v0.23.23

1 finding

LOW No provenance attestation provenance

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

v0.23.22

1 finding

LOW No provenance attestation provenance

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

v0.23.21

1 finding

LOW No provenance attestation provenance

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

v0.23.20

1 finding

LOW No provenance attestation provenance

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

v0.23.19

1 finding

LOW No provenance attestation provenance

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

v0.23.15

1 finding

LOW No provenance attestation provenance

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

v0.23.14

1 finding

LOW No provenance attestation provenance

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

v0.23.13

1 finding

LOW No provenance attestation provenance

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

v0.23.12

1 finding

LOW No provenance attestation provenance

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

v0.23.11

1 finding

LOW No provenance attestation provenance

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

v0.23.10

2 findings

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

Package name '@aiready/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.23.9

1 finding

LOW No provenance attestation provenance

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

v0.23.8

1 finding

LOW No provenance attestation provenance

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

v0.23.7

1 finding

LOW No provenance attestation provenance

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

v0.23.6

1 finding

LOW No provenance attestation provenance

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

v0.23.5

1 finding

LOW No provenance attestation provenance

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

v0.23.4

2 findings

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

Package name '@aiready/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.