@kevisual/api
对 kevisual 相关的query router 的模块整理
Supply chain provenance
Status for the latest visible version.
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
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| publish-pattern | new-deps-added | AI (publish-pattern): sonner and zustand are established libraries; @kevisual/context is from the same publisher org. No malicious indicators. | ai | |
| phantom-deps | phantom-dep:nanoid | AI (phantom-deps): Declared runtime dep likely consumed via bundled dist; stable false positive for this package. | ai | |
| phantom-deps | phantom-dep:es-toolkit | AI (phantom-deps): Declared runtime dep likely consumed via bundled dist; stable false positive for this package. | ai | |
| bogus-package | bogus-package | AI (bogus-package): Active package with 64 versions and 332-day history; missing metadata is a style issue, not a spam indicator. | ai | |
| typosquat | typosquat.levenshtein:hapi | AI (typosquat): Scoped @kevisual org package; not impersonating hapi. 64 versions published over 332 days. | ai | |
| typosquat | typosquat.levenshtein:ajv | AI (typosquat): Scoped @kevisual org package; Levenshtein match to 'ajv' is coincidental. | ai | |
| typosquat | typosquat.levenshtein:joi | AI (typosquat): Scoped @kevisual org package; Levenshtein match to 'joi' is coincidental. | ai | |
| typosquat | typosquat.levenshtein:pg | AI (typosquat): Scoped @kevisual org package; Levenshtein match to 'pg' is coincidental. | ai |
Versions (showing 64 of 64)
| Version | Deps | Published |
|---|---|---|
| 0.0.71 | 13 / 13 | |
| 0.0.70 | 13 / 13 | |
| 0.0.69 | 13 / 13 | |
| 0.0.68 | 13 / 13 | |
| 0.0.67 | 13 / 13 | |
| 0.0.66 | 13 / 13 | |
| 0.0.65 | 13 / 13 | |
| 0.0.64 | 12 / 13 | |
| 0.0.63 | 12 / 13 | |
| 0.0.62 | 12 / 13 | |
| 0.0.61 | 12 / 13 | |
| 0.0.60 | 12 / 13 | |
| 0.0.59 | 12 / 13 | |
| 0.0.58 | 12 / 13 | |
| 0.0.57 | 12 / 13 | |
| 0.0.56 | 12 / 13 | |
| 0.0.55 | 12 / 13 | |
| 0.0.54 | 12 / 13 | |
| 0.0.53 | 12 / 13 | |
| 0.0.52 | 12 / 13 | |
| 0.0.51 | 12 / 13 | |
| 0.0.50 | 11 / 13 | |
| 0.0.49 | 11 / 13 | |
| 0.0.48 | 8 / 15 | |
| 0.0.47 | 8 / 15 | |
| 0.0.46 | 8 / 15 | |
| 0.0.44 | 8 / 13 | |
| 0.0.43 | 8 / 13 | |
| 0.0.42 | 9 / 11 | |
| 0.0.41 | 9 / 11 | |
| 0.0.40 | 9 / 11 | |
| 0.0.39 | 9 / 11 | |
| 0.0.38 | 9 / 11 | |
| 0.0.37 | 9 / 11 | |
| 0.0.35 | 7 / 11 | |
| 0.0.34 | 7 / 11 | |
| 0.0.33 | 7 / 11 | |
| 0.0.32 | 7 / 11 | |
| 0.0.31 | 7 / 11 | |
| 0.0.30 | 7 / 11 | |
| 0.0.29 | 7 / 11 | |
| 0.0.28 | 6 / 9 | |
| 0.0.26 | 5 / 9 | |
| 0.0.25 | 5 / 9 | |
| 0.0.24 | 5 / 9 | |
| 0.0.23 | 5 / 9 | |
| 0.0.22 | 5 / 9 | |
| 0.0.21 | 5 / 9 | |
| 0.0.20 | 5 / 9 | |
| 0.0.19 | 5 / 9 | |
| 0.0.18 | 5 / 9 | |
| 0.0.17 | 5 / 9 | |
| 0.0.16 | 5 / 9 | |
| 0.0.15 | 5 / 9 | |
| 0.0.14 | 5 / 9 | |
| 0.0.12 | 5 / 9 | |
| 0.0.11 | 5 / 9 | |
| 0.0.10 | 4 / 9 | |
| 0.0.9 | 4 / 9 | |
| 0.0.8 | 3 / 9 | |
| 0.0.7 | 3 / 9 | |
| 0.0.6 | 3 / 9 | |
| 0.0.5 | 2 / 8 | |
| 0.0.1 | 2 / 2 |
v0.0.71
2 findingsPackage name '@kevisual/api' is 1 edit(s) away from popular package 'hapi'.
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.70
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.69
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.68
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.67
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.66
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.65
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.64
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.63
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.62
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.61
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.60
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.59
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.58
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.57
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.56
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.55
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.54
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.53
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.52
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.51
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.50
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.49
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.48
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.47
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.46
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.44
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.43
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.42
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.41
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.40
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.39
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.38
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.37
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.35
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.34
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.33
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.32
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.31
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.30
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.29
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.28
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.26
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.25
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.24
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.23
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.22
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.21
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.20
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.19
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.18
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.17
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.16
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.15
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.14
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.12
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.11
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.10
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.9
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.8
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.7
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.6
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.5
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.