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

Bump llama-index-core from 0.11.10 to 0.11.14 #44

Open
wants to merge 1 commit into
base: main
Choose a base branch
from

Conversation

dependabot[bot]
Copy link
Contributor

@dependabot dependabot bot commented on behalf of github Oct 1, 2024

Bumps llama-index-core from 0.11.10 to 0.11.14.

Changelog

Sourced from llama-index-core's changelog.

llama-index-core [0.11.14]

  • Enhance insert Method in BaseIndex to Support Customizable Transformations (#16206)
  • Ensure ChatMemoryBuffer's chat history never begins with a TOOL message (#16214)
  • safe prompt helper string formatting (#16219)
  • [Feature Request] Support max concurrent workflow_instance.run() executions (#16215)
  • Workflows + Human In The Loop Dedicated Support (#16220)

llama-index-graph-stores-neptune [0.2.2]

  • fix NoneType object error when passing in provided client (#16174)

llama-index-llms-ollama [0.3.3]

  • fix ollama chat missing keep_alive (#16182)

llama-index-llms-vertex [0.3.6]

  • Fix vertex init function (#16216)

llama-index-multi-modal-llms-mistral [0.1.0]

  • Add support for Mistral Multi modal LLM (#16191)

llama-index-readers-jira [0.3.0]

  • Add pagination support for Jira Reader (#16226)

llama-index-vector-stores-azurecosmosmongo [0.2.1]

  • Azure Cosmos DB Filtered Vector Search (#16175)

llama-index-vector-stores-azurecosmosnosql [1.1.0]

  • Azure Cosmos DB Filtered Vector Search (#16175)

llama-index-vector-stores-deeplake [0.2.1]

  • Add missing JWT dependency (#16236)

[2024-09-24]

llama-index-core [0.11.13]

  • add option for string node representation during retireval in property graphs (#16100)
  • improve markdown element node parser and structured prediction reliability (#16172)

llama-index-graph-stores-neptune [0.2.1]

  • Fixed issue where Neptune was adding additional labels (#16137)

... (truncated)

Commits

Dependabot compatibility score

Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting @dependabot rebase.


Dependabot commands and options

You can trigger Dependabot actions by commenting on this PR:

  • @dependabot rebase will rebase this PR
  • @dependabot recreate will recreate this PR, overwriting any edits that have been made to it
  • @dependabot merge will merge this PR after your CI passes on it
  • @dependabot squash and merge will squash and merge this PR after your CI passes on it
  • @dependabot cancel merge will cancel a previously requested merge and block automerging
  • @dependabot reopen will reopen this PR if it is closed
  • @dependabot close will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually
  • @dependabot show <dependency name> ignore conditions will show all of the ignore conditions of the specified dependency
  • @dependabot ignore this major version will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)
  • @dependabot ignore this minor version will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)
  • @dependabot ignore this dependency will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)

Bumps [llama-index-core](https://github.com/run-llama/llama_index) from 0.11.10 to 0.11.14.
- [Release notes](https://github.com/run-llama/llama_index/releases)
- [Changelog](https://github.com/run-llama/llama_index/blob/main/CHANGELOG.md)
- [Commits](run-llama/llama_index@v0.11.10...v0.11.14)

---
updated-dependencies:
- dependency-name: llama-index-core
  dependency-type: direct:production
  update-type: version-update:semver-patch
...

Signed-off-by: dependabot[bot] <support@github.com>
@dependabot dependabot bot added the dependencies Pull requests that update a dependency file label Oct 1, 2024
Copy link

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

Package New capabilities Transitives Size Publisher
pypi/llama-index-core@0.11.14 environment, eval, filesystem, network, shell, unsafe +82 23.3 MB jerryjliu

🚮 Removed packages: pypi/llama-index-core@0.11.10

View full report↗︎

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.

Alert Package NoteSourceCI
Filesystem access pypi/llama-index-core@0.11.14 🚫
Network access pypi/llama-index-core@0.11.14 🚫
Shell access pypi/llama-index-core@0.11.14 🚫
Uses eval pypi/llama-index-core@0.11.14 🚫
Environment variable access pypi/llama-index-core@0.11.14 🚫
Filesystem access pypi/llama-index-core@0.11.14 🚫
Network access pypi/llama-index-core@0.11.14 🚫
Shell access pypi/llama-index-core@0.11.14 🚫
Uses eval pypi/llama-index-core@0.11.14 🚫
Environment variable access pypi/llama-index-core@0.11.14 🚫

View full report↗︎

Next steps

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 is network access?

This module accesses the network.

Packages should remove all network access that is functionally unnecessary. Consumers should audit network access to ensure legitimate use.

What is shell access?

This module accesses the system shell. Accessing the system shell increases the risk of executing arbitrary code.

Packages should avoid accessing the shell which can reduce portability, and make it easier for malicious shell access to be introduced.

What is dynamic code execution?

Package uses dynamic code execution (e.g., eval()), which is a dangerous practice. This can prevent the code from running in certain environments and increases the risk that the code may contain exploits or malicious behavior.

Avoid packages that use dynamic code execution like eval(), since this could potentially execute any code.

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.

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 pypi/llama-index-core@0.11.14

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
dependencies Pull requests that update a dependency file
Projects
None yet
Development

Successfully merging this pull request may close these issues.

0 participants