ci(github): move connect webextension example tests to GitHub Actions

[karliatto]

Description

Migrate from GitLab to GitHub Actions example webextension test.

Move the tests for example webextension to popup tests since they are using the same infrastructure and it was confusing to have those in connect-webextension package because that package now is used for different reason.

Related Issue

Resolve #7916

[socket-security]

🚨 Potential security issues detected. Learn more about Socket for GitHub ↗︎

To accept the risk, merge this PR and you will not be notified again.

Alert	Package	Note	Source
New author	npm/[email protected]	New Author: michaelficarra Previous Author: nzakas	orphan: npm/[email protected]
New author	npm/[email protected]	New Author: qix Previous Author: sindresorhus	orphan: npm/[email protected]
Trivial Package	npm/[email protected]	Location: Package overview	orphan: npm/[email protected]
Environment variable access	npm/[email protected]	Env Vars: NO_DEPRECATION Location: Package overview	orphan: npm/[email protected]
Environment variable access	npm/[email protected]	Env Vars: TRACE_DEPRECATION Location: Package overview	orphan: npm/[email protected]
Uses eval	npm/[email protected]	Eval Type: eval Location: Package overview	orphan: npm/[email protected]
Filesystem access	npm/[email protected]	Module: fs Location: Package overview	orphan: npm/[email protected]
Environment variable access	npm/[email protected]	Env Vars: NODE_ENV Location: Package overview	orphan: npm/[email protected]
Floating dependency	npm/@types/[email protected]	Location: Package overview	orphan: npm/@types/[email protected]
New author	npm/[email protected]	New Author: ljharb Previous Author: radubrehar	orphan: npm/[email protected]
Floating dependency	npm/@types/[email protected]	Location: Package overview	orphan: npm/@types/[email protected]

View full report↗︎

Next steps

What is new author?

A new npm collaborator published a version of the package for the first time. New collaborators are usually benign additions to a project, but do indicate a change to the security surface area of a package.

Scrutinize new collaborator additions to packages because they now have the ability to publish code into your dependency tree. Packages should avoid frequent or unnecessary additions or changes to publishing rights.

What are trivial packages?

Packages less than 10 lines of code are easily copied into your own project and may not warrant the additional supply chain risk of an external dependency.

Removing this package as a dependency and implementing its logic will reduce supply chain risk.

What is environment variable access?

Package accesses environment variables, which may be a sign of credential stuffing or data theft.

Packages should be clear about which environment variables they access, and care should be taken to ensure they only access environment variables they claim to.

What is eval?

Package uses eval() which is a dangerous function. This prevents the code from running in certain environments and increases the risk that the code may contain exploits or malicious behavior.

Avoid packages that use eval, since this could potentially execute any code.

What is filesystem access?

Accesses the file system, and could potentially read sensitive data.

If a package must read the file system, clarify what it will read and ensure it reads only what it claims to. If appropriate, packages can leave file system access to consumers and operate on data passed to it instead.

What are floating dependencies?

Package has a dependency with a floating version range. This can cause issues if the dependency publishes a new major version.

Packages should specify properly semver ranges to avoid version conflicts.

Take a deeper look at the dependency

Take a moment to review the security alert above. Review the linked package source code to understand the potential risk. Ensure the package is not malicious before proceeding. If you're unsure how to proceed, reach out to your security team or ask the Socket team for help at support [AT] socket [DOT] dev.

Remove the package

If you happen to install a dependency that Socket reports as Known Malware you should immediately remove it and select a different dependency. For other alert types, you may may wish to investigate alternative packages or consider if there are other ways to mitigate the specific risk posed by the dependency.

Mark a package as acceptable risk

To ignore an alert, reply with a comment starting with @SocketSecurity ignore followed by a space separated list of ecosystem/package-name@version specifiers. e.g. @SocketSecurity ignore npm/[email protected] or ignore all packages with @SocketSecurity ignore-all

• @SocketSecurity ignore npm/[email protected]
• @SocketSecurity ignore npm/[email protected]
• @SocketSecurity ignore npm/[email protected]
• @SocketSecurity ignore npm/[email protected]
• @SocketSecurity ignore npm/[email protected]
• @SocketSecurity ignore npm/@types/[email protected]
• @SocketSecurity ignore npm/[email protected]
• @SocketSecurity ignore npm/@types/[email protected]

[karliatto]

@SocketSecurity ignore

[martykan]

It's not called with parameters like before (--trezor-connect-src "${URL}" --npm-src "${URL}/trezor-connect.js") is this intended?

[karliatto]

Yes, that was missed, I just added it. Thanks!

[vdovhanych]

Otherwise i think its fine

[vdovhanych]

we should use directly building just the necessary lib, not all of them, right?

[mroz22]

yes, that shouldn't be needed globally here.

[karliatto]

You are right, that yarn build:libs was totally unnecessary, done 1c66aef

[mroz22]

so url here is just regular branch of a PR right? (or maybe develop branch)

also didn't we use it somewhere in combination production URLs?

[karliatto]

Yes, URL here is that, the branch of the PR where this test is running. On schedule it is develop.

[karliatto]

so what do you think guys, it is ok alreay? @vdovhanych @martykan @mroz22

[karliatto]

@SocketSecurity ignore