@xwiki/cristal-link-suggest-nextcloud
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:@xwiki/cristal-api | AI (dependencies): Sibling package in the same XWiki Cristal monorepo; co-released at matching version. | ai | |
| dependencies | unvetted-dep:@xwiki/cristal-model-api | AI (dependencies): Sibling package in the same XWiki Cristal monorepo; co-released at matching version. | ai | |
| dependencies | unvetted-dep:@xwiki/cristal-link-suggest-api | AI (dependencies): Sibling package in the same XWiki Cristal monorepo; co-released at matching version. | ai | |
| dependencies | unvetted-dep:@xwiki/cristal-authentication-api | AI (dependencies): Sibling package in the same XWiki Cristal monorepo; co-released at matching version. | ai | |
| dependencies | unvetted-dep:@xwiki/cristal-model-reference-api | AI (dependencies): Sibling package in the same XWiki Cristal monorepo; co-released at matching version. | ai | |
| dependencies | unvetted-dep:@xwiki/cristal-model-remote-url-api | AI (dependencies): Sibling package in the same XWiki Cristal monorepo; co-released at matching version. | ai |
Versions (showing 7 of 7)
| Version | Deps | Published |
|---|---|---|
| 1.4.0 | 8 / 6 | |
| 1.3.0 | 8 / 6 | |
| 1.2.0 | 8 / 6 | |
| 1.1.0 | 8 / 6 | |
| 1.0.0 | 8 / 6 | |
| 0.25.0 | 8 / 6 | |
| 0.24.0 | 7 / 6 |
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.