@archbase/advanced
Archbase React Advanced Components - Charts, Kanban, QueryBuilder
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 |
|---|---|---|---|---|
| phantom-deps | phantom-dep:dayjs | AI (phantom-deps): Declared dependency; used transitively through component exports. | ai | |
| phantom-deps | phantom-dep:i18next | AI (phantom-deps): Declared dependency; used transitively through component exports. | ai | |
| phantom-deps | phantom-dep:react-use | AI (phantom-deps): Declared dependency; used transitively through component exports. | ai | |
| phantom-deps | phantom-dep:react-modal | AI (phantom-deps): Declared dependency; used transitively through component exports. | ai | |
| phantom-deps | phantom-dep:react-select | AI (phantom-deps): Declared dependency; used transitively through component exports. | ai | |
| phantom-deps | phantom-dep:react-i18next | AI (phantom-deps): Declared dependency; used transitively through component exports. | ai |
Versions (showing 14 of 14)
| Version | Deps | Published |
|---|---|---|
| 4.0.28 | 16 / 7 | |
| 4.0.27 | 16 / 7 | |
| 4.0.26 | 16 / 7 | |
| 4.0.25 | 16 / 7 | |
| 4.0.24 | 16 / 7 | |
| 4.0.23 | 16 / 7 | |
| 4.0.22 | 16 / 7 | |
| 4.0.21 | 16 / 7 | |
| 4.0.20 | 16 / 7 | |
| 4.0.19 | 16 / 7 | |
| 4.0.18 | 16 / 7 | |
| 4.0.17 | 16 / 7 | |
| 4.0.3 | 16 / 7 | |
| 4.0.2 | 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. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.0.26
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.0.25
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.0.24
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.0.23
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.0.22
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.0.21
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.0.20
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.0.19
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.0.18
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.0.17
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.