@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 — 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): 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 26 of 26)
| 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 |
v0.2.8
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.2.6
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.2.5
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.2.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.2.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.2.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.2.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.2.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.5
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.26
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.25
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.24
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.23
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.22
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.21
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.20
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.19
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.18
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.17
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.16
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.