@xwiki/cristal-dsapi
Supply chain provenance
Status for the latest visible version.
Without SLSA provenance there is no cryptographic link between this tarball and the public source, so a manually published version cannot be tied back to a reviewed commit.
Maintainers
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| publish-pattern | new-deps-added | AI (publish-pattern): New deps are first-party sibling packages plus vue; normal for monorepo internal restructuring. | ai | |
| source-diff | large-new-source-files | AI (source-diff): Monorepo package growth, no exec/network behavior found. | ai | |
| source-diff | source-size-tripled | AI (source-diff): Consistent with legitimate feature expansion in a small early-stage package. | ai | |
| bogus-package | bogus-package | AI (bogus-package): Empty description/main is a monorepo API stub pattern, not spam. | ai |
Versions (showing 17 of 17)
| Version | Deps | Published |
|---|---|---|
| 0.24.0 | 4 / 4 | |
| 0.23.1 | 4 / 4 | |
| 0.23.0 | 4 / 4 | |
| 0.22.0 | 3 / 4 | |
| 0.21.1 | 3 / 4 | |
| 0.21.0 | 3 / 4 | |
| 0.20.0 | 3 / 4 | |
| 0.19.0 | 4 / 3 | |
| 0.18.0 | 4 / 3 | |
| 0.17.0 | 4 / 3 | |
| 0.16.0 | 4 / 3 | |
| 0.15.0 | 4 / 3 | |
| 0.14.0 | 3 / 3 | |
| 0.13.0 | 0 / 3 | |
| 0.12.0 | 0 / 0 | |
| 0.11.0 | 0 / 0 | |
| 0.10.0 | 0 / 0 |
v0.24.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.23.1
2 findingsPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
This version was published by a different npm account (pierre.jeanjean) than the most recent previously approved version (marius.dumitru.florea) on 2025-10-23, but pierre.jeanjean is listed as a maintainer on prior approved versions (matched on name). This looks like a manual publish by a known maintainer rather than a publisher change. Recorded as INFO for audit trail.
v0.23.0
2 findingsPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
This version was published by a different npm account (marius.dumitru.florea) than the most recent previously approved version (manuelleduc) on 2025-10-21, but marius.dumitru.florea is listed as a maintainer on prior approved versions (matched on name). This looks like a manual publish by a known maintainer rather than a publisher change. Recorded as INFO for audit trail.
v0.22.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.21.1
2 findingsPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
This version was published by a different npm account (manuelleduc) than the most recent previously approved version (pierre.jeanjean) on 2025-08-25, but manuelleduc is listed as a maintainer on prior approved versions (matched on name). This looks like a manual publish by a known maintainer rather than a publisher change. Recorded as INFO for audit trail.
v0.21.0
2 findingsPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
This version was published by a different npm account (pierre.jeanjean) than the most recent previously approved version (manuelleduc) on 2025-08-18, but pierre.jeanjean is listed as a maintainer on prior approved versions (matched on name). This looks like a manual publish by a known maintainer rather than a publisher change. Recorded as INFO for audit trail.
v0.20.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.19.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.18.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.17.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.16.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.15.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.14.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.13.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.12.0
2 findingsPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
This version was published by a different npm account (manuelleduc) than the most recent previously approved version (marius.dumitru.florea) on 2024-11-25, but manuelleduc is listed as a maintainer on prior approved versions (matched on name). This looks like a manual publish by a known maintainer rather than a publisher change. Recorded as INFO for audit trail.
v0.11.0
2 findingsPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
This version was published by a different npm account (marius.dumitru.florea) than the most recent previously approved version (pierre.jeanjean) on 2024-10-29, but marius.dumitru.florea is listed as a maintainer on prior approved versions (matched on name). This looks like a manual publish by a known maintainer rather than a publisher change. Recorded as INFO for audit trail.
v0.10.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.