@xwiki/cristal-authentication-github-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
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| phantom-deps | phantom-dep:@xwiki/cristal-api | AI (phantom-deps): Same-org monorepo dep used via DI container, not direct import; stable pattern for this package. | ai | |
| phantom-deps | phantom-dep:@xwiki/cristal-icons | AI (phantom-deps): Same-org monorepo dep; consistent with DI/plugin pattern across cristal packages. | ai | |
| phantom-deps | phantom-dep:@xwiki/platform-api | AI (phantom-deps): Same-org scoped dependency; likely re-exported by intermediate packages in the XWiki ecosystem. | ai | |
| phantom-deps | phantom-dep:@xwiki/platform-icons | AI (phantom-deps): Same-org scoped dependency; likely re-exported by intermediate packages in the XWiki ecosystem. | ai | |
| phantom-deps | phantom-dep:@xwiki/cristal-browser-api | AI (phantom-deps): Same-org scoped dependency; likely re-exported by intermediate packages in the XWiki ecosystem. | ai | |
| phantom-deps | phantom-dep:@xwiki/cristal-uiextension-default | AI (phantom-deps): Same-org scoped dependency; likely re-exported by intermediate packages in the XWiki ecosystem. | ai |
Versions (showing 7 of 7)
| Version | Deps | Published |
|---|---|---|
| 1.4.0 | 8 / 11 | |
| 1.3.0 | 8 / 11 | |
| 1.2.0 | 8 / 11 | |
| 1.1.0 | 8 / 11 | |
| 1.0.0 | 8 / 11 | |
| 0.25.0 | 8 / 11 | |
| 0.24.0 | 8 / 11 |
v1.4.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.3.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.2.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.1.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.25.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.24.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.