@easyink/designer
EasyInk document/report designer workbench
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 |
|---|---|---|---|---|
| dependencies | unvetted-dep:@easyink/locales | AI (dependencies): First-party @easyink monorepo sibling, pinned to matching version; not an external unvetted dep. | ai | |
| bogus-package | bogus-package | AI (bogus-package): New monorepo-style package family; sparse metadata is expected at this early stage, not a spam/malware indicator. | ai | |
| provenance | no-provenance | AI (provenance): New package family without provenance setup; consistent across all @easyink/* versions. | ai |
Versions (showing 9 of 9)
| Version | Deps | Published |
|---|---|---|
| 0.0.13 | 16 / 0 | |
| 0.0.11 | 16 / 0 | |
| 0.0.10 | 14 / 0 | |
| 0.0.9 | 14 / 0 | |
| 0.0.8 | 14 / 0 | |
| 0.0.7 | 14 / 0 | |
| 0.0.6 | 14 / 0 | |
| 0.0.5 | 14 / 0 | |
| 0.0.4 | 14 / 0 |
v0.0.13
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.11
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.10
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
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 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.7
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.6
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
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.4
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.