@deviceinsight/ng-ui-components
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 |
|---|---|---|---|---|
| dependencies | unvetted-dep:react-select-async-paginate | AI (dependencies): react-select-async-paginate is a well-known, benign pagination wrapper; stable false positive for this package. | ai | |
| provenance | no-provenance | AI (provenance): Org-published component library; provenance omission is consistent across versions and poses no direct security risk. | ai |
Versions (showing 5 of 5)
| Version | Deps | Published |
|---|---|---|
| 7.9.0 | 22 / 34 | |
| 7.5.0 | 22 / 34 | |
| 7.4.0 | 22 / 34 | |
| 7.2.0 | 22 / 34 | |
| 7.0.0 | 22 / 34 |
v7.9.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v7.5.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v7.4.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v7.2.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.
v7.0.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.