@akinon/ui-tree-select
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 |
|---|---|---|---|---|
| publish-pattern | new-deps-added | AI (publish-pattern): New deps are first-party @akinon/* or established packages (classnames, @ant-design/cssinjs); consistent with UI component expansion. | ai | |
| bogus-package | bogus-package | AI (bogus-package): Akinon org packages consistently lack descriptions/repo URLs; not indicative of spam or malice. | ai |
Versions (showing 16 of 16)
| Version | Deps | Published |
|---|---|---|
| 1.1.13 | 5 / 5 | |
| 1.1.12 | 5 / 5 | |
| 1.1.11 | 5 / 5 | |
| 1.1.10 | 5 / 5 | |
| 1.1.9 | 5 / 5 | |
| 1.1.8 | 5 / 5 | |
| 1.1.7 | 5 / 5 | |
| 1.1.6 | 5 / 5 | |
| 1.1.5 | 5 / 5 | |
| 1.1.4 | 1 / 5 | |
| 1.1.3 | 1 / 5 | |
| 1.1.2 | 1 / 5 | |
| 1.1.1 | 1 / 5 | |
| 1.1.0 | 1 / 5 | |
| 1.0.1 | 1 / 5 | |
| 1.0.0 | 1 / 5 |
v1.1.13
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.1.12
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.1.11
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.1.10
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.1.9
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.