@kevisual/ai No license 27 versions

@kevisual/ai

npm

27

Versions

—

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

kevisual

Keywords

kevisualaitools

Accepted risks

Findings the reviewer chose to accept rather than block on.

Source	Rule	Reason	Accepted by	When
phantom-deps	phantom-dep:@kevisual/logger	AI (phantom-deps): Same-org dep; may be used indirectly via re-exports or runtime config — stable false positive for this package.	ai	2026/05/20
typosquat	typosquat.levenshtein:pg	AI (typosquat): Scoped package @kevisual/ai; Levenshtein match to 'pg' is a false positive.	ai	2026/05/20
typosquat	typosquat.levenshtein:qs	AI (typosquat): Scoped package @kevisual/ai; Levenshtein match to 'qs' is a false positive.	ai	2026/05/20
typosquat	typosquat.levenshtein:joi	AI (typosquat): Scoped package @kevisual/ai; Levenshtein match to 'joi' is a false positive.	ai	2026/05/20
typosquat	typosquat.levenshtein:ajv	AI (typosquat): Scoped package @kevisual/ai; Levenshtein match to 'ajv' is a false positive.	ai	2026/05/20
typosquat	typosquat.levenshtein:hapi	AI (typosquat): Scoped package @kevisual/ai; Levenshtein match to 'hapi' is a false positive.	ai	2026/05/20
phantom-deps	phantom-dep:@ai-sdk/anthropic	AI (phantom-deps): Same as @ai-sdk/openai; config-based usage pattern, stable false positive.	ai	2026/05/20
phantom-deps	phantom-dep:@ai-sdk/openai-compatible	AI (phantom-deps): Same as other @ai-sdk/* deps; config-based usage pattern, stable false positive.	ai	2026/05/20
phantom-deps	phantom-dep:@kevisual/permission	AI (phantom-deps): Same-org scoped dep; phantom detection is a false positive for this package.	ai	2026/05/20
phantom-deps	phantom-dep:@ai-sdk/openai	AI (phantom-deps): AI SDK deps declared as runtime deps but used via config/re-export pattern; stable false positive for this package.	ai	2026/05/20

Versions (showing 27 of 27)

Version	Deps	Published
0.0.33	10 / 18	2026-04-17
0.0.29	9 / 18	2026-04-06
0.0.28	9 / 18	2026-03-11
0.0.27	9 / 18	2026-03-10
0.0.26	3 / 17	2026-03-02
0.0.25	3 / 17	2026-03-02
0.0.24	3 / 17	2026-01-26
0.0.23	3 / 17	2026-01-26
0.0.22	3 / 17	2026-01-23
0.0.21	3 / 17	2026-01-18
0.0.20	3 / 17	2026-01-10
0.0.19	3 / 17	2025-12-08
0.0.18	3 / 17	2025-12-08
0.0.17	3 / 17	2025-12-08
0.0.16	3 / 30	2025-12-05
0.0.15	2 / 30	2025-12-04
0.0.14	2 / 30	2025-12-04
0.0.13	2 / 30	2025-12-04
0.0.12	1 / 30	2025-11-23
0.0.11	1 / 30	2025-10-23
0.0.10	1 / 30	2025-10-23
0.0.9	1 / 30	2025-08-07
0.0.8	1 / 30	2025-06-21
0.0.7	1 / 30	2025-06-21
0.0.6	1 / 30	2025-06-09
0.0.5	1 / 30	2025-05-26
0.0.4	1 / 30	2025-05-25

v0.0.33

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

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

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

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

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

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

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