@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, so a manually published version cannot be tied back to a reviewed commit.
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 73 of 73)
| Version | Deps | Published |
|---|---|---|
| 1.5.6 | 11 / 3 | |
| 1.5.5 | 11 / 3 | |
| 1.5.4 | 11 / 3 | |
| 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 | |
| 1.4.12 | 10 / 3 | |
| 1.4.11 | 10 / 3 | |
| 1.4.10 | 10 / 3 | |
| 1.4.9 | 10 / 3 | |
| 1.4.8 | 10 / 3 | |
| 1.4.6 | 10 / 3 | |
| 1.4.5 | 10 / 3 | |
| 1.4.4 | 10 / 3 | |
| 1.4.3 | 10 / 3 | |
| 1.4.1 | 10 / 3 | |
| 1.4.0 | 10 / 3 | |
| 1.3.9 | 10 / 3 | |
| 1.3.8 | 10 / 3 | |
| 1.3.7 | 10 / 3 | |
| 1.3.6 | 10 / 3 | |
| 1.3.5 | 10 / 3 | |
| 1.3.4 | 10 / 3 | |
| 1.3.3 | 10 / 3 | |
| 1.3.2 | 10 / 3 | |
| 1.3.1 | 10 / 3 | |
| 1.3.0 | 10 / 3 | |
| 1.2.17 | 9 / 3 | |
| 1.2.16 | 9 / 3 | |
| 1.2.15 | 9 / 3 | |
| 1.2.14 | 9 / 3 | |
| 1.2.13 | 9 / 3 | |
| 1.2.12 | 9 / 3 | |
| 1.2.11 | 9 / 3 | |
| 1.2.10 | 9 / 3 | |
| 1.2.9 | 9 / 3 | |
| 1.2.8 | 9 / 3 | |
| 1.2.7 | 9 / 3 | |
| 1.2.6 | 9 / 3 | |
| 1.2.5 | 9 / 3 | |
| 1.2.4 | 9 / 3 | |
| 1.2.3 | 9 / 3 | |
| 1.2.2 | 9 / 3 | |
| 1.2.1 | 9 / 3 | |
| 1.2.0 | 9 / 3 | |
| 1.1.9 | 9 / 3 | |
| 1.1.8 | 9 / 3 | |
| 1.1.7 | 9 / 3 | |
| 1.1.6 | 9 / 3 | |
| 1.1.5 | 9 / 3 | |
| 1.1.4 | 9 / 3 | |
| 1.1.3 | 9 / 3 | |
| 1.1.2 | 9 / 3 | |
| 1.1.1 | 9 / 3 | |
| 1.1.0 | 9 / 3 |
v1.5.6
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.5.5
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.4.12
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.4.11
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.4.10
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.4.9
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.4.8
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.4.6
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.4.5
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.4.4
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.4.3
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.4.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.4.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.3.9
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.3.8
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.3.7
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.3.6
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.3.5
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.3.4
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.3.3
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.3.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.3.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.3.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.2.17
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.2.16
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.2.15
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.2.14
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.2.13
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.2.12
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.2.11
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.2.10
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.2.9
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.2.8
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.2.7
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.2.6
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.2.5
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.2.4
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.2.3
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.2.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.2.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.2.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.1.9
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.1.8
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.1.7
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.1.6
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.1.5
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.1.4
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.1.3
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.1.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.1.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.1.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.