@archbase/security-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 — the axios compromise (March 2026) relied on exactly this gap.
Maintainers
Keywords
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| phantom-deps | phantom-dep:rxjs | AI (phantom-deps): Declared dep used transitively/in config; common pattern for this component library. | ai | |
| phantom-deps | phantom-dep:uuid | AI (phantom-deps): Declared dep used transitively/in config; common pattern for this component library. | ai | |
| phantom-deps | phantom-dep:lodash | AI (phantom-deps): Declared dep used transitively/in config; common pattern for this component library. | ai | |
| phantom-deps | phantom-dep:i18next | AI (phantom-deps): Declared dep used transitively/in config; common pattern for this component library. | ai | |
| phantom-deps | phantom-dep:crypto-js | AI (phantom-deps): Declared dep used transitively/in config; common pattern for this component library. | ai | |
| phantom-deps | phantom-dep:inversify | AI (phantom-deps): Declared dep used transitively/in config; common pattern for this component library. | ai | |
| phantom-deps | phantom-dep:react-dom | AI (phantom-deps): Also listed as peer dep; phantom-dep false positive for this package. | ai | |
| phantom-deps | phantom-dep:jwt-decode | AI (phantom-deps): Declared dep used transitively/in config; common pattern for this component library. | ai | |
| phantom-deps | phantom-dep:react-i18next | AI (phantom-deps): Declared dep used transitively/in config; common pattern for this component library. | ai | |
| phantom-deps | phantom-dep:inversify-react | AI (phantom-deps): Declared dep used transitively/in config; common pattern for this component library. | ai | |
| phantom-deps | phantom-dep:reflect-metadata | AI (phantom-deps): Known implicit runtime dep for inversify; not directly imported by design. | ai |
Versions (showing 23 of 23)
| Version | Deps | Published |
|---|---|---|
| 4.0.28 | 17 / 7 | |
| 4.0.27 | 17 / 7 | |
| 4.0.26 | 17 / 7 | |
| 4.0.25 | 17 / 7 | |
| 4.0.24 | 17 / 7 | |
| 4.0.23 | 17 / 7 | |
| 4.0.22 | 17 / 7 | |
| 4.0.21 | 17 / 7 | |
| 4.0.20 | 17 / 7 | |
| 4.0.19 | 17 / 7 | |
| 4.0.18 | 17 / 7 | |
| 4.0.17 | 17 / 7 | |
| 4.0.4 | 17 / 7 | |
| 4.0.3 | 17 / 7 | |
| 3.0.25 | 17 / 7 | |
| 3.0.23 | 17 / 7 | |
| 3.0.22 | 17 / 7 | |
| 3.0.21 | 17 / 7 | |
| 3.0.11 | 17 / 7 | |
| 3.0.9 | 17 / 7 | |
| 3.0.8 | 17 / 7 | |
| 3.0.5 | 17 / 7 | |
| 3.0.2 | 17 / 7 |
v4.0.28
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.0.27
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.0.26
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.0.25
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.0.24
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.0.23
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.0.22
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.0.21
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.0.20
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.0.19
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.0.18
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.0.17
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.0.4
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.0.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.0.25
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.0.23
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.0.22
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.0.21
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.0.11
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.0.9
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.0.8
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.0.5
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.0.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.