@easyink/ai
AI integration for EasyInk designer (chat, MCP, prompt templates)
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 |
|---|---|---|---|---|
| phantom-deps | phantom-dep:@vueuse/core | AI (phantom-deps): @vueuse/core is explicitly declared as a runtime dependency in package.json; phantom-dep is a false positive here. | ai | |
| typosquat | typosquat.levenshtein:hapi | AI (typosquat): Scoped @easyink/ai is not a typosquat of hapi; short-name edit-distance FP. | ai | |
| typosquat | typosquat.levenshtein:pg | AI (typosquat): Scoped @easyink/ai is not a typosquat of pg; short-name edit-distance FP. | ai | |
| typosquat | typosquat.levenshtein:qs | AI (typosquat): Scoped @easyink/ai is not a typosquat of qs; short-name edit-distance FP. | ai | |
| typosquat | typosquat.levenshtein:joi | AI (typosquat): Scoped @easyink/ai is not a typosquat of joi; short-name edit-distance FP. | ai | |
| typosquat | typosquat.levenshtein:ajv | AI (typosquat): Scoped @easyink/ai is not a typosquat of ajv; short-name edit-distance FP. | ai |
Versions (showing 14 of 14)
| Version | Deps | Published |
|---|---|---|
| 0.0.17 | 8 / 0 | |
| 0.0.16 | 8 / 0 | |
| 0.0.14 | 8 / 0 | |
| 0.0.13 | 8 / 0 | |
| 0.0.11 | 8 / 0 | |
| 0.0.10 | 8 / 0 | |
| 0.0.9 | 8 / 0 | |
| 0.0.8 | 8 / 0 | |
| 0.0.7 | 8 / 0 | |
| 0.0.6 | 8 / 0 | |
| 0.0.5 | 8 / 0 | |
| 0.0.4 | 8 / 0 | |
| 0.0.3 | 9 / 0 | |
| 0.0.1 | 9 / 0 |
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.14
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.13
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. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.10
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.9
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.8
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.7
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.6
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.5
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.3
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.