@scm-manager/e2e-tests
End to end Tests for SCM-Manager
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 |
|---|---|---|---|---|
| provenance | publisher-changed | AI (provenance): cesmarvin is an established Cloudogu org publisher with prior approved packages; transition appears legitimate. | ai | |
| provenance | no-provenance | AI (provenance): Established SCM-Manager org package; lack of Sigstore attestation is a process gap, not a security indicator for this package. | ai | |
| publish-pattern | dormant-publish | AI (publish-pattern): SCM-Manager is an established OSS project; long gap likely reflects release cadence, not takeover. | ai | |
| phantom-deps | phantom-dep:fluent-ffmpeg | AI (phantom-deps): ffmpeg deps are used for Cypress video recording in e2e tests; config-file-only references are expected. | ai | |
| phantom-deps | phantom-dep:@ffmpeg-installer/ffmpeg | AI (phantom-deps): Same ffmpeg video-recording pattern; stable false positive for this e2e test package. | ai |
Versions (showing 18 of 18)
| Version | Deps | Published |
|---|---|---|
| 3.11.9 | 3 / 1 | |
| 3.11.8 | 3 / 1 | |
| 3.11.7 | 3 / 1 | |
| 3.11.6 | 3 / 1 | |
| 3.11.5 | 3 / 1 | |
| 3.11.4 | 3 / 1 | |
| 3.11.3 | 3 / 1 | |
| 3.11.2 | 3 / 1 | |
| 3.11.1 | 3 / 1 | |
| 3.11.0 | 3 / 1 | |
| 3.10.3 | 3 / 1 | |
| 3.10.2 | 3 / 1 | |
| 3.10.1 | 3 / 1 | |
| 3.10.0 | 3 / 1 | |
| 3.9.0 | 3 / 1 | |
| 3.7.8 | 3 / 1 | |
| 3.7.7 | 3 / 1 | |
| 3.7.6 | 3 / 1 |
v3.11.9
2 findingsThis version was published by a different npm account than previous versions on 2026-05-07. This could indicate a legitimate maintainer transition or an account compromise.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.11.8
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.11.7
2 findingsThis version was published by a different npm account than previous versions on 2026-03-20. This could indicate a legitimate maintainer transition or an account compromise.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.11.6
2 findingsThis version was published by a different npm account than previous versions on 2026-03-11. This could indicate a legitimate maintainer transition or an account compromise.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.11.5
2 findingsThis version was published by a different npm account than previous versions on 2026-02-25. This could indicate a legitimate maintainer transition or an account compromise.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.11.4
2 findingsThis version was published by a different npm account than previous versions on 2026-02-11. This could indicate a legitimate maintainer transition or an account compromise.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.11.3
2 findingsThis version was published by a different npm account than previous versions on 2026-02-10. This could indicate a legitimate maintainer transition or an account compromise.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.11.2
2 findingsThis version was published by a different npm account than previous versions on 2026-01-12. This could indicate a legitimate maintainer transition or an account compromise.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.11.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.11.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.10.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.10.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.10.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.10.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.9.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.7.8
2 findingsThis version was published by a different npm account than previous versions on 2026-02-25. This could indicate a legitimate maintainer transition or an account compromise.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.7.7
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.7.6
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.