[Snyk] Upgrade bancos-brasileiros from 5.1.76 to 5.1.81

[guibranco]

This PR was automatically created by Snyk using the credentials of a real user.

Snyk has created this PR to upgrade bancos-brasileiros from 5.1.76 to 5.1.81.

ℹ️ Keep your dependencies up-to-date. This makes it easier to fix existing vulnerabilities and to more quickly identify and fix newly disclosed vulnerabilities when they affect your project.

---

• The recommended version is 4 versions ahead of your current version.
• The recommended version was released 21 days ago, on 2024-02-26.

Release notes

Package name: bancos-brasileiros

• 5.1.81 - 2024-02-26
  

  Release of Bancos Brasileiros - v5.1.81

  • Added 1 bank
    • 584 - "CCC POUP E INV DOS ESTADOS DO PR, SP E RJ" - 80.230.774/0001-48
• 5.1.80 - 2024-02-26
• 5.1.79 - 2024-02-23
  

  Release of Bancos Brasileiros - v5.1.79

  • Updated 1 bank
    • 279 - COOP DE PRIMAVERA DO LESTE - 26.563.270/0001-02
      • LongName (STR): PRIMACREDI COOPERATIVA DE CR?DITO DE PRIMAVERA DO LESTE -> PRIMACREDI CREDISIS - COOPERATIVA DE CR?DITO DE PRIMAVERA DO LESTE
• 5.1.78 - 2024-02-22
  

  Release of Bancos Brasileiros - v5.1.78

  • Added 2 banks
    • 586 - Z1 IP LTDA. - 35.810.871/0001-55
    • 580 - CCCPOUPINV SUL E SUDESTE - CENTRAL SICREDI SUL/SUDESTE - 87.437.687/0001-05
• 5.1.76 - 2024-02-15
  

  Release of Bancos Brasileiros - v5.1.76

  • Added 2 banks
    • 586 - Z1 IP LTDA. - 35.810.871/0001-55
    • 580 - CCCPOUPINV SUL E SUDESTE - CENTRAL SICREDI SUL/SUDESTE - 87.437.687/0001-05

from bancos-brasileiros GitHub release notes

Commit messages

Package name: bancos-brasileiros

• 48fb547 Daily updates (bot)
• 38a3863 Daily updates (bot)
• 936475f Update README.pt-br.md
• 3a46255 Update README.md
• 2d4c61d build(deps): bump Renato66/auto-label from 2.3.1 to 2.4.0 (build(deps): bump Renato66/auto-label from 2.3.1 to 2.4.0 #364)
• 7e0c4da fix: upgrade bancos-brasileiros from 5.1.73 to 5.1.74 ([Snyk] Upgrade bancos-brasileiros from 5.1.73 to 5.1.74 #365)

Compare

---

Note: You are seeing this because you or someone else with access to this repository has authorized Snyk to open upgrade PRs.

For more information:

🧐 View latest project report

🛠 Adjust upgrade PR settings

🔕 Ignore this dependency or unsubscribe from future upgrade PRs

[socket-security]

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

Package	New capabilities	Transitives	Size	Publisher
npm/[email protected]	None	0	278 kB	guibranco

🚮 Removed packages: npm/[email protected]

View full report↗︎

[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
Missing license	npm/[email protected]	Location: Package overview	examples/emberjs/package-lock.json examples/emberjs/package.json
No tests	npm/[email protected]	Location: Package overview	examples/emberjs/package-lock.json examples/emberjs/package.json

View full report↗︎

Next steps

What is a missing license?

(Experimental) Package does not have a license and consumption legal status is unknown.

A new version of the package should be published that includes a valid SPDX license in a license file, package.json license field or mentioned in the README.

What does no tests mean?

Package does not have any tests. This is a strong signal of a poorly maintained or low quality package.

Add tests and publish a new version of the package. Consumers may look for an alternative package with better testing.

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]