@archbase/security
Security and authentication components for Archbase React
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:lodash | AI (phantom-deps): lodash is a runtime dep used via config/build tooling in this monorepo package; stable false positive. | ai | |
| phantom-deps | phantom-dep:i18next | AI (phantom-deps): i18next referenced in config files; stable false positive for this package. | ai | |
| phantom-deps | phantom-dep:react-dom | AI (phantom-deps): react-dom is a peer/runtime dep; phantom-dep heuristic misfires here. | ai | |
| phantom-deps | phantom-dep:react-i18next | AI (phantom-deps): react-i18next referenced in config; stable false positive. | ai | |
| phantom-deps | phantom-dep:@archbase/layout | AI (phantom-deps): Same-org sibling package; phantom-dep heuristic misfires for monorepo splits. | ai |
Versions (showing 28 of 28)
| Version | Deps | Published |
|---|---|---|
| 4.0.28 | 16 / 8 | |
| 4.0.27 | 16 / 8 | |
| 4.0.26 | 16 / 8 | |
| 4.0.25 | 16 / 8 | |
| 4.0.24 | 16 / 8 | |
| 4.0.23 | 16 / 8 | |
| 4.0.22 | 16 / 8 | |
| 4.0.21 | 16 / 8 | |
| 4.0.20 | 16 / 8 | |
| 4.0.19 | 16 / 8 | |
| 4.0.18 | 16 / 8 | |
| 4.0.17 | 16 / 8 | |
| 4.0.4 | 16 / 8 | |
| 4.0.3 | 16 / 8 | |
| 4.0.2 | 16 / 8 | |
| 4.0.1 | 16 / 8 | |
| 3.0.22 | 16 / 8 | |
| 3.0.18 | 16 / 8 | |
| 3.0.16 | 16 / 8 | |
| 3.0.13 | 16 / 8 | |
| 3.0.12 | 16 / 8 | |
| 3.0.10 | 16 / 8 | |
| 3.0.8 | 16 / 8 | |
| 3.0.7 | 16 / 8 | |
| 3.0.5 | 16 / 8 | |
| 3.0.4 | 16 / 8 | |
| 3.0.2 | 16 / 8 | |
| 3.0.0 | 16 / 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.
v4.0.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.0.1
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.18
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.0.16
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.0.13
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.0.12
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.0.10
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.7
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.4
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.
v3.0.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.