@aplus-frontend/ui
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
Keywords
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| npm-metadata | no-description | AI (npm-metadata): Org-internal component library; missing description is a stable pattern across all versions. | ai | |
| provenance | no-provenance | AI (provenance): No provenance across 487 versions; org does not use Sigstore CI publishing. | ai | |
| bogus-package | bogus-package | AI (bogus-package): Internal UI library; sparse metadata is consistent across 487 versions, not indicative of spam/malware. | ai | |
| typosquat | typosquat.levenshtein:joi | AI (typosquat): Same as above — scoped package name, not a typosquat of joi. | ai | |
| typosquat | typosquat.levenshtein:uuid | AI (typosquat): Scoped org package @aplus-frontend/ui; Levenshtein match to short names is noise, not a real typosquat. | ai | |
| phantom-deps | phantom-dep:@aplus-frontend/hooks | AI (phantom-deps): Same-org scoped dep; phantom-dep heuristic unreliable for monorepo packages. | ai | |
| typosquat | typosquat.levenshtein:yup | AI (typosquat): Same as above — scoped package name, not a typosquat of yup. | ai | |
| typosquat | typosquat.levenshtein:pg | AI (typosquat): Same as above — scoped package name, not a typosquat of pg. | ai | |
| typosquat | typosquat.levenshtein:qs | AI (typosquat): Same as above — scoped package name, not a typosquat of qs. | ai |
Versions (showing 38 of 38)
| Version | Deps | Published |
|---|---|---|
| 7.28.0 | 17 / 19 | |
| 7.27.1 | 17 / 12 | |
| 7.27.0 | 17 / 12 | |
| 7.26.10 | 17 / 12 | |
| 7.26.9 | 17 / 12 | |
| 7.26.8 | 17 / 12 | |
| 7.26.7 | 17 / 12 | |
| 7.26.6 | 17 / 12 | |
| 7.26.5 | 17 / 12 | |
| 7.26.4 | 17 / 12 | |
| 7.26.3 | 17 / 12 | |
| 7.26.2 | 17 / 12 | |
| 7.26.1 | 17 / 12 | |
| 7.26.0 | 17 / 12 | |
| 7.25.0 | 17 / 11 | |
| 7.24.1 | 17 / 11 | |
| 7.24.0 | 17 / 11 | |
| 7.23.2 | 17 / 11 | |
| 7.23.1 | 17 / 11 | |
| 7.23.0 | 17 / 11 | |
| 7.22.10 | 17 / 11 | |
| 7.22.9 | 17 / 11 | |
| 7.22.8 | 17 / 11 | |
| 7.22.7 | 17 / 11 | |
| 7.22.5 | 17 / 11 | |
| 7.22.4 | 17 / 11 | |
| 7.22.0 | 17 / 11 | |
| 7.21.1 | 17 / 11 | |
| 7.21.0 | 17 / 11 | |
| 7.10.6 | 17 / 11 | |
| 7.10.5 | 17 / 11 | |
| 7.10.4 | 17 / 11 | |
| 7.10.3 | 17 / 11 | |
| 7.10.2 | 17 / 11 | |
| 7.10.1 | 17 / 12 | |
| 7.10.0 | 16 / 12 | |
| 7.9.1 | 16 / 12 | |
| 7.9.0 | 16 / 12 |
v7.28.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v7.27.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v7.27.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v7.26.10
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v7.26.9
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v7.10.6
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v7.10.5
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v7.10.4
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v7.10.3
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v7.10.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v7.10.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v7.10.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v7.9.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.
v7.9.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.