Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Development #29

Merged
merged 8 commits into from
Oct 6, 2023
Merged

Development #29

merged 8 commits into from
Oct 6, 2023

Conversation

corrideat
Copy link
Member

No description provided.

Update module import paths
Remove .tsbuildinfo files from published packages
Browser: Use createElementNS insteado createElement
Browser: Check for custom element support
@socket-security
Copy link

socket-security bot commented Oct 6, 2023

New and removed dependencies detected. Learn more about Socket for GitHub ↗︎

Packages Version New capabilities Transitives Size Publisher
audit 0.0.6 None +0 21.7 kB
react-scripts 5.0.1 network, filesystem, shell, environment +952 178 MB iansu
@testing-library/react 14.0.0 eval, environment +67 18 MB testing-library-bot
fix 0.0.6 network, filesystem +3 315 kB falcon
react 18.2.0 environment +1 322 kB gnoff
react-dom 18.2.0 environment +3 4.92 MB gnoff
@testing-library/user-event 14.5.1 eval +58 6.62 MB testing-library-bot
web-vitals 3.5.0 None +0 383 kB tunetheweb

🚮 Removed packages: [email protected]

@socket-security
Copy link

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

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

Issue Package Version Note Source
Bin script confusion jest 27.5.1
Bin script confusion jest-cli 27.5.1
CVE nth-check 1.0.2
Mild CVE underscore.string 1.1.4
Mild CVE postcss 7.0.39

Next steps

What is bin script confusion?

This package has multiple bin scripts with the same name. This can cause non-deterministic behavior when installing or could be a sign of a supply chain attack

Consider removing one of the conflicting packages. Packages should only export bin scripts with their name

What is a CVE?

Contains a high severity Common Vulnerability and Exposure (CVE).

Remove or replace dependencies that include known high severity CVEs. Consumers can use dependency overrides or npm audit fix --force to remove vulnerable dependencies.

What is a mild CVE?

Contains a low severity Common Vulnerability and Exposure (CVE).

Remove or replace dependencies that include known low severity CVEs. Consumers can use dependency overrides or npm audit fix --force to remove vulnerable dependencies.

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 package-name@version specifiers. e.g. @SocketSecurity ignore [email protected] bar@* or ignore all packages with @SocketSecurity ignore-all

@sonarqubecloud
Copy link

sonarqubecloud bot commented Oct 6, 2023

Kudos, SonarCloud Quality Gate passed!    Quality Gate passed

Bug A 0 Bugs
Vulnerability A 0 Vulnerabilities
Security Hotspot A 0 Security Hotspots
Code Smell A 1 Code Smell

No Coverage information No Coverage information
0.0% 0.0% Duplication

@corrideat corrideat merged commit a5b787c into master Oct 6, 2023
6 of 7 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

1 participant