Software function library management method and system, electronic equipment and storage medium

Abstract

The invention discloses a software function library management method and system, electronic equipment and a storage medium. The method comprises the steps that under the condition that an instruction for calling a target software function library is received, judgment is carried out based on permission information in the instruction, and a judgment result is obtained; when the judgment result is that the permission information conforms to the preset calling permission, obtaining a target packaging interface corresponding to the target software function library; based on an original interface corresponding to the target encapsulation interface, calling a target software function library, the original interface being an interface of the target software function library; based on the library information of the target software function library, the target software function library is monitored, a monitoring result of the target software function library is obtained, and the monitoring result is used for representing whether the target software function library meets a preset safety condition or not. The technical problem of low management efficiency of the software function library in related technologies is solved.

Description

Technical Field

[0001] This application relates to the field of software development, and more specifically, to a method, system, electronic device, and storage medium for managing a software function library. Background Technology

[0002] In modern software development, the introduction of third-party libraries has become an important means to improve development efficiency, reduce costs, and enhance application functionality. However, the widespread use of third-party libraries has also brought significant challenges, especially in terms of security and compliance. Under traditional management models, each project team independently selects and maintains software function libraries. This not only increases the complexity of the technology stack but also leads to frequent security vulnerabilities. When facing library security issues, project teams often need to independently complete tasks such as patching and version upgrades. This decentralized management approach results in a large amount of repetitive work, leading to low management efficiency of software function libraries in related technologies.

[0003] There is currently no effective solution to the above problems. Summary of the Invention

[0004] This application provides a method, system, electronic device, and storage medium for managing software function libraries, in order to at least solve the technical problem of low management efficiency of software function libraries in related technologies.

[0005] According to one aspect of the embodiments of this application, a method for managing a software function library is provided, applied to a library management module, comprising: upon receiving an instruction to call a target software function library, judging based on permission information in the instruction to obtain a judgment result, wherein the judgment result is used to indicate whether the client's permission information meets preset calling permissions; if the judgment result indicates that the permission information meets preset calling permissions, obtaining a target encapsulation interface corresponding to the target software function library, wherein the target encapsulation interface is used to characterize the interface used by the client to call the target software function library, the target software function library is determined from multiple software function libraries based on software function library identification information in the instruction, the software function library identification information is used to represent a unique identifier for identifying the target software function library; calling the target software function library based on the original interface corresponding to the target encapsulation interface, wherein the original interface is the interface of the target software function library; and monitoring the target software function library based on the library information of the target software function library to obtain a monitoring result of the target software function library, wherein the monitoring result is used to indicate whether the target software function library meets preset security conditions.

[0006] Furthermore, the method also includes: for any one of the multiple software function libraries, encapsulating the software function library to obtain the encapsulation interface corresponding to the software function library, wherein the encapsulation interface corresponding to the software function library corresponds to the original interface corresponding to the software function library.

[0007] Furthermore, the method also includes: if the monitoring result indicates that the target software function library does not meet the preset security conditions, updating the target software function library to obtain the update result of the target software function library, wherein the update result is used to indicate whether the target software function library has been successfully updated; if the update result indicates that the target software function library has been successfully updated, updating the target encapsulation interface synchronously.

[0008] Furthermore, the method also includes: if the monitoring result indicates that the target software function library does not meet the preset security conditions, identifying at least one software that uses the target software function library; sending a prompt message to the client corresponding to the at least one software, wherein the prompt message is used to prompt adjustments to the at least one software; and upgrading the library management module upon receiving the adjustment instruction sent by the client.

[0009] Furthermore, the method also includes: acquiring historical call records and library information of the target software function library based on a preset interval; generating monitoring results of the target software function library based on the historical call records and library information; and outputting the monitoring results.

[0010] According to another aspect of the embodiments of this application, a software function library management system is also provided, including: a library management module, used to provide multiple encapsulation interfaces corresponding to multiple software function libraries, and to obtain library information of a target software function library, wherein the multiple encapsulation interfaces correspond one-to-one with the original interfaces of the multiple software function libraries; and a monitoring platform, used to receive the library information and determine the monitoring results of the target software function library based on the library information.

[0011] Furthermore, the library management module includes a library encapsulation module and a library monitoring module. The library encapsulation module is used to encapsulate multiple software function libraries to obtain multiple encapsulation interfaces corresponding to the multiple software function libraries. The library monitoring module is used to collect and transmit library information corresponding to the target software function library.

[0012] According to another aspect of the embodiments of this application, a software function library management device is also provided, comprising: a judgment module, configured to, upon receiving an instruction to call a target software function library, judge based on permission information in the instruction to obtain a judgment result, wherein the judgment result is used to indicate whether the client's permission information meets preset calling permissions; an acquisition module, configured to, if the judgment result indicates that the permission information meets preset calling permissions, acquire a target encapsulation interface corresponding to the target software function library, wherein the target encapsulation interface is used to characterize the interface used by the client to call the target software function library, the target software function library is determined from multiple software function libraries based on software function library identification information in the instruction, the software function library identification information is used to represent a unique identifier for identifying the target software function library; a calling module, configured to call the target software function library based on the original interface corresponding to the target encapsulation interface, wherein the original interface is the interface of the target software function library; and a monitoring module, configured to, based on the library information of the target software function library, monitor the target software function library to obtain a monitoring result of the target software function library, wherein the monitoring result is used to indicate whether the target software function library meets preset security conditions.

[0013] According to another aspect of the embodiments of this application, an electronic device is also provided, including: a memory storing an executable program; and a processor for running the program, wherein the program executes the methods in various embodiments of this application when it runs.

[0014] According to another aspect of the embodiments of this application, a computer-readable storage medium is also provided, the computer-readable storage medium including a stored executable program, wherein, when the executable program is running, it controls the device where the computer-readable storage medium is located to perform the methods of various embodiments of this application.

[0015] According to another aspect of the embodiments of this application, a computer program product is also provided, including a computer program that, when executed by a processor, implements the methods of various embodiments of this application.

[0016] According to another aspect of the embodiments of this application, a computer program product is also provided, including a non-volatile computer-readable storage medium storing a computer program that, when executed by a processor, implements the methods in various embodiments of this application.

[0017] According to another aspect of the embodiments of this application, a computer program is also provided, which, when executed by a processor, implements the methods of the various embodiments of this application.

[0018] This application provides a method for managing software function libraries, applied to a library management module. First, upon receiving an instruction to call a target software function library, the module performs a judgment based on the permission information in the instruction, obtaining a judgment result. If the judgment result indicates that the permission information meets preset calling permissions, the module obtains the target encapsulation interface corresponding to the target software function library. Next, based on the original interface corresponding to the target encapsulation interface, the module calls the target software function library, where the original interface is the interface of the target software function library. Finally, based on the library information of the target software function library, the module monitors the target software function library, obtaining the monitoring result. In this management method, when the library management module receives a client's instruction to call a specific target software function library, it first obtains a specially designed target encapsulation interface corresponding to that target library. This encapsulation interface, while maintaining the integrity of the original library functions, provides a unified access standard and additional security control measures, enabling clients to call different libraries through a consistent interface, greatly simplifying the software development process. Next, the library management module indirectly calls the target software function library based on the target encapsulation interface through its corresponding original interface. Finally, the library management module monitors the target software function library based on its library information and generates monitoring results. These results clearly indicate whether the target software function library meets preset security conditions, thus achieving the technical objective of efficient management and monitoring of the software function library. This application, by constructing a collaborative working mechanism between the library encapsulation module and the monitoring mechanism, achieves efficient, standardized, and secure management of the software function library, greatly improving management efficiency and thus solving the technical problem of low management efficiency of software function libraries in related technologies. Attached Figure Description

[0019] The accompanying drawings, which are included to provide a further understanding of this application and form part of this application, illustrate exemplary embodiments of this application and are used to explain this application, but do not constitute an undue limitation of this application. In the drawings:

[0020] Figure 1 This is a flowchart of a software function library management method according to an embodiment of this application;

[0021] Figure 2 This is a schematic diagram of software function library management according to an embodiment of this application;

[0022] Figure 3 This is a schematic diagram of a software function library management device according to an embodiment of this application. Detailed Implementation

[0023] To enable those skilled in the art to better understand the present application, the technical solutions in the embodiments of the present application will be clearly and completely described below with reference to the accompanying drawings. Obviously, the described embodiments are only some embodiments of the present application, and not all embodiments. Based on the embodiments in the present application, all other embodiments obtained by those of ordinary skill in the art without creative effort should fall within the scope of protection of the present application.

[0024] It should be noted that the terms "first," "second," etc., in the specification, claims, and accompanying drawings of this application are used to distinguish similar objects and are not necessarily used to describe a specific order or sequence. It should be understood that such data can be interchanged where appropriate so that the embodiments of this application described herein can be implemented in orders other than those illustrated or described herein. Furthermore, the terms "comprising" and "having," and any variations thereof, are intended to cover non-exclusive inclusion; for example, a process, method, system, product, or apparatus that comprises a series of steps or units is not necessarily limited to those steps or units explicitly listed, but may include other steps or units not explicitly listed or inherent to such processes, methods, products, or apparatus.

[0025] The collection, storage, use, processing, transmission, provision, and disclosure of financial data or user data involved in the technical solution of this application all comply with the provisions of relevant laws and regulations and do not violate public order and good morals.

[0026] It should be noted that in the embodiments of this application, certain software, components, models and other existing solutions in the industry will be mentioned. These should be regarded as exemplary and are only intended to illustrate the feasibility of implementing the technical solution of this application. However, it does not mean that the applicant has used or necessarily used the solution.

[0027] According to an embodiment of this application, a method for managing a software function library is provided. It should be noted that the steps shown in the flowchart in the accompanying drawings can be executed in a computer system such as a set of computer-executable instructions. Furthermore, although a logical order is shown in the flowchart, in some cases, the steps shown or described may be executed in a different order than that shown here.

[0028] Figure 1 This is a flowchart of a software function library management method according to an embodiment of this application, applied to a library management module, such as... Figure 1 As shown, the method includes the following steps:

[0029] Step S102: Upon receiving an instruction to call the target software function library, a judgment is made based on the permission information in the instruction to obtain a judgment result, wherein the judgment result is used to indicate whether the client's permission information meets the preset calling permissions.

[0030] The aforementioned target software function library can refer to a software library or component selected for use during the software development process to achieve a specific function or solve a problem. Target software function libraries can provide a predefined set of functions, simplifying the development process and improving software development efficiency and functionality.

[0031] The aforementioned instructions can refer to requests issued by the client, instructing the invocation of specific software function libraries to perform a certain function or task. Instruction types may include, but are not limited to, invocation instructions, Application Programming Interface (API) requests, and message passing instructions; the specific instructions must be determined based on actual needs. Instructions can serve as communication signals between the client and the library management module, triggering subsequent operations by the library management module, such as obtaining encapsulated interfaces or actually invoking functions.

[0032] The aforementioned permission information refers to a set of data in the invocation command that describes the identity of the client (caller) and its permission level for accessing or operating specific software function libraries. Permission information may include, but is not limited to, client ID, permission level code, validity period, and specific access restrictions; the specific permission information needs to be determined based on the client type. Permission information serves as the basis for invocation authentication and authorization, ensuring that only authenticated clients can access the software function libraries.

[0033] The aforementioned judgment result refers to the conclusion reached after the permission information has been verified by the system, indicating whether the client possesses the preset calling permissions, thereby determining whether to allow it to call the target software function library. The judgment result may include, but is not limited to, permission information conforming to preset calling permissions or permission information not conforming to preset calling permissions; the specific judgment result needs to be determined based on the actual judgment situation. The library management module decides whether to continue processing the client's calling command based on the judgment result, and how to process it. The result of each judgment is recorded as part of the system log for subsequent security and compliance analysis.

[0034] The aforementioned preset access permissions refer to the permission rules or thresholds set in advance by the enterprise or system administrator, allowing clients to access software function libraries. These permissions can be defined based on roles, departments, project requirements, or specific attributes of the software function libraries (such as sensitivity or security rating). Clearly defining and enforcing preset access permissions helps standardize and automate access management, simplifies processes, and enhances system controllability and transparency.

[0035] Step S104: If the judgment result is that the permission information meets the preset calling permissions, obtain the target encapsulation interface corresponding to the target software function library. The target encapsulation interface is used to characterize the interface used by the client to call the target software function library. The target software function library is determined from multiple software function libraries based on the software function library identification information in the instruction. The software function library identification information is used to represent the unique identifier of the target software function library.

[0036] The aforementioned target encapsulation interface refers to the interface designed within the library management module for clients to call target software function libraries. It acts as an intermediate layer, converting and adapting client requests to the actual interface of the software function library. Depending on the software function library, the type and functionality of the target encapsulation interface will vary, but its core purpose is to provide a secure and unified entry point. Through the target encapsulation interface, clients can indirectly and securely access and use the target software function library without directly exposing the details of the underlying library, thus enhancing security and providing a unified calling method.

[0037] The aforementioned client can refer to a software application or module that needs to call a software function library to achieve a specific function. Clients can include, but are not limited to, software developed by internal project teams, server-side applications, and mobile applications; the specific client needs to be determined based on the actual application scenario. The client can call the software function library through the library management module to fulfill the functional requirements in software development. It does not need to understand the details of the underlying library; it can complete the call through the target encapsulated interface.

[0038] In one optional embodiment, the method for obtaining the target encapsulation interface corresponding to the target software function library may include, but is not limited to, the following methods:

[0039] The first method is static mapping lookup: The library management module pre-establishes and maintains a mapping table between software function libraries and encapsulated interfaces. When a call command arrives, the module quickly retrieves the corresponding target encapsulated interface from the mapping table based on the library information specified in the command, such as name and version.

[0040] The second method involves dynamic proxy generation: the library management module can use dynamic proxy technology to generate proxy objects for the target encapsulated interface in real time based on the calling instructions. In this method, the acquisition of the encapsulated interface is completed dynamically at runtime, improving the module's flexibility and responsiveness.

[0041] The third method involves configuration file retrieval: the library management module can rely on configuration files to store information about function libraries and their encapsulated interfaces. Upon receiving a call instruction, the module reads the configuration file, parses the encapsulated interface configurations related to the target software function library, and thus obtains the specific interface required for the call.

[0042] The above methods of obtaining the data are for illustrative purposes only. The specific methods should be determined based on the actual system design requirements, and are not limited here.

[0043] In one optional embodiment, if the determination result indicates that the permission information conforms to the preset calling permissions, the library management module internally searches for and locates the target encapsulation interface that matches the target software function library. The design of the target encapsulation interface not only follows the client's calling habits but also seamlessly connects to the original interface of the function library. By using the target encapsulation interface, the client can securely and efficiently access and utilize the capabilities of the target software function library without needing to understand the specific implementation details of the function library. Simultaneously, it facilitates the library management module in monitoring and controlling calling behavior, ensuring the security and compliance of the software ecosystem.

[0044] Step S106: Based on the original interface corresponding to the target encapsulation interface, call the target software function library, where the original interface is the interface of the target software function library.

[0045] The aforementioned raw interfaces can refer to interfaces directly provided to developers by the target software function library (i.e., a third-party library). Raw interfaces can include, but are not limited to, function interfaces, class interfaces, API interfaces, and library-level interfaces; the specific raw interface needs to be determined based on the software function library. Raw interfaces are a core component of the function library, defining the functions and services provided by the library, as well as the rules and methods for calling these functions and services, ensuring the standardization and consistency of the calls.

[0046] In one alternative embodiment, the library management module can indirectly call the original interface by using the target encapsulated interface, thereby enabling access to the functionality of the target software library. This encapsulation mechanism not only provides a security barrier but also allows the library management module to add additional monitoring, security checks, or performance optimization logic without changing the functionality of the original interface, thus enhancing the overall stability and security of the software.

[0047] For example, the process of calling a target software function library based on a target encapsulated interface essentially involves indirectly accessing its corresponding original interface through the target encapsulated interface to utilize the function library's capabilities. The original interface, as a core component of the function library, directly defines the services or functions provided by the library, as well as the rules and methods for calling these services or functions. When the library management module receives a call instruction from a client through the encapsulated interface, the module internally parses the mapping relationship between the encapsulated interface and the original interface to identify the specific original interface call requirement. Subsequently, the module will transparently proxy the call to the original interface based on this requirement, while performing security checks, permission verification, or logging to ensure the compliance and security of the call process. Finally, the target software function library responds to the call through the original interface, returning the expected processing result, while the client receives this result through the encapsulated interface, achieving efficient, secure, and unified access and management of the function library.

[0048] Step S108: Based on the library information of the target software function library, monitor the target software function library to obtain the monitoring result of the target software function library, wherein the monitoring result is used to indicate whether the target software function library meets the preset security conditions.

[0049] The aforementioned library information can refer to a series of detailed data about the target software's functional libraries. Library information may include, but is not limited to, the library's unique identifier (such as library name and version number), release date, license type, dependencies, and the library's latest security status. Specific library information needs to be determined based on actual management requirements. Library information can be used to manage different versions of the library, ensuring that the project uses a verified, stable version and can respond promptly to changes brought about by library updates. Simultaneously, library information can also be used to determine whether the library complies with enterprise or industry security standards, helping to prevent potential legal risks and security vulnerabilities.

[0050] The aforementioned monitoring results refer to the data set obtained after performing security monitoring on the target software library, reflecting whether the library's current state meets the preset security conditions. Monitoring results may include, but are not limited to, the target software library meeting or not meeting the preset security conditions; the specific monitoring results need to be determined based on the actual monitoring situation. Monitoring results can help the project team promptly identify and respond to library security issues, avoiding risks caused by vulnerabilities in third-party libraries. They can also be used to indicate which library versions have security issues, prompting the project team to consider whether to update or replace the libraries.

[0051] The aforementioned preset security conditions can refer to a set of standards and criteria defined by an enterprise or industry organization to measure and evaluate the security and compliance of third-party libraries. Preset security conditions may include, but are not limited to, security vulnerability thresholds, encryption compliance, license requirements, and security update frequency; specific preset security conditions need to be determined based on actual needs. Preset security conditions can be used to screen and exclude high-risk libraries, reducing potential losses caused by using insecure libraries. They can also be used to provide unified security standards, simplifying the library evaluation process and making security checks more systematic and automated.

[0052] In one optional embodiment, firstly, library information of the target software function library is collected, including but not limited to the library's name, version number, dependencies, license type, and known security vulnerability records. Subsequently, this library information is used to monitor the target software function library. After monitoring is complete, monitoring results are generated, indicating the security status of the target software function library, including whether it meets preset security conditions, such as the absence of high-risk vulnerabilities, the use of compliant licenses, and consistency with corporate security policies. This monitoring result is crucial for maintaining project security. It not only helps the project team quickly identify and respond to security changes in third-party libraries but also provides a basis for decision-making, enabling the implementation of relevant measures to maintain software security and compliance, avoid potential production accidents and regulatory risks, and thus effectively improve the stability and security of the entire software development process.

[0053] For example, an enterprise has a software library called "Math" (version 1.0.4). Its library information includes its name, version, a list of dependent libraries, license information, and a record of known security issues. The library management module periodically, or during library calls, monitors "Math" based on this information. The monitoring process involves examining the library's code to identify potential vulnerabilities, comparing it against a security database to confirm the presence of unpatched vulnerabilities, reviewing the license to ensure its use complies with enterprise policies, and analyzing dependencies to assess the risks of third-party libraries. Upon completion of monitoring, a monitoring result is generated, detailing whether "Math" meets preset security conditions. In this way, the enterprise can obtain the real-time security status of third-party libraries, enabling timely responses to security threats and ensuring the robust operation of software projects.

[0054] This application provides a method for managing software function libraries, applied to a library management module. First, upon receiving an instruction to call a target software function library, the module performs a judgment based on the permission information in the instruction, obtaining a judgment result. If the judgment result indicates that the permission information meets preset calling permissions, the module obtains the target encapsulation interface corresponding to the target software function library. Next, based on the original interface corresponding to the target encapsulation interface, the module calls the target software function library, where the original interface is the interface of the target software function library. Finally, based on the library information of the target software function library, the module monitors the target software function library, obtaining the monitoring result. In this management method, when the library management module receives a client's instruction to call a specific target software function library, it first obtains a specially designed target encapsulation interface corresponding to that target library. This encapsulation interface, while maintaining the integrity of the original library functions, provides a unified access standard and additional security control measures, enabling clients to call different libraries through a consistent interface, greatly simplifying the software development process. Next, the library management module indirectly calls the target software function library based on the target encapsulation interface through its corresponding original interface. Finally, the library management module monitors the target software function library based on its library information and generates monitoring results. These results clearly indicate whether the target software function library meets preset security conditions, thus achieving the technical objective of efficient management and monitoring of the software function library. This application, by constructing a collaborative working mechanism between the library encapsulation module and the monitoring mechanism, achieves efficient, standardized, and secure management of the software function library, greatly improving management efficiency and thus solving the technical problem of low management efficiency of software function libraries in related technologies.

[0055] Optionally, the method further includes: for any one of the multiple software function libraries, encapsulating the software function library to obtain the encapsulation interface corresponding to the software function library, wherein the encapsulation interface corresponding to the software function library corresponds to the original interface corresponding to the software function library.

[0056] The aforementioned multiple software function libraries refer to several different third-party libraries or modules integrated during the software development process to achieve specific functions or solve specific problems. In enterprise applications, especially financial software projects, these libraries can cover multiple areas such as data processing, encryption and decryption, network communication, and graphics rendering. Each library may have multiple versions, providing different functions and fixing different problems. Different libraries present different probabilities of security issues and compliance risks. Unified management of multiple software function libraries can enhance the overall system security and ensure compliance.

[0057] The encapsulation described above refers to hiding the implementation details of software function libraries and providing only a set of easy-to-understand and use interfaces. Encapsulation can unify the calling methods of different libraries, simplifying the development and maintenance work of the project team. At the same time, by encapsulating interfaces, library usage can be monitored, access permissions can be controlled, and improper use of libraries can be prevented.

[0058] The aforementioned encapsulated interfaces can refer to new interfaces created for software function libraries. These interfaces correspond one-to-one with the original library's interface functionality but may include additional detection and security features. Encapsulated interfaces can provide a simpler calling method, making them easier to integrate into projects. They also ensure that all project teams use the library in a consistent manner, facilitating unified management and maintenance.

[0059] In one alternative embodiment, a wrapper operation is performed on any one of the multiple software function libraries to create its corresponding wrapper interface. This process involves repackaging the original interface corresponding to the software function library, ensuring that each wrapper interface functionally corresponds one-to-one with its original interface. In this way, the project team calls the wrapper interface during development, rather than directly calling the original library's interface. Such wrapping not only maintains the functional integrity of the library but also allows enterprises to uniformly control and monitor the use of third-party libraries without affecting the core functionality of the software, ensuring that the use of all software function libraries complies with preset security conditions, thereby effectively improving the security management level of the entire software project.

[0060] Optionally, the method further includes: if the monitoring result indicates that the target software function library does not meet the preset security conditions, updating the target software function library to obtain the update result of the target software function library, wherein the update result is used to indicate whether the target software function library has been successfully updated; if the update result indicates that the target software function library has been successfully updated, updating the target encapsulation interface synchronously.

[0061] The aforementioned version update refers to taking action to migrate from the current version to a new version when a security vulnerability is detected in the target software feature library or it does not meet preset security conditions. The new version should have features that fix known security issues or provide higher security standards. The update methods mentioned above may include, but are not limited to, automatic updates, manual updates, and batch updates, and the specific update method should be determined based on actual needs. Version updates can be upgrades to a single library or a complete migration involving multiple interdependent libraries, ensuring that all related components work together without introducing new compatibility or security risks.

[0062] The update result mentioned above can refer to a feedback mechanism. The update result can be used to clearly identify whether the version update of the target software library was successfully completed. This result is usually determined based on whether the updated library can be compiled and run normally, and whether there are still security vulnerabilities or violations of preset security conditions.

[0063] In one alternative embodiment, when monitoring results indicate that the security status of a target software library does not meet preset standards, a version update operation is immediately performed on the library. This process typically involves finding and applying the latest patches or updating to a known more secure version, followed by a series of functional and compatibility tests to verify the success of the update. The update results serve as feedback information, clearly indicating whether the library has been successfully upgraded to a state that meets security requirements. If the update is confirmed to be successful, the next step is to synchronously update the target encapsulation interface associated with the library to ensure its compatibility with the new version of the library. This means adjusting any relevant parts of the encapsulation interface, such as method signatures, parameter types, or exception handling, to seamlessly integrate with the new library while maintaining the original encapsulation functionality, such as security checks and logging. This series of steps aims to continuously improve the security of the software project while reducing the burden on the development team in handling third-party library updates and compatibility issues.

[0064] Optionally, the method further includes: if the monitoring result indicates that the target software function library does not meet the preset security conditions, determining at least one software that uses the target software function library; sending a prompt message to the client corresponding to the at least one software, wherein the prompt message is used to prompt adjustments to the at least one software; and upgrading the library management module upon receiving the adjustment instruction sent by the client.

[0065] At least one of the aforementioned software programs can refer to a software project that relies on a specific target software function library during its development or operation. These projects can be different applications within an enterprise or customer-facing product software; they share the same third-party library but may have different functional requirements and security configurations.

[0066] The aforementioned notifications can refer to communication methods. Through these notifications, the monitoring system can convey important notifications regarding the security status of the target software's functional libraries to the software project's clients or development teams. These notifications can warn recipients of security vulnerabilities in currently used third-party libraries, requiring immediate adjustments. This helps raise awareness of potential security threats, prompting developers or administrators to react quickly and prevent further escalation of security incidents.

[0067] The aforementioned adjustment directive can refer to a formal request issued by the project team or client of the affected software after the monitoring system issues a warning about a security risk in the target software's functional library (third-party library). The adjustment directive can be used to instruct or authorize version upgrades, replacements, or other forms of adjustments to the library and / or its encapsulated interfaces. This is a proactive response mechanism that allows enterprises or project teams to respond quickly and effectively to monitoring results, ensuring the security and compliance of the software system.

[0068] The types of adjustment instructions mentioned above may include, but are not limited to, immediate update instructions, planned update instructions, replacement library instructions, and custom policy instructions. Immediate update instructions are used to request an immediate upgrade to a specified version, typically for patching urgent security vulnerabilities. Planned update instructions are used to schedule an upgrade operation at a future point in time, applicable to non-urgent but noteworthy security issues. Replacement library instructions are used to request replacement with another proven, more secure library when an existing library cannot resolve security issues through version updates. Custom policy instructions allow project teams to propose specific upgrade paths or security policies, which can be adjusted according to specific project needs. Specific adjustment instructions need to be determined based on actual requirements and are not limited here.

[0069] In one optional embodiment, when monitoring results show that the target software library does not meet preset security conditions, all software projects using the target software library are identified, i.e., "at least one software". Then, a customized notification message is sent to the end users or development teams of the at least one software, explaining the security issues and negative impacts of the target software library and suggesting relevant adjustment measures.

[0070] If the receiving client or development team decides to follow this recommendation, they can respond to the monitoring system by sending an adjustment command. At this point, the monitoring system not only records the software team's response but also guides relevant personnel to upgrade the library management module. This upgrade typically includes updating or replacing the target third-party library and simultaneously adjusting the corresponding encapsulated interfaces. The entire process aims to ensure that all software affected by third-party library security issues can respond quickly, achieving a complete resolution through upgrades, while simultaneously enhancing the enterprise's control and transparency regarding the use of third-party libraries and reducing the risk of similar issues occurring in the future.

[0071] For example, suppose a monitoring system in an internet service company discovers a critical security vulnerability in a widely used image processing library (ImageProcessorLib). This vulnerability could allow unverified remote code execution, threatening data security and user privacy. After confirming the monitoring results, it was found that multiple software projects within the company rely on this library, including image editors, social networking applications, and advertising management systems.

[0072] Next, the monitoring system will send customized alerts to the corresponding clients of these software programs, clearly pointing out the security issues in the current version of ImageProcessorLib and recommending immediate upgrades to the latest version, which has fixed the aforementioned security vulnerabilities. The alerts typically include a description of the problem, its potential impact, the recommended version number, and guidelines for the update process. Once the client (e.g., the project manager or security administrator) assesses the risk after receiving the alerts and decides to respond to the recommended adjustments, they will send an adjustment instruction through the company's internal security management system. This instruction not only confirms that the recipient is aware of the security issue but also authorizes the library management team to perform the upgrade operation, i.e., update the version of ImageProcessorLib and simultaneously adjust all related encapsulated interfaces to ensure the compatibility and security of the new version.

[0073] Upon receiving the adjustment instructions, the library management module was immediately updated to ensure that all software projects using "ImageProcessorLib" could be seamlessly migrated to the more secure version. After the upgrade was completed, the library management team would again verify through the monitoring system whether all affected software projects had been correctly upgraded and confirm that the security vulnerabilities had been eliminated. The entire process, through close collaboration between monitoring, notification, decision-making, and execution, effectively improved the overall security and responsiveness of the software projects.

[0074] Optionally, the method further includes: acquiring historical call records and library information of the target software function library based on a preset interval; generating monitoring results of the target software function library based on the historical call records and library information; and outputting the monitoring results.

[0075] The aforementioned preset interval duration refers to the periodic check frequency set in the monitoring system. The preset interval duration can include, but is not limited to, once per hour, once per day, or once per week. The specific preset interval duration needs to be determined based on project requirements and the external security environment. Setting the preset interval duration ensures that the status of third-party libraries can be checked automatically and periodically, promptly detecting security updates, vulnerability reports, or other important information. At the same time, setting a reasonable check frequency can balance the real-time nature of monitoring and system resource consumption, avoiding over-monitoring and ensuring that important security dynamics are captured within a reasonable timeframe.

[0076] The aforementioned historical call records refer to the history of calls made by the software to third-party library methods during runtime. These records may include, but are not limited to, call time, parameters, return results, and version information of the called functions; the specific historical call information needs to be determined based on actual requirements. Historical call records can provide detailed software behavior data for monitoring systems, helping to gain a deeper understanding of the actual usage scenarios and frequency of libraries. They can also be used to assess the impact of library updates or replacements on software performance and functionality, guiding the project team to develop reasonable upgrade plans.

[0077] In one optional embodiment, historical call records and library information of the target software function library are automatically retrieved based on preset intervals. The retrieved historical call records and library information are then analyzed to obtain monitoring results. Finally, the monitoring results are sent to relevant decision-makers to understand whether the target software function library meets security requirements and to recommend necessary actions. This process ensures continuous monitoring of third-party libraries, enabling timely detection and response to potential security risks.

[0078] For example, in a technology company's software development environment, the system is configured to perform automatic monitoring every 24 hours. At the end of the execution cycle, the system begins collecting data from all running services, paying particular attention to call records of the image processing library (ImageProcessorLib), and simultaneously obtaining the corresponding library information. The historical call records detail the time, method, parameters, and result of each library call; the library information includes the current version number, compilation time, and known security update status.

[0079] The system uses collected data to compare with the official security update logs of "ImageProcessorLib" to check if the currently used version has any known security vulnerabilities. If any mismatch is found, the system generates a monitoring report detailing the affected software services, specific security vulnerabilities, and recommended updates. The monitoring report is then automatically sent to relevant team emails and the project management platform, ensuring all key personnel receive timely notifications. Upon receiving the report, the relevant teams assess the affected software and, if necessary, initiate the upgrade process for the library management module to eliminate the security risks identified in the monitoring results. This series of steps forms a closed loop, effectively maintaining the security and stability of the software project through regular monitoring, analysis, reporting, and response.

[0080] According to another aspect of the embodiments of this application, a software function library management system is also provided, including: a library management module, used to provide multiple encapsulated interfaces corresponding to multiple software function libraries, and to obtain library information of a target software function library, wherein the multiple encapsulated interfaces correspond one-to-one with the original interfaces of the multiple software function libraries; and a monitoring platform, used to receive the library information and determine the monitoring results of the target software function library based on the library information.

[0081] The aforementioned monitoring platform can refer to a software system that receives information from a library management module. This information includes the version of the target software function library, its call history, and other key metrics. By analyzing this data, the platform assesses the security status, performance, and compliance of the software function library, thereby determining the monitoring results. The functions of the monitoring platform may include, but are not limited to, software function library security assessment, software function library performance analysis, software function library compliance checks, and software function library version control.

[0082] In one optional embodiment, a software function library management system includes a library management module and a monitoring platform. The library management module provides encapsulation interfaces for multiple software function libraries, ensuring a one-to-one correspondence between each encapsulation interface and the original interface of the software function library, while simultaneously collecting version and status information of the target software function libraries. The monitoring platform receives library information sent by the library management module and generates monitoring results about the software function libraries through analysis of the library information. This management system forms a closed-loop management mechanism for software function libraries, incorporating each step from resource encapsulation to status monitoring into automated management and monitoring, thereby improving management transparency and software security.

[0083] Optionally, the library management module includes a library encapsulation module and a library monitoring module, including: a library encapsulation module, used to encapsulate multiple software function libraries to obtain multiple encapsulation interfaces corresponding to the multiple software function libraries; and a library monitoring module, used to collect and transmit library information corresponding to the target software function library.

[0084] The aforementioned library encapsulation module can refer to a key component in the library management module. The library encapsulation module can be used to encapsulate various software function libraries. That is, while keeping the original functions of the library unchanged, an encapsulation layer is added to the library. This encapsulation layer is usually manifested as a set of new interfaces (APIs). These new interfaces correspond one-to-one with the original interfaces of the library, but through them, the application can indirectly call the functions of the library without directly interacting with the library.

[0085] The aforementioned library monitoring module can refer to another important component in the library management module. Its responsibility is to collect the operation information and version data of the target software function library, including the library's usage frequency, call time, version number, etc., and then transmit this data to the monitoring platform for analysis.

[0086] In one optional embodiment, the library management module consists of a library encapsulation module and a library monitoring module. The library encapsulation module acts as an interface converter for software function libraries. Its main task is to encapsulate multiple software function libraries, generating corresponding encapsulated interfaces. These encapsulated interfaces match the original library's interface functionality, but through a unified calling standard, they provide the project team with an intermediate layer to indirectly use the software function libraries, thereby simplifying the library integration and management process. The library monitoring module is responsible for collecting and transmitting library information. When a target software function library is called in a project, it captures key information such as the library's type, version, and calling status, and transmits this data to the monitoring platform for subsequent analysis and management.

[0087] In one alternative embodiment, Figure 2 This is a schematic diagram of software function library management according to an embodiment of this application, such as... Figure 2 As shown, Figure 2 It includes multiple third-party libraries, namely Third-Party Library 1, Third-Party Library 2, Third-Party Library, etc. The third-party library management module includes a third-party library encapsulation sub-module and a third-party library monitoring sub-module, multiple project groups, namely Project Group 1, Project Group 2, Project Group, etc., as well as an enterprise third-party library monitoring platform.

[0088] Specifically, the third-party library management module contains two sub-modules: the third-party library encapsulation sub-module and the third-party library monitoring sub-module. The third-party library encapsulation sub-module encapsulates specified versions of common third-party libraries, maintaining functionality while opening new API interfaces for various project teams to use. These new API interfaces have a one-to-one relationship with the third-party library's API interface. The third-party library monitoring sub-module monitors which third-party libraries a project team uses. When a project team's software goes live, the monitoring module is triggered when a third-party library's API interface is called for the first time. The monitoring module collects the third-party library type and version information, as well as the current software's name and version information, and uploads this data to the monitoring platform.

[0089] Before software development, the project team selects an appropriate version of the third-party library management module for import, indirectly importing the corresponding third-party libraries. The functionality of the third-party libraries is used indirectly by calling the functions of the encapsulated sub-modules. The monitoring platform is responsible for collecting information on the versions of the third-party libraries that various enterprise software depends on, and provides enterprise managers with query views. When a third-party library has a security issue and requires a version change, the enterprise upgrades the third-party library management module and updates the corresponding third-party library version. Enterprise managers identify enterprise software with third-party library security issues by querying the monitoring platform and require the corresponding project team to rectify the problem. The project team completes the rectification by upgrading the third-party library management module version. Enterprise managers confirm whether each project team has completed the rectification by querying the monitoring platform.

[0090] According to an embodiment of this application, a software function library management device is provided. It should be noted that this device can be used to execute the aforementioned software function library management method. The specific implementation method and preferred application scenarios are the same as those in the above embodiment, and will not be repeated here.

[0091] Figure 3 This is a schematic diagram of a software function library management device according to an embodiment of this application, such as... Figure 3 As shown, the device includes: a judgment module 302, an acquisition module 304, a calling module 306, and a monitoring module 308.

[0092] The judgment module 302 is used to judge based on the permission information in the instruction when receiving an instruction to call the target software function library, and obtain a judgment result, wherein the judgment result is used to indicate whether the client's permission information meets the preset calling permissions; the acquisition module 304 is used to acquire the target encapsulation interface corresponding to the target software function library when the judgment result indicates that the permission information meets the preset calling permissions, wherein the target encapsulation interface is used to characterize the interface used by the client to call the target software function library, and the target software function library is determined from multiple software function libraries based on the software function library identification information in the instruction, wherein the software function library identification information is used to represent a unique identifier for identifying the target software function library; the calling module 306 is used to call the target software function library based on the original interface corresponding to the target encapsulation interface, wherein the original interface is the interface of the target software function library; the monitoring module 308 is used to monitor the target software function library based on the library information of the target software function library, and obtain a monitoring result of the target software function library, wherein the monitoring result is used to indicate whether the target software function library meets the preset security conditions.

[0093] Optionally, the device is also used to encapsulate any one of the multiple software function libraries to obtain the encapsulation interface corresponding to the software function library, wherein the encapsulation interface corresponding to the software function library corresponds to the original interface corresponding to the software function library.

[0094] Optionally, the device is also used to update the target software function library when the monitoring result indicates that the target software function library does not meet the preset security conditions, and obtain the update result of the target software function library, wherein the update result is used to indicate whether the target software function library has been successfully updated; if the update result indicates that the target software function library has been successfully updated, the target encapsulation interface is updated synchronously.

[0095] Optionally, the device is also configured to: determine at least one software using the target software function library if the monitoring result indicates that the target software function library does not meet the preset security conditions; send a prompt message to the client corresponding to the at least one software, wherein the prompt message is used to prompt adjustments to the at least one software; and upgrade the library management module upon receiving the adjustment instruction sent by the client.

[0096] Optionally, the device is also used to acquire historical call records and library information of the target software function library based on a preset interval; generate monitoring results of the target software function library based on the historical call records and library information; and output the monitoring results.

[0097] Embodiments of this application also provide an electronic device, including: a memory storing an executable program; and a processor for running the program, wherein the program executes the methods in various embodiments of this application when it runs.

[0098] Embodiments of this application also provide a computer-readable storage medium including a stored executable program, wherein, when the executable program is running, it controls the device where the computer-readable storage medium is located to perform the methods of various embodiments of this application.

[0099] Embodiments of this application also provide a computer program product, including a computer program that, when executed by a processor, implements the methods of various embodiments of this application.

[0100] Embodiments of this application also provide a computer program product, including a non-volatile computer-readable storage medium for storing a computer program that, when executed by a processor, implements the methods in various embodiments of this application.

[0101] Embodiments of this application also provide a computer program that, when executed by a processor, implements the methods described in the various embodiments of this application.

[0102] In the above embodiments of this application, the descriptions of each embodiment have different focuses. For parts not described in detail in a certain embodiment, please refer to the relevant descriptions of other embodiments.

[0103] In the several embodiments provided in this application, it should be understood that the disclosed technical content can be implemented in other ways. The device embodiments described above are merely illustrative; for example, the division of units can be a logical functional division, and in actual implementation, there may be other division methods. For instance, multiple units or components may be combined or integrated into another system, or some features may be ignored or not executed. Furthermore, the displayed or discussed mutual coupling, direct coupling, or communication connection may be through some interfaces; the indirect coupling or communication connection between units or modules may be electrical or other forms.

[0104] The units described as separate components may or may not be physically separate. The components shown as units may or may not be physical units; that is, they may be located in one place or distributed across multiple units. Some or all of the units can be selected to achieve the purpose of this embodiment according to actual needs.

[0105] Furthermore, the functional units in the various embodiments of this application can be integrated into one processing unit, or each unit can exist physically separately, or two or more units can be integrated into one unit. The integrated unit can be implemented in hardware or as a software functional unit.

[0106] If the integrated unit is implemented as a software functional unit and sold or used as an independent product, it can be stored in a computer-readable storage medium. Based on this understanding, the technical solution of this application, in essence, or the part that contributes to the prior art, or all or part of the technical solution, can be embodied in the form of a software product. This computer software product is stored in a storage medium and includes several instructions to cause a computer device (which may be a personal computer, server, or network device, etc.) to execute all or part of the steps of the methods described in the various embodiments of this application. The aforementioned storage medium includes various media capable of storing program code, such as a USB flash drive, read-only memory (ROM), random access memory (RAM), portable hard drive, magnetic disk, or optical disk.

[0107] The above description is only a preferred embodiment of this application. It should be noted that for those skilled in the art, several improvements and modifications can be made without departing from the principle of this application, and these improvements and modifications should also be considered within the scope of protection of this application.

Claims

1. A method for managing a software function library, characterized in that, Applied to the library management module, the method includes: Upon receiving an instruction to call a target software function library, a judgment is made based on the permission information in the instruction to obtain a judgment result, wherein the judgment result is used to indicate whether the client's permission information meets the preset calling permissions; If the judgment result is that the permission information meets the preset calling permission, the target encapsulation interface corresponding to the target software function library is obtained. The target encapsulation interface is used to characterize the interface used by the client to call the target software function library. The target software function library is determined from multiple software function libraries based on the software function library identification information in the instruction. The software function library identification information is used to represent a unique identifier for identifying the target software function library. Based on the original interface corresponding to the target encapsulation interface, the target software function library is called, wherein the original interface is the interface of the target software function library; Based on the library information of the target software function library, the target software function library is monitored to obtain the monitoring result of the target software function library, wherein the monitoring result is used to indicate whether the target software function library meets the preset security conditions.

2. The method according to claim 1, characterized in that, The method further includes: For any one of the multiple software function libraries, the software function library is encapsulated to obtain the encapsulation interface corresponding to the software function library, wherein the encapsulation interface corresponding to the software function library corresponds to the original interface corresponding to the software function library.

3. The method according to claim 1, characterized in that, The method further includes: If the monitoring result indicates that the target software function library does not meet the preset security conditions, the target software function library is updated to obtain the update result of the target software function library, wherein the update result is used to indicate whether the target software function library has been successfully updated; If the update result indicates that the target software function library has been successfully updated, the target encapsulation interface is updated synchronously.

4. The method according to claim 3, characterized in that, The method further includes: If the monitoring result indicates that the target software function library does not meet the preset security conditions, then at least one software using the target software function library is determined. Send a prompt message to the client corresponding to the at least one software, wherein the prompt message is used to prompt adjustments to the at least one software; Upon receiving an adjustment instruction from the client, the library management module is upgraded.

5. The method according to any one of claims 1 to 4, characterized in that, The method further includes: Based on a preset interval, obtain the historical call records of the target software function library and the library information; Based on the historical call records and the library information, a monitoring result for the target software function library is generated; Output the monitoring results.

6. A software function library management system, characterized in that, include: The library management module is used to provide multiple encapsulation interfaces corresponding to multiple software function libraries and to obtain the library information of the target software function library, wherein the multiple encapsulation interfaces correspond one-to-one with the original interfaces of the multiple software function libraries. A monitoring platform is used to receive the library information and determine the monitoring results of the target software function library based on the library information.

7. The system according to claim 6, characterized in that, The library management module includes a library encapsulation module and a library monitoring module, including: The library encapsulation module is used to encapsulate the plurality of software function libraries to obtain the plurality of encapsulation interfaces corresponding to the plurality of software function libraries; The library monitoring module is used to collect and transmit the library information corresponding to the target software function library.

8. An electronic device, characterized in that, include: Memory, which stores executable programs; A processor for running the program, wherein the program, when running, performs the method according to any one of claims 1 to 5.

9. A computer-readable storage medium, characterized in that, The computer-readable storage medium includes a stored executable program, wherein, when the executable program is executed, it controls the device on which the storage medium is located to perform the method according to any one of claims 1 to 5.

10. A computer program product, characterized in that, Includes a computer program that, when executed by a processor, implements the method according to any one of claims 1 to 5.

Images