@midscene/computer-mcp
Midscene MCP Server for Computer desktop automation
Supply chain provenance
Status for the latest visible version.
Maintainers
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| provenance | publisher-changed | AI (provenance): Transition to GitHub Actions publisher is confirmed legitimate by SLSA provenance attestation on this and subsequent releases. | ai | |
| phantom-deps | phantom-dep:utf-8-validate | AI (phantom-deps): utf-8-validate is a well-known optional ws performance dep; phantom flag is expected for bundled packages that list it as an external. | ai | |
| phantom-deps | phantom-dep:sharp | AI (phantom-deps): sharp is a known native image processing library; phantom flag for runtime/binary implicit dep is standard for bundled packages. | ai | |
| phantom-deps | phantom-dep:bufferutil | AI (phantom-deps): bufferutil is a well-known optional ws performance dep; phantom flag is expected for bundled packages that list it as an external. | ai | |
| phantom-deps | phantom-dep:@silvia-odwyer/photon | AI (phantom-deps): WASM image processing library; config-only reference is consistent with bundler externals pattern for this desktop automation package. | ai | |
| phantom-deps | phantom-dep:@silvia-odwyer/photon-node | AI (phantom-deps): WASM image processing library (Node variant); config-only reference is consistent with bundler externals pattern. | ai | |
| phantom-deps | phantom-dep:@computer-use/libnut | AI (phantom-deps): libnut is a native desktop automation binding; conditional/config-only reference is expected for platform-specific native modules. | ai |
Versions (showing 51 of 53)
| Version | Deps | Published |
|---|---|---|
| 1.9.1 | 6 / 12 | |
| 1.9.0 | 6 / 12 | |
| 1.8.11 | 6 / 12 | |
| 1.8.9 | 6 / 12 | |
| 1.8.8 | 6 / 12 | |
| 1.8.7 | 6 / 12 | |
| 1.8.6 | 6 / 12 | |
| 1.8.5 | 6 / 12 | |
| 1.8.4 | 6 / 12 | |
| 1.8.3 | 6 / 12 | |
| 1.8.2 | 6 / 12 | |
| 1.8.1 | 6 / 12 | |
| 1.8.0 | 6 / 12 | |
| 1.7.10 | 6 / 12 | |
| 1.7.9 | 6 / 12 | |
| 1.7.7 | 6 / 12 | |
| 1.7.6 | 6 / 12 | |
| 1.7.5 | 6 / 12 | |
| 1.7.4 | 6 / 12 | |
| 1.7.3 | 6 / 12 | |
| 1.7.2 | 6 / 12 | |
| 1.7.1 | 6 / 12 | |
| 1.7.0 | 6 / 12 | |
| 1.6.4 | 6 / 12 | |
| 1.6.3 | 6 / 12 | |
| 1.6.2 | 6 / 12 | |
| 1.6.1 | 6 / 12 | |
| 1.6.0 | 6 / 12 | |
| 1.5.8 | 6 / 12 | |
| 1.5.7 | 6 / 12 | |
| 1.5.6 | 6 / 12 | |
| 1.5.5 | 6 / 12 | |
| 1.5.4 | 6 / 12 | |
| 1.5.3 | 6 / 12 | |
| 1.5.2 | 6 / 12 | |
| 1.5.1 | 6 / 12 | |
| 1.5.0 | 6 / 12 | |
| 1.4.9 | 6 / 12 | |
| 1.4.8 | 6 / 12 | |
| 1.4.7 | 6 / 12 | |
| 1.4.6 | 6 / 12 | |
| 1.4.5 | 6 / 12 | |
| 1.4.4 | 6 / 12 | |
| 1.4.3 | 6 / 12 | |
| 1.4.2 | 6 / 12 | |
| 1.4.1 | 6 / 12 | |
| 1.4.0 | 6 / 12 | |
| 1.3.11 | 6 / 12 | |
| 1.3.10 | 6 / 12 | |
| 1.3.9 | 5 / 12 | |
| 1.3.8 | 5 / 12 |
v1.9.1
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v1.9.0
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v1.8.11
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v1.8.9
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v1.8.8
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v1.8.7
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v1.8.6
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v1.8.5
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v1.8.4
2 findingsThis version was published by a different npm account than previous versions on 2026-05-21. This could indicate a legitimate maintainer transition or an account compromise.
Published via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v1.8.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.8.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.8.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.8.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.7.10
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.7.9
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.7.7
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.7.5
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.7.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.7.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.7.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.7.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.7.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.6.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.6.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.6.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.6.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.6.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.5.8
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.5.7
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.5.6
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.5.5
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.5.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.5.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.5.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.5.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.5.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.4.9
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.4.8
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.4.7
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.4.6
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.4.5
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.4.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.4.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.4.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.4.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.4.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.3.11
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.3.10
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.3.9
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.3.8
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.