@lemon-fe/kits
> TODO: description
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 |
|---|---|---|---|---|
| provenance | no-provenance | AI (provenance): Established internal monorepo package; provenance absence is consistent across all 506 versions. | ai | |
| phantom-deps | phantom-dep:ag-grid-community | AI (phantom-deps): ag-grid-community is a declared runtime dep; phantom-dep heuristic false positive for this package. | ai | |
| typosquat | typosquat.levenshtein:vite | AI (typosquat): Scoped package @lemon-fe/kits; edit-distance match to 'vite' is a false positive with no plausible impersonation intent. | ai | |
| phantom-deps | phantom-dep:@ant-design/icons | AI (phantom-deps): @ant-design/icons is a declared runtime dep; phantom-dep heuristic fires because it's re-exported via the component library rather than directly imported. | ai |
Versions (showing 21 of 21)
| Version | Deps | Published |
|---|---|---|
| 1.5.3 | 11 / 3 | |
| 1.5.2 | 11 / 3 | |
| 1.5.1 | 11 / 3 | |
| 1.5.0 | 11 / 3 | |
| 1.4.29 | 11 / 3 | |
| 1.4.28 | 11 / 3 | |
| 1.4.27 | 11 / 3 | |
| 1.4.26 | 11 / 3 | |
| 1.4.25 | 11 / 3 | |
| 1.4.24 | 11 / 3 | |
| 1.4.23 | 11 / 3 | |
| 1.4.22 | 11 / 3 | |
| 1.4.21 | 10 / 3 | |
| 1.4.20 | 10 / 3 | |
| 1.4.19 | 10 / 3 | |
| 1.4.18 | 10 / 3 | |
| 1.4.17 | 10 / 3 | |
| 1.4.16 | 10 / 3 | |
| 1.4.15 | 10 / 3 | |
| 1.4.14 | 10 / 3 | |
| 1.4.13 | 10 / 3 |
v1.5.3
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.5.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.5.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.4.29
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.4.28
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.4.27
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.4.26
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.4.25
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.4.24
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.4.23
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.4.22
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.4.21
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.4.20
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.4.19
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.4.18
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.4.17
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.4.16
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.4.15
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.4.14
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.4.13
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.