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

v1.10.0 #292

Merged
merged 6 commits into from
Aug 24, 2024
Merged

v1.10.0 #292

merged 6 commits into from
Aug 24, 2024

Conversation

n4ze3m
Copy link
Owner

@n4ze3m n4ze3m commented Aug 21, 2024

  • Telegram bot markdown support
  • Added Data source search
  • [BETA] Internet Search

Copy link

vercel bot commented Aug 21, 2024

The latest updates on your projects. Learn more about Vercel for Git ↗︎

Name Status Preview Comments Updated (UTC)
dialoqbase-ui ✅ Ready (Inspect) Visit Preview 💬 Add feedback Aug 24, 2024 8:47am

Copy link

socket-security bot commented Aug 21, 2024

🚨 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 NoteSourceCI
Install scripts npm/esbuild@0.18.20 🚫
Install scripts npm/@fortawesome/fontawesome-free@6.5.1
  • Install script: postinstall
  • Source: node attribution.js
🚫
Install scripts npm/@swc/core@1.4.8
  • Install script: postinstall
  • Source: node postinstall.js
🚫
Install scripts npm/core-js-pure@3.36.1
  • Install script: postinstall
  • Source: node -e "try{require('./postinstall')}catch(e){}"
🚫

View full report↗︎

Next steps

What is an install script?

Install scripts are run when the package is installed. The majority of malware in npm is hidden in install scripts.

Packages should not be running non-essential scripts during install and there are often solutions to problems people solve with install scripts that can be run at publish time instead.

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/foo@1.0.0 or ignore all packages with @SocketSecurity ignore-all

  • @SocketSecurity ignore npm/esbuild@0.18.20
  • @SocketSecurity ignore npm/@fortawesome/fontawesome-free@6.5.1
  • @SocketSecurity ignore npm/@swc/core@1.4.8
  • @SocketSecurity ignore npm/core-js-pure@3.36.1

Copy link

gitguardian bot commented Aug 22, 2024

⚠️ GitGuardian has uncovered 1 secret following the scan of your pull request.

Please consider investigating the findings and remediating the incidents. Failure to do so may lead to compromising the associated services or software components.

🔎 Detected hardcoded secret in your pull request
GitGuardian id GitGuardian status Secret Commit Filename
13507327 Triggered Generic High Entropy Secret 7b9793e docker/searxng/settings.yml View secret
🛠 Guidelines to remediate hardcoded secrets
  1. Understand the implications of revoking this secret by investigating where it is used in your code.
  2. Replace and store your secret safely. Learn here the best practices.
  3. Revoke and rotate this secret.
  4. If possible, rewrite git history. Rewriting git history is not a trivial act. You might completely break other contributing developers' workflow and you risk accidentally deleting legitimate data.

To avoid such incidents in the future consider


🦉 GitGuardian detects secrets in your source code to help developers and security teams secure the modern development process. You are seeing this because you or someone else with access to this repository has authorized GitGuardian to scan your pull request.

Copy link

Report too large to display inline

View full report↗︎

@n4ze3m n4ze3m marked this pull request as ready for review August 24, 2024 08:47
@n4ze3m n4ze3m merged commit dd79a51 into main Aug 24, 2024
5 of 6 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