@ticatec/uniface-app-component
uniface web app components base on the uniface web elements
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): Publisher consistently publishes without provenance; stable pattern across this package family. | ai | |
| phantom-deps | phantom-dep:@ticatec/restful_service_api | AI (phantom-deps): Same-org scoped dep; phantom flag is a stable false positive for this package family. | ai |
Versions (showing 40 of 40)
| Version | Deps | Published |
|---|---|---|
| 0.2.8 | 1 / 28 | |
| 0.2.7 | 1 / 28 | |
| 0.2.6 | 1 / 28 | |
| 0.2.5 | 1 / 28 | |
| 0.2.4 | 1 / 28 | |
| 0.2.3 | 1 / 28 | |
| 0.2.2 | 1 / 28 | |
| 0.2.1 | 1 / 28 | |
| 0.2.0 | 1 / 28 | |
| 0.1.5 | 1 / 27 | |
| 0.1.4 | 1 / 27 | |
| 0.1.3 | 1 / 27 | |
| 0.1.2 | 1 / 27 | |
| 0.1.1 | 0 / 26 | |
| 0.1.0 | 0 / 26 | |
| 0.0.26 | 0 / 26 | |
| 0.0.25 | 0 / 26 | |
| 0.0.24 | 0 / 26 | |
| 0.0.23 | 0 / 26 | |
| 0.0.22 | 0 / 26 | |
| 0.0.21 | 0 / 26 | |
| 0.0.20 | 0 / 26 | |
| 0.0.19 | 0 / 25 | |
| 0.0.18 | 0 / 25 | |
| 0.0.17 | 0 / 25 | |
| 0.0.16 | 0 / 25 | |
| 0.0.15 | 0 / 25 | |
| 0.0.14 | 0 / 25 | |
| 0.0.13 | 0 / 25 | |
| 0.0.12 | 0 / 25 | |
| 0.0.11 | 0 / 25 | |
| 0.0.10 | 1 / 24 | |
| 0.0.9 | 1 / 24 | |
| 0.0.8 | 1 / 24 | |
| 0.0.7 | 1 / 24 | |
| 0.0.6 | 1 / 24 | |
| 0.0.5 | 1 / 24 | |
| 0.0.4 | 1 / 24 | |
| 0.0.3 | 0 / 24 | |
| 0.0.1 | 0 / 24 |
v0.0.15
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.14
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.13
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.12
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 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
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 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.4
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.3
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.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.