CN113743895A

CN113743895A - Component management method and device, computer equipment and storage medium

Info

Publication number: CN113743895A
Application number: CN202111003389.1A
Authority: CN
Inventors: 李安冉
Original assignee: OneConnect Financial Technology Co Ltd Shanghai
Current assignee: OneConnect Smart Technology Co Ltd; OneConnect Financial Technology Co Ltd Shanghai
Priority date: 2021-08-30
Filing date: 2021-08-30
Publication date: 2021-12-03

Abstract

The embodiment of the invention discloses a component management method, a device, computer equipment and a storage medium, wherein the component management method is applied to a component ecosystem and comprises the following steps: developing the component according to a preset component development template in response to a component development instruction triggered by a component development user; in response to a packaging component instruction and a packaging component uploading instruction triggered by a component development user, packaging the developed components to form a packaging component, and uploading the packaging component to a component to-be-audited cache region of a component ecosystem; and auditing the packaged components in the cache region to be audited of the components, and storing the packaged components in a component developer warehouse of a component development user under the condition that the packaged components are determined to pass the auditing. The technical scheme of the embodiment of the invention can enrich and perfect the development function of the component, and improve the safety and usability of the component, thereby improving the user experience.

Description

Component management method and device, computer equipment and storage medium

Technical Field

The embodiment of the invention relates to the technical field of computers and artificial intelligence, in particular to a component management method, a component management device, computer equipment and a storage medium.

Background

At present, front-end open source component libraries are various, and the use, configuration and style of each component library are different. Since all the components in the open source component library are general components, when a developer installs and uses the components in the open source component library in a project by using a certain open source component library, there is a case that the components in the open source component library are not suitable or have no related components. At this time, the developer needs to pull other more suitable open source component libraries or customize a set of component libraries, which forms a plurality of component packages in the development project and virtually increases the volume of the project.

In order to solve the problem of individual requirements of the components and reduce the project volume increased by the number of the components, part of the component development system realizes the function of individually customizing and developing the components. However, the component development system often only provides development functions of personalized components, and only brand new components can be developed according to development requirements of developers, but cannot provide richer functions related to the components, and cannot ensure the safety and usability of the components, so that the developed components still cannot meet the component use requirements of the developers, and the user experience of the component development system is reduced.

Disclosure of Invention

The embodiment of the invention provides a component management method, a component management device, computer equipment and a storage medium, which can enrich and perfect the development function of a component and improve the safety and usability of the component, thereby improving the user experience.

In a first aspect, an embodiment of the present invention provides a component management method, which is applied to a component ecosystem, where the component management method includes:

developing the component according to a preset component development template in response to a component development instruction triggered by a component development user; wherein the type of the component comprises at least one of a newly built component or a secondarily developed component;

responding to a packaging component instruction and a packaging component uploading instruction triggered by the component development user, packaging the developed components to form a packaging component, and uploading the packaging component to a component to-be-audited cache region of the component ecosystem;

and auditing the packaged components in the cache region to be audited of the components, and storing the packaged components in a component developer warehouse of the component development user under the condition that the packaged components are determined to pass the auditing.

In a second aspect, an embodiment of the present invention further provides a component management apparatus configured in a component ecosystem, including:

the component development module is used for responding to a component development instruction triggered by a component development user and developing a component according to a preset component development template; wherein the type of the component comprises at least one of a newly built component or a secondarily developed component;

the component packaging and uploading module is used for responding to a packaging component instruction and a packaging component uploading instruction triggered by the component development user, packaging the developed components to form packaging components, and uploading the packaging components to a component to-be-audited cache region of the component ecosystem;

and the packaging component auditing storage module is used for auditing the packaging components in the cache region to be audited of the components and storing the packaging components in a component developer warehouse of the component development user under the condition that the packaging components are determined to pass the auditing.

In a third aspect, an embodiment of the present invention further provides a computer device, where the computer device includes:

one or more processors;

storage means for storing one or more programs;

when the one or more programs are executed by the one or more processors, the one or more processors are caused to implement the component management method provided by any embodiment of the present invention.

In a fourth aspect, an embodiment of the present invention further provides a computer storage medium, on which a computer program is stored, where the computer program is executed by a processor to implement the computer method provided in any embodiment of the present invention.

The embodiment of the invention responds to the component development instruction triggered by the component development user by utilizing the component ecosystem so as to develop the newly-built component or the secondary development component according to the preset component development template. After the component development is completed, in response to a packaging component instruction and a packaging component uploading instruction triggered by a component development user, packaging the component developed by the component development user, uploading the packaged component to a component to-be-checked cache region of a component ecosystem, checking the packaging component uploaded by the component development user in the component to-be-checked cache region, and storing the packaging component uploaded by the component development user in a component developer warehouse of the component development user under the condition that the packaging component uploaded by the component development user is confirmed to pass the checking. Therefore, the component ecosystem provided by the embodiment of the invention not only can support the brand new development function and the secondary development function of the personalized component, but also can support the examination and verification of the developed component so as to determine the safety and the usability of the component, solve the problem of single component development function of the existing component development system, enrich and perfect the development function of the component, improve the safety and the usability of the component and further improve the user experience.

Drawings

FIG. 1 is a flowchart of a component management method according to an embodiment of the present invention;

FIG. 2 is a flowchart of a component management method according to a second embodiment of the present invention;

FIG. 3 is a flowchart of a component management method according to a second embodiment of the present invention;

FIG. 4 is a diagram illustrating a component management apparatus according to a fourth embodiment of the present invention;

fig. 5 is a schematic structural diagram of a computer device according to a fourth embodiment of the present invention.

Detailed Description

The present invention will be described in further detail with reference to the accompanying drawings and examples. It is to be understood that the specific embodiments described herein are merely illustrative of the invention and are not limiting of the invention.

It should be further noted that, for the convenience of description, only some but not all of the relevant aspects of the present invention are shown in the drawings. Before discussing exemplary embodiments in more detail, it should be noted that some exemplary embodiments are described as processes or methods depicted as flowcharts. Although a flowchart may describe the operations (or steps) as a sequential process, many of the operations can be performed in parallel, concurrently or simultaneously. In addition, the order of the operations may be re-arranged. The process may be terminated when its operations are completed, but may have additional steps not included in the figure. The processes may correspond to methods, functions, procedures, subroutines, and the like.

The terms "first" and "second," and the like in the description and claims of embodiments of the invention and in the drawings, are used for distinguishing between different objects and not for describing a particular order. Furthermore, the terms "comprising" and "having," as well as any variations thereof, are intended to cover non-exclusive inclusions. For example, a process, method, system, article, or apparatus that comprises a list of steps or elements is not set forth for a listed step or element but may include steps or elements not listed.

First, an embodiment of the present invention provides a component ecosystem. Optionally, the modular ecosystem may comprise two sets of forms and a set of modular ecological scaffolds. The templates may include component development templates and project framework templates, among others.

Specifically, the component development template is used to define a framework of ecological development components, all of which are developed under a unified directory in the framework. The component development user can develop the components through the component development template, install the existing components and develop the existing components secondarily, pack the components, upload the components to the component ecosystem, and the like. Each component developed through the component development template is a folder, and the component development template can independently pack each developed component into a component file.

The project framework template is used for defining a front-end project development infrastructure, a project developer can acquire a project type to be developed by configuring related parameters for the project framework template, and install components and package projects to run online on the basis of the determined project type. For example, the project types obtained by the project developer by configuring the relevant parameters for the project framework template may include, but are not limited to, a middle platform template at a Web end, an office system template at the Web end, an e-commerce platform template at the Web end, a middle platform template at a PC (Personal Computer) end, an office system template at a PC end, an e-commerce platform template at a PC end, a middle platform template at a mobile phone end, an office system template at a mobile phone end, an e-commerce platform template at a mobile phone end, and the like.

The component ecological scaffold can be used for installing component development templates to develop components and can also be used for installing project framework templates to develop projects. Meanwhile, the ecological scaffold for the components can also be provided with functions of installing the components in a project, reporting component feedback, unloading the components in the project and the like.

Therefore, the component ecosystem provides a function of ecological management of the components, and developers can quickly acquire the required components through the component ecological construction system, so that the project development efficiency and the development quality are improved. Meanwhile, the components developed by the component ecological construction system can realize open source processing, and different users do not need to repeatedly develop the components for the second time, so that the service efficiency of the components is improved.

Example one

Fig. 1 is a flowchart of a component management method according to an embodiment of the present invention, where the embodiment is applicable to a case where personalized, high-security and high-availability components are developed, and the method may be executed by a component management apparatus, which may be implemented by software and/or hardware, and may be generally integrated in a computer device. Accordingly, as shown in fig. 1, the method comprises the following operations:

s110, responding to a component development instruction triggered by a component development user, and developing a component according to a preset component development template; wherein the type of the component comprises at least one of a newly created component or a secondarily developed component.

Wherein, the component development user is also the user who develops the personalized component by utilizing the component ecosystem. The component development instructions can be instructions triggered by a component development user utilizing the component ecosystem, and can be used to instruct the component ecosystem to begin developing the component. The component development template is also a framework for ecologically developing components in the component ecosystem. The newly created component can be a newly developed component, and the secondarily developed component can be a component developed again on the basis of the existing component.

In embodiments of the present invention, a component development user can develop components using a component ecosystem. In particular, a component development user can trigger component development instructions of the component ecosystem to instruct the component ecosystem to develop components according to component development templates integrated within the system. Optionally, the component development user may trigger the component development instruction through the component development template.

It should be noted that, the component development template of the ecological component system in the embodiment of the present invention may not only develop a brand new component to obtain a newly built component, but also perform secondary development on the basis of an existing component to obtain a secondary development component.

In an optional embodiment of the present invention, the developing a component according to a preset component development template may include: determining parameters to be configured of the component development template, and performing parameter configuration on the parameters to be configured to generate the newly-built component; and/or installing the existing component through the component development template, and modifying the component parameters of the existing component to generate the secondary development component.

The parameters to be configured may be parameters that need to be assigned to the component development template, may be partial or all component parameters, and may be used to determine the type and function of the component. It can be understood that the parameters to be configured and the assignment of the parameters are different, and the functions of the generated components are also different.

Specifically, a component development user can directly develop the new component through the component development template, that is, the parameter to be configured of the component development template is determined according to the component development requirement, and the parameter configuration is performed on the determined parameter to be configured, so that the new component is generated. It should be noted that the parameter configuration content of the parameter to be configured may include, but is not limited to, variables in the form of numeric values or characters, and functional segments defined in a code language, as long as the configuration of the parameter to be configured can be completed to complete the development of the component, and the parameter configuration content of the parameter to be configured is not limited in the embodiment of the present invention. Or the component development user can directly install the existing component in the component development template and modify the component parameters of the component installed in the component development template, so that open source processing of secondary development of the existing component is completed, and the secondary development component is generated.

Therefore, the component developed by the component ecosystem can realize open source processing, and different users do not need to repeatedly develop the component for the second time, so that the use efficiency of the component is improved.

And S120, responding to a packaging component instruction and a packaging component uploading instruction triggered by the component development user, packaging the developed components to form packaging components, and uploading the packaging components to a component to-be-audited cache region of the component ecosystem.

Wherein the package component instructions can be used to instruct the component ecosystem to package the component developed by the component development user. And the packaging component uploading instruction is used for instructing the component ecosystem to upload the components packaged by the component development user to a system for storage. The cache region to be checked of the component can be a region for caching the component in the component ecosystem. Optionally, the component development user may trigger the packaging component instruction and the packaging component upload instruction through the component development template.

Correspondingly, after the component development user develops the component through the component development template of the component ecosystem, the component development user can further trigger a packaging component instruction by using the component development template. At this point, the component development template may package the components developed by the component development user. After the assembly is packaged, the assembly development user can further trigger a packaging assembly uploading instruction by using an assembly development template. At this time, the component development template can upload the packaged components to a cache region to be checked of the component ecosystem, so as to check the packaged components uploaded by a component development user. Optionally, the components developed by the component development template may be in a folder form, and the component development template may package each developed component individually into a component file.

Therefore, the component development template in the component ecosystem can support component development functions of developing components, installing the existing components, secondarily developing the existing components, packaging the components, uploading the components to the component ecosystem and the like.

S130, auditing the packaging assembly in the cache region to be audited of the assembly, and storing the packaging assembly in an assembly developer warehouse of the assembly development user under the condition that the packaging assembly is confirmed to pass the auditing.

Wherein the component developer repository may be a repository of component ecosystems that develop user-defined storage components for each component. Each component developer can correspondingly establish a component developer warehouse in the component ecosystem, and the component developers can maintain and manage the components developed by the component developers through the component developer warehouse.

In order to further determine the security and the availability of the components, after the component developer completes component development and uploading by using a component development template of the component ecosystem, the component ecosystem can audit the packaged components uploaded to the component to-be-audited cache region by each component development user. For example, the audit content of the package component may include, but is not limited to, a security audit, an availability audit, and the like, and the specific audit content of the package component is not limited in the embodiments of the present invention. Accordingly, when the packaged component passes the audit, the component ecosystem can determine that the packaged component has security and availability, and therefore the packaged component can be stored in a component developer repository corresponding to the component development user.

The component ecosystem manages the components developed by each component development user in a component developer repository, but the component development users can access and acquire the components in the component developer repositories of other component development users to utilize or secondarily develop the components of the other component development users. It should also be noted that only the component development user who developed the component has the right to uninstall the component. That is, a component development user can uninstall a component in its component developer repository, but cannot uninstall a component in the component developer repository of other component development users.

Example two

Fig. 2 is a flowchart of a component management method according to a second embodiment of the present invention, which is embodied based on the above embodiments, and in this embodiment, various specific optional implementation manners for checking a packaged component uploaded by a component development user in a cache region to be checked of a component and an executable operation before component development are given. Correspondingly, as shown in fig. 2, the method of the present embodiment may include:

s210, obtaining system login information of the component development user login component ecosystem.

The system login information can be information of a component development user for logging in the component ecosystem, and can be a user account, a user password and the like. Optionally, the user account may be a mailbox, a mobile phone number, or other named identifier of the user, which is not limited in the embodiment of the present invention.

It will be appreciated that if a component development user does not register the component ecosystem, it will first need to perform a registration operation with the component ecosystem before it can manage the component using the component ecosystem. The component development user can log in to the component ecosystem according to the registered information to manage the component.

And S220, creating a component developer warehouse matched with the component development user according to the system login information of the component development user.

Wherein the component developer repository is to maintain component information developed by the component development user.

Correspondingly, after the component development user logs in the component ecosystem, if the component development user does not create a component developer warehouse in the component ecosystem, the component ecosystem can collect the system login information of the component development user so as to automatically create the component developer warehouse matched with the component development user according to the system login information, and therefore the component of the component developer is managed and maintained through the component developer warehouse, such as component development, component release, component installation and component unloading.

In a specific example, assuming that the component ecosystem is a website-type system, after a component development user logs in the component ecosystem, a "new warehouse" function of the component ecosystem can be triggered, and then a page of a new developer warehouse is opened. Further, the component development user can configure the repository information of the component developer repository in the page of the newly created developer repository. Alternatively, the repository information of the component developer repository may include at least "repository name", "home", "path", "repository introduction", "whether to open source", "select language", "add open source license", and "initialize repository", and the like. Wherein, the "warehouse name" represents the name of the warehouse and is used for the warehouse name. "Home" means a repository home account, which may be one of a personal account number/organization/enterprise, that defaults to the owner of the repository after successful creation. "Path" represents the git (a code hosting technique) access path of the repository, and may consist of "user-specific address + repository path name". The user will access the repository through this path after the repository is created. "warehouse description" is also a brief description of a warehouse. "open source" means that whether the warehouse is set to be a public warehouse, the public warehouse is visible to all people, and the private warehouse is visible only to warehouse members. The "selected language" may determine the programming language in which the warehouse is primarily developed. "Add open Source license" means that if the warehouse is a public warehouse, an open Source agreement setting the warehouse may be added as a licensing constraint for the current project warehouse and the derived project warehouse. The "initialize repository" may then select the corresponding file template to initialize the repository.

Optionally, the component ecosystem may default to a warehouse name, an attribution, and the like according to the system login information of the component development user. For other parameters to be configured, a component development user can configure while creating a component developer warehouse, or can ignore the configuration and assign values by the component ecosystem by adopting default parameters. And in the process of using the component development warehouse, the component development user can configure each configuration parameter of the component development warehouse according to the development requirement.

According to the technical scheme, the components developed by each component development user are managed in a component developer warehouse mode, distributed management of the components is achieved, and rights and interests of the component development users for managing and maintaining the components can be effectively maintained.

And S230, responding to a component ecological scaffold starting instruction triggered by the component development user, and installing the component development template through the component ecological scaffold.

The starting instruction of the component ecological scaffold can be an instruction triggered by a component development user by utilizing a component ecological system, and can be used for indicating the component ecological system to start the component ecological scaffold. The scaffold mentioned in the front-end development is an image metaphor which is similar to the previous working environment of various languages. What the scaffold fingers on software development (including front-end development) are: tools and development environments used in the development process are configured in advance, and the development environments are scaffolds. Correspondingly, the component ecological scaffold is also a pre-configured component development environment.

In the embodiment of the invention, when a component development user develops a component, the component ecological scaffold of the component ecological system can be started, so that the component development template is installed through the component ecological scaffold, and the component is further developed by utilizing the component development template.

In a specific example, the specific implementation process of installing the component development template through the component ecological scaffold can be as follows: the component ecosystem, which is configured with an npm (node package manager, a package management tool for nodejs) warehouse of component ecological scaffolds, may first install the component ecological scaffold through its npm warehouse, such as the input command line "npm install component-cli-g," where "component-cli" is the name of the component ecological scaffold. After the ecological scaffold is successfully installed, the component development template can be installed locally through the ecological scaffold, for example, a command line "component-cli create _ component project _ name" is input, where "project _ name" is a name of the component development template installed locally. After successful installation, the component development user can open project _ name for component development using a front-end development tool, such as VScode (visual Stdio code).

S240, responding to an assembly development instruction triggered by the assembly development user, and developing an assembly according to a preset assembly development template; wherein the type of the component comprises at least one of a newly created component or a secondarily developed component.

And S250, responding to a packaging component instruction and a packaging component uploading instruction triggered by the component development user, packaging the developed components to form packaging components, and uploading the packaging components to a component to-be-audited cache region of the component ecosystem.

S260, carrying out security vulnerability scanning and attack scanning on the packaging assembly.

Specifically, after the component development user packages and uploads the developed components to the component to-be-audited cache region of the component ecosystem, the component ecosystem can firstly perform security vulnerability scanning and attack scanning on the packaged components to determine that the packaged components do not have security vulnerability problems and security problems.

In one specific example, the component ecosystem can employ an APPScan standard edition (automated application security scanning and testing tool) to perform security vulnerability scanning and attack scanning on packaged components. Specifically, the component ecosystem creates a scanning task through the APPScan, and configures a scanning path as a code path of the uploaded packaged component. Further, the scan is initiated by the APPScan, which automatically retrieves the internal structure of the packaged component before performing various tests. After the scan is completed, the APPScan may output the relevant detailed scan result. And if the APPScan determines that the packaged component has security holes and/or attacks according to the scanning result, a report is derived and sent to a component developer for repairing.

And S270, judging whether the packaging assembly is successfully scanned, if so, executing S280, and otherwise, executing S2B 0.

S280, sending the packaging assemblies to a first preset number of examination and approval personnel, and accepting examination and approval results of the set number of examination and approval personnel.

The first preset number may be set according to an actual requirement, such as 10 or 20, and the embodiment of the present invention does not limit a specific numerical value of the first preset number. The approver may be a person who audits the component developed by the component development user. The set number can also be set according to actual requirements, such as 3 or 5, and the embodiment of the present invention does not limit the specific value of the set number. It will be appreciated that the set number is less than the first predetermined number.

And S290, judging whether all the approval results pass the approval, if so, executing S2A0, and otherwise, executing S2B 0.

And S2A0, determining that the packaging component passes the audit, and storing the packaging component uploaded by the component development user in a component developer warehouse of the component development user.

And S2B0, determining that the packaging component does not pass the audit, and sending component audit failure information to the component development user.

The component audit failure information may be information notifying the component development user that the component fails to be audited.

Accordingly, after the packaged component passes through the security vulnerability scanning and the attack scanning, the packaged component can be determined to be successfully scanned. In order to ensure that the component has availability, the component ecosystem can further send the scanned packaged component to a plurality of approvers, and each approver manually checks the availability of the component. For example, the inside of the audit for manually auditing the availability of the component by each approver may include, but is not limited to, whether the function of the component is normal, whether data output after the component is tested meets a preset index requirement, whether the component has practicability, and the like. Considering that the component issuing efficiency is delayed due to the fact that part of the examination and approval personnel do not feed back timely, the examination and approval results of the examination and approval personnel with set quantity can be set and received, and whether the packed component is finally approved or not is judged according to the received examination and approval results. For example, when the package component is sent to 20 approvers, if 3 approvers firstly feed back the approval result, it may be determined whether the package component passes the audit according to the approval result fed back by the 3 approvers. If all the approval results are approved, the packaged component can be determined to pass the approval, and the component can have no problem and has usability. At this point, the component ecosystem can feed back to the component development user that the component published successful information. If all the approval results are approved, the packaged component can be determined to pass the approval, and the component can have no problem and has usability. If the scanning of the packaging component fails or the approval result comprises the condition of failure of approval, determining that the packaging component fails to be approved, and indicating that the component has certain problems and is not available. At this point, the component ecosystem can send component audit failure information to the component development user to feed back the component release failure information, such as informing the component development user that the component failed scanning or manual auditing. Meanwhile, the component audit failure information may also include specific reasons causing component audit failure, such as which security holes exist or specific problems of the components fed back by the approval staff.

Or, if the step of manually checking the components can be completed through the corresponding test cases, after the packaged components pass security vulnerability scanning and attack scanning, automatic test checking can be performed on the packaged components according to the built-in test cases of the component ecosystem, and the checking result is fed back to the component development user, so that the manual checking mode is replaced by the mode of automatically testing through the test cases.

Optionally, the component ecosystem may obtain the contact information of the user according to a component developer repository of the component development user, so as to publish information to the component development user feedback component. For example, if the system login information of the component development user is a user mailbox, the component ecosystem may acquire the mailbox of the component development user by using the component developer repository of the component development user, and notify the component development user of component release information, such as successful release or failure release, by using a mail. If the system login information of the component development user is the mobile phone number of the user, the component ecosystem can acquire the mobile phone number of the component development user by using the component developer warehouse of the component development user and inform the component development user of component release information through short messages, such as successful release or failed release.

According to the technical scheme, after a component development user develops the component by using the component ecosystem, the developed component is audited by the component ecosystem, so that the safety and usability of the component in the component ecosystem can be ensured, the problems of safety and usability of the component are avoided, and the user experience is improved.

EXAMPLE III

Fig. 3 is a flowchart of a component management method according to a second embodiment of the present invention, which is embodied based on the second embodiment, and in this embodiment, a plurality of specific optional implementation manners for searching and installing components in a project to be developed by using a component ecosystem are given. Accordingly, as shown in fig. 3, the method of the present embodiment may include:

s310, responding to a component development instruction triggered by the component development user, and developing a component according to a preset component development template; wherein the type of the component comprises at least one of a newly created component or a secondarily developed component.

And S320, responding to a packaging component instruction and a packaging component uploading instruction triggered by the component development user, packaging the developed components to form packaging components, and uploading the packaging components to a component to-be-audited cache region of the component ecosystem.

S330, auditing the packaged components in the cache region to be audited of the components, and storing the packaged components in a component developer warehouse of the component development user under the condition that the packaged components are confirmed to pass the auditing.

S340, responding to a project development instruction triggered by a project development user, and determining a project template to be developed of a project to be developed; the project templates to be developed comprise project templates stored in a system and project framework templates installed by the component ecological scaffolds.

Wherein, the project development user is also the user of the component development project stored by the component ecosystem. The project to be developed is also the project which needs to be developed by the project development user. The to-be-developed project template may be a project template for a to-be-developed project. In embodiments of the present invention, the project template to be developed may include two types. Namely, the project template to be developed can be a project template stored in the component ecosystem and can also be a project frame template installed by the component ecological scaffold. The project template stored in the component ecosystem can be a project developed by a project development user by using the component ecosystem, and the project development user can continue to develop the project on the basis of the developed project. Thus, the project templates stored in the component ecosystem can be projects that have not yet been developed or projects that have already been developed. The project framework template can be a basic framework of project development provided by the component ecosystem, and project developers can develop various types of projects by using the project framework template.

In the embodiment of the invention, the component ecosystem can support a project development user to develop the component, publish the component and manage the component, and can also support the project development user to install the component stored in the component ecosystem in a developed project. Specifically, a project development user can trigger a project development instruction of the component ecosystem, and determine a to-be-developed project template of the to-be-developed project through the component ecosystem. Optionally, the project development user may specify an existing project template as a to-be-developed project template through the component ecosystem, so as to continue development or perform secondary development on the basis of the existing project. The project development user can also install project frame templates as project templates to be developed through a component ecological scaffold of the component ecosystem so as to develop brand new projects according to the project frame templates. When a project development user installs a project frame template as a project template to be developed through a component ecological scaffold of a component ecosystem, various parameters can be configured for the project frame template, so that the type, the function and the like of the project to be developed are determined. After the parameter configuration is completed, the project development user can acquire the required components from the component ecosystem and install the components in the project to be developed.

And S350, receiving a target component retrieval instruction sent by the project development user, and retrieving the matched target component for the project development user according to a target component retrieval statement input by the project development user in a component retrieval area.

Wherein the target component retrieval instructions are for a component retrieved from the component ecosystem. The component retrieval area can be the component ecosystem's entry to a user search component provided by the project development user. The target component search statement may be a search statement input by the project development user in the component search area, and may be used to search for a desired component. The target component, i.e., the component that the project development user needs to install into the project to be developed.

The component ecosystem provides component retrieval functionality specifically for project development users. A project development user can input target component retrieval statements in a component retrieval area of the component ecosystem so as to retrieve components stored in the component ecosystem, and therefore a suitable target component can be obtained. Optionally, all approved components in the component ecosystem can be retrieved and used.

In an optional embodiment of the present invention, the retrieving, by the project development user, the matched target component according to the target component retrieval statement input by the project development user in the component retrieval area may include: performing word segmentation processing on the target component retrieval statement; extracting a second preset number of search keywords according to the word segmentation result; and searching and matching all the components stored in the system according to the retrieval key words to obtain the target component.

The second preset number may be a value set according to actual requirements, such as 5, 10, or 20, and the embodiment of the present invention does not limit this.

Specifically, after the component ecosystem receives the target component search statement, in order to clarify the search requirement of the project development user, word segmentation processing may be performed on the target component search statement, and a second preset number of search keywords may be extracted according to the word segmentation result. For example, nonsense words such as auxiliary words or interval symbols in the word segmentation result may be filtered, and the remaining segmented words may be used as search keywords. Correspondingly, after the retrieval keywords are obtained, all components stored in the component ecosystem can be searched and matched according to the retrieval keywords, and the target components meeting the project development requirements of project development users are obtained.

Optionally, in the embodiment of the present invention, the process of performing word segmentation on the target component search statement, extracting the search keyword, and searching for a matching target component according to the search keyword may be completed based on an Artificial Intelligence (AI) technology, and related data related to the above operation is mainly obtained and processed by the AI technology. The artificial intelligence is a theory, a method, a technology and an application system which simulate, extend and expand human intelligence by using a digital computer or a machine controlled by the digital computer, sense the environment, acquire knowledge and obtain the best result by using the knowledge.

The artificial intelligence infrastructure generally includes technologies such as sensors, dedicated artificial intelligence chips, cloud computing, distributed storage, big data processing technologies, operation/interaction systems, mechatronics, and the like. The artificial intelligence software technology mainly comprises a computer vision technology, a robot technology, a biological recognition technology, a voice processing technology, a natural language processing technology, machine learning/deep learning and the like.

In an optional embodiment of the present invention, after the extracting a second preset number of search keywords according to the word segmentation result, the method may further include: determining matched retrieval weight for each retrieval keyword according to the sequence of the retrieval keywords; constructing a retrieval keyword vector according to the retrieval keyword and the retrieval weight; the searching and matching of all the components stored in the system according to the retrieval keywords comprises the following steps: and searching and matching all the components stored in the system according to the retrieval keyword vector by adopting a cosine similarity algorithm.

The retrieval weight may be a weight of each retrieval keyword, and is used to represent an importance degree of the retrieval keyword. The search keyword vector may be a vector constructed from search keywords and corresponding search weights.

In order to improve the accuracy of component retrieval and quickly retrieve required components for project development users, after the component ecosystem extracts retrieval keywords according to target component retrieval statements, the component ecosystem can determine matched retrieval weights for the retrieval keywords according to the sequence of the retrieval keywords. It can be understood that the more advanced the sequence of searching keywords, the more in line with the search requirements of the project development user. Therefore, the higher the search weight corresponding to the search keyword in the top order can be. Correspondingly, after determining that each retrieval keyword determines the matched retrieval weight, the component ecosystem can further construct a retrieval keyword vector according to the retrieval keywords and the retrieval weight so as to search and match all components stored in the system according to the constructed retrieval keyword vector.

In a specific example, assume that the search keywords are e1, e2, and e3, respectively, and the weights of the search keywords are w1, w2, and w3, respectively. Alternatively, the value of w1 may be greater than w2, the value of w2 may be greater than w3, and the sum of w1, w2, and w3 may be 1. Accordingly, the search keyword vector constructed according to the search keywords and the search weights may be { (e1, w1), (e2, w2), (e3, w3) }.

Optionally, when the assembly is readyAfter the state system obtains the retrieval keyword vector, the state system can further search and match all the components stored in the built ecological system according to the retrieval keyword vector by adopting a cosine similarity algorithm so as to determine the component which is most matched with the component retrieval requirement of the project development user. The cosine similarity algorithm may calculate the similarity of the component stored in the component ecosystem to the search keyword vector based on the search keyword vector. In a specific example, assume that the search keyword vector is { (e1, w1), (e2, w2), (e3, w3) }, and the component vector is: { (z1,1), (z2,1), (z3,1) … }, wherein z1, z2, z3 represent the individual components of the component ecosystem store. Then, the cosine similarity between the first search keyword and the first component calculated by using a cosine similarity algorithm may be:

by analogy, the cosine similarity between each search keyword and each component can be calculated. It will be appreciated that a higher cosine similarity indicates that the component approximately matches the search keyword.

In an optional embodiment of the present invention, after the performing search matching on all components stored in the system according to the search keyword vector by using a cosine similarity algorithm, the method may further include: sequentially screening a third preset number of candidate target assemblies from the preliminary retrieval result of the target assemblies according to the sequence of similarity from high to low, and determining assembly statistical information of the candidate target assemblies; wherein the component statistical information comprises the praise amount of the component and/or the installation amount of the component; and sequencing each candidate target component according to the component statistical information, and feeding back a sequencing result of the candidate target components to the project development user so that the project development user selects the target component according to the sequencing result of the candidate target components.

The target component preliminary retrieval result may be a result obtained by the component ecosystem performing preliminary retrieval on the component according to the target component retrieval statement, and may include a plurality of matched components. The candidate target component may be a component obtained by further screening the preliminary search result of the target component, and the third preset number may be set according to an actual requirement, such as 5 or 10, which is not limited in the embodiment of the present invention. The component statistical information may be related statistical information of the candidate target component, may be usage information of the component, such as an installation amount of the component, or may be feedback information of the component, such as a praise amount and a goodness amount of the component.

The component ecosystem can adopt a cosine similarity algorithm to calculate the similarity between each component and the retrieval keyword vector, so that a certain number of components can be screened out according to the similarity to serve as the preliminary retrieval result of the target component. For example, the component ecosystem can screen out components with similarity exceeding a certain threshold value to form a preliminary retrieval result of the target component. After obtaining the preliminary retrieval result of the target components, the component ecosystem may sequentially select a third preset number of candidate target components from the preliminary retrieval result of the target components in the order from high similarity to low similarity, so as to further select several candidate target components that most match the retrieval requirements of the project development user components. For example, the component ecosystem may select m components with the highest similarity in the preliminary search results of the target components as the candidate target components in the order of the similarity from high to low.

Correspondingly, after the component ecosystem screens the candidate target components which are most matched with the component retrieval requirements of the project development user, in order to further enrich the component retrieval function, the component ecosystem can also determine component statistical information such as the approval quantity and/or the installation quantity of the candidate target components of the third preset number which are sequentially screened from high to low in similarity, sort the candidate target components again according to the component statistical information such as the approval quantity and/or the installation quantity, and feed back the sorting results of the candidate target components to the project development user. It can be appreciated that a higher approval or installation indicates a better use of the alternative target component. Therefore, the alternative target components can be sorted in the order of the approval amount and/or the installation amount from large to small. Accordingly, the project development user can select the target component required by the project development user by referring to the praise amount and/or the installation amount of each candidate target component.

In an optional embodiment of the present invention, after the sorting the candidate target components according to the component statistical information, the method may further include: acquiring component screening conditions input by the project development user on the alternative target components; wherein the component filtering condition comprises a condition filtered according to component refreshing time and/or a condition filtered according to component updating frequency; and screening the sorted candidate target components according to the component screening conditions.

Wherein, the component screening condition can be a condition for further screening the candidate target components. Optionally, the component screening condition may screen the candidate target component according to the component refresh time, or may also screen the candidate target component according to the component update frequency, which is not limited in the embodiment of the present invention.

It is to be appreciated that components stored in the component ecosystem may experience long term non-update conditions, which generally indicate poor availability of the component. Therefore, the availability of the obtained alternative target components cannot be guaranteed only by sorting the alternative target components according to the approval quantity and/or the installation quantity of the components. Therefore, after the component ecosystem sorts the candidate target components according to the component statistical information, the project development user can set component screening conditions for the candidate target components. For example, the project development user may select the component refresh time of the last three months, the last half year, or the last year to screen the candidate target components, or may also screen each candidate target component according to the component update frequency, and only reserve the candidate target component with the higher component update frequency. Accordingly, the project development user may select a target component with reference to the component refresh time and/or component update frequency of the candidate target component.

According to the technical scheme, the similarity between each component and the target component retrieval statement input by the project development user in the component retrieval area is calculated through the component ecosystem, and the accuracy of the retrieved component can be determined. Meanwhile, the retrieved high-similarity components are sorted according to the praise amount and/or the installation amount, and the alternative target components are further screened according to the screening conditions of the project development users, so that the requirements of the project development users on various retrieval of the components can be met, the efficiency and the accuracy of component retrieval are improved, and the project development users are assisted to quickly retrieve and position the required components.

And S360, responding to a target component installation instruction triggered by the project development user, and installing the target component in the project template to be developed.

Wherein the target component installation instruction may be an instruction indicating that the target component is installed in the project template to be developed.

Correspondingly, after a project development user retrieves a target component through the component ecosystem, a target component installation instruction of the component ecosystem can be triggered, and the retrieved target component is installed in a project template to be developed. Optionally, the target components can be uniformly installed in a public directory file in the project template to be developed.

In an optional embodiment of the present invention, the installing the target component in the to-be-developed project template may include: acquiring a source code of the target component, and installing the target component in the project template to be developed according to the source code; or, in response to a component installation instruction triggered by the project development user, installing the target component in the to-be-developed project template.

The component installation instruction can be an instruction triggered by a project development user by using a component ecosystem, and can be used for instructing the component ecosystem to install the target component in the project template to be developed.

In embodiments of the present invention, the component ecosystem can provide two ways to install target components in a project template to be developed. Specifically, the project development user can directly copy the source code of the target component, i.e., import the source code of the target component into the component ecosystem. Accordingly, the component ecosystem can directly run the source code of the target component to install the target component in the project template to be developed. Alternatively, the project development user may also directly trigger the component installation instruction, such as installing the target component into the project template to be developed through the component ecological scaffold. In addition, the project development user can uninstall the installed components from the project template to be developed, such as uninstalling the target components from the project template to be developed through a component ecological scaffold.

By adopting the technical scheme, the component is searched and installed in the project to be developed by utilizing the component ecosystem, the management function of the component ecosystem on the component is enriched, developers are helped to quickly acquire the required component, the component searching accuracy can be ensured, and therefore the project development efficiency and the development quality are improved.

It should be noted that any permutation and combination between the technical features in the above embodiments also belong to the scope of the present invention.

Example four

Fig. 4 is a schematic diagram of a component management apparatus according to a fourth embodiment of the present invention, where the component management apparatus may configure and implement a component ecosystem, as shown in fig. 4, the apparatus includes: the component development module 410, the component packaging upload module 420, and the packaging component audit storage module 430, wherein:

the component development module 410 is used for responding to a component development instruction triggered by a component development user and developing components according to a preset component development template; wherein the type of the component comprises at least one of a newly built component or a secondarily developed component;

the component packaging and uploading module 420 is configured to respond to a packaging component instruction and a packaging component uploading instruction triggered by the component development user, package the developed components to form packaging components, and upload the packaging components to a component to-be-checked cache region of the component ecosystem;

and the package component audit storage module 430 is configured to audit the package components in the buffer to be audited for the component, and store the package components in a component developer warehouse of the component development user when the package components are determined to pass the audit.

Optionally, the component management apparatus may further include: the system login information acquisition module is used for acquiring system login information of the component development user for logging in the component ecosystem; the component developer warehouse creating module is used for creating a component developer warehouse matched with the component development user according to the system login information of the component development user; wherein the component developer repository is to maintain component information developed by the component development user; and the component development template installation module is used for responding to a component ecological scaffold starting instruction triggered by the component development user and installing the component development template through the component ecological scaffold.

Optionally, the component development module 410 is specifically configured to: determining parameters to be configured of the component development template, and performing parameter configuration on the parameters to be configured to generate the newly-built component; and/or installing the existing component through the component development template, and modifying the component parameters of the existing component to generate the secondary development component.

Optionally, the package component audit storage module 430 is specifically configured to: performing security vulnerability scanning and attack scanning on the packaging component; under the condition that the scanning is determined to be successful, the packaging assemblies are sent to a first preset number of examination and approval personnel, and examination and approval results of the set number of examination and approval personnel are accepted; determining that the packaging assembly passes the examination and approval under the condition that all the examination and approval results are determined to pass the examination and approval; and under the condition that the scanning fails or the approval result comprises that the approval is failed, determining that the packaged component is not approved, and sending component approval failure information to the component development user.

Optionally, the component management apparatus may further include: the to-be-developed project template determining module is used for responding to a project development instruction triggered by a project development user and determining a to-be-developed project template of a to-be-developed project; the project templates to be developed comprise project templates stored in a system and project frame templates installed on component ecological scaffolds; the target component retrieval module is used for receiving a target component retrieval instruction sent by the project development user and retrieving a matched target component for the project development user according to a target component retrieval statement input by the project development user in a component retrieval area; and the target component installation module is used for responding to a target component installation instruction triggered by the project development user and installing the target component in the project template to be developed.

Optionally, the target component retrieving module is specifically configured to: performing word segmentation processing on the target component retrieval statement; extracting a second preset number of search keywords according to the word segmentation result; and searching and matching all the components stored in the system according to the retrieval key words to obtain the target component.

Optionally, the target component retrieving module is specifically configured to: determining matched retrieval weight for each retrieval keyword according to the sequence of the retrieval keywords; constructing a retrieval keyword vector according to the retrieval keyword and the retrieval weight; and searching and matching all the components stored in the system according to the retrieval keyword vector by adopting a cosine similarity algorithm.

Optionally, the target component retrieving module is specifically configured to: obtaining a preliminary retrieval result of the target component; sequentially screening a third preset number of alternative target assemblies from the preliminary retrieval result of the target assemblies according to the sequence of similarity from high to low; determining component statistics for the candidate target component; wherein the component statistical information comprises the praise amount of the component and/or the installation amount of the component; and sequencing each candidate target component according to the component statistical information, and feeding back a sequencing result of the candidate target components to the project development user so that the project development user selects the target component according to the sequencing result of the candidate target components.

Optionally, the target component retrieving module is specifically configured to: acquiring component screening conditions input by the project development user on the alternative target components; wherein the component filtering condition comprises a condition filtered according to component refreshing time and/or a condition filtered according to component updating frequency; and screening the sorted candidate target components according to the component screening conditions.

Optionally, the target component installation module is specifically configured to obtain a source code of the target component, and install the target component in the to-be-developed project template according to the source code; or, in response to a component installation instruction triggered by the project development user, installing the target component in the to-be-developed project template.

The component management device can execute the component management method provided by any embodiment of the invention, and has corresponding functional modules and beneficial effects of the execution method. For details of the technique not described in detail in this embodiment, reference may be made to the component management method provided in any embodiment of the present invention.

Since the component management apparatus described above is an apparatus capable of executing the component management method in the embodiment of the present invention, based on the component management method described in the embodiment of the present invention, a person skilled in the art can understand a specific implementation manner of the component management apparatus in the embodiment of the present invention and various variations thereof, and therefore, how the component management apparatus implements the component management method in the embodiment of the present invention is not described in detail herein. The device used by those skilled in the art to implement the component management method in the embodiments of the present invention is within the scope of the present application.

EXAMPLE five

Fig. 5 is a schematic structural diagram of a computer device according to a fourth embodiment of the present invention. FIG. 5 illustrates a block diagram of an exemplary computer device 12 suitable for use in implementing embodiments of the present invention. The computer device 12 shown in FIG. 5 is only an example and should not bring any limitations to the functionality or scope of use of embodiments of the present invention.

As shown in FIG. 5, computer device 12 is in the form of a general purpose computing device. The components of computer device 12 may include, but are not limited to: one or more processors 16, a memory 28, and a bus 18 that connects the various system components (including the memory 28 and the processors 16).

Bus 18 represents one or more of any of several types of bus structures, including a memory bus or memory controller, a peripheral bus, an accelerated graphics port, and a processor or local bus using any of a variety of bus architectures. By way of example, such architectures include, but are not limited to, an Industry Standard Architecture (ISA) bus, a Micro Channel Architecture (MCA) bus, an enhanced ISA bus, a Video Electronics Standards Association (VESA) local bus, and a Peripheral Component Interconnect (PCI) bus.

Computer device 12 typically includes a variety of computer system readable media. Such media may be any available media that is accessible by computer device 12 and includes both volatile and nonvolatile media, removable and non-removable media.

Memory 28 may include computer system readable media in the form of volatile Memory, such as Random Access Memory (RAM) 30 and/or cache Memory 32. Computer device 12 may further include other removable/non-removable, volatile/nonvolatile computer system storage media. By way of example only, storage system 34 may be used to read from and write to non-removable, nonvolatile magnetic media (not shown in FIG. 5, and commonly referred to as a "hard drive"). Although not shown in FIG. 5, a magnetic disk drive for reading from and writing to a removable, nonvolatile magnetic disk (e.g., a "floppy disk") and an optical disk drive for reading from or writing to a removable, nonvolatile optical disk (e.g., a Compact disk-Read Only Memory (CD-ROM), a Digital Video disk (DVD-ROM), or other optical media) may be provided. In these cases, each drive may be connected to bus 18 by one or more data media interfaces. Memory 28 may include at least one program product having a set (e.g., at least one) of program modules that are configured to carry out the functions of embodiments of the invention.

A program/utility 40 having a set (at least one) of program modules 42 may be stored, for example, in memory 28, such program modules 42 including, but not limited to, an operating system, one or more application programs, other program modules, and program data, each of which examples or some combination thereof may comprise an implementation of a network environment. Program modules 42 generally carry out the functions and/or methodologies of the described embodiments of the invention.

Computer device 12 may also communicate with one or more external devices 14 (e.g., keyboard, pointing device, display 24, etc.), with one or more devices that enable a user to interact with computer device 12, and/or with any devices (e.g., network card, modem, etc.) that enable computer device 12 to communicate with one or more other computing devices. Such communication may be through an Input/Output (I/O) interface 22. Moreover, computer device 12 may also communicate with one or more networks (e.g., a Local Area Network (LAN), Wide Area Network (WAN)) and/or a public Network (e.g., the Internet) via Network adapter 20. As shown, network adapter 20 communicates with the other modules of computer device 12 via bus 18. It should be appreciated that although not shown in FIG. 5, other hardware and/or software modules may be used in conjunction with computer device 12, including but not limited to: microcode, device drivers, Redundant processing units, external disk drive Arrays, (Redundant Arrays of Independent Disks, RAID) systems, tape drives, and data backup storage systems, to name a few.

The processor 16 executes various functional applications and data processing by executing programs stored in the memory 28, thereby implementing the component management method provided by the embodiment of the present invention: developing the component according to a preset component development template in response to a component development instruction triggered by a component development user; wherein the type of the component comprises at least one of a newly built component or a secondarily developed component; responding to a packaging component instruction and a packaging component uploading instruction triggered by the component development user, packaging the developed components to form a packaging component, and uploading the packaging component to a component to-be-audited cache region of the component ecosystem; and auditing the packaged components in the cache region to be audited of the components, and storing the packaged components in a component developer warehouse of the component development user under the condition that the packaged components are determined to pass the auditing.

EXAMPLE six

An embodiment of the present invention further provides a computer storage medium storing a computer program, where the computer program is used to execute the component management method according to any one of the above embodiments of the present invention when executed by a computer processor: developing the component according to a preset component development template in response to a component development instruction triggered by a component development user; wherein the type of the component comprises at least one of a newly built component or a secondarily developed component; responding to a packaging component instruction and a packaging component uploading instruction triggered by the component development user, packaging the developed components to form a packaging component, and uploading the packaging component to a component to-be-audited cache region of the component ecosystem; and auditing the packaged components in the cache region to be audited of the components, and storing the packaged components in a component developer warehouse of the component development user under the condition that the packaged components are determined to pass the auditing.

Computer storage media for embodiments of the invention may employ any combination of one or more computer-readable media. The computer readable medium may be a computer readable signal medium or a computer readable storage medium. A computer readable storage medium may be, for example, but not limited to, an electronic, magnetic, optical, electromagnetic, infrared, or semiconductor system, apparatus, or device, or any combination of the foregoing. More specific examples (a non-exhaustive list) of the computer readable storage medium would include the following: an electrical connection having one or more wires, a portable computer diskette, a hard disk, a Random Access Memory (RAM), a Read-Only Memory (ROM), an Erasable Programmable Read-Only Memory (EPROM) or flash Memory), an optical fiber, a portable compact disc Read-Only Memory (CD-ROM), an optical storage device, a magnetic storage device, or any suitable combination of the foregoing. In the context of this document, a computer readable storage medium may be any tangible medium that can contain, or store a program for use by or in connection with an instruction execution system, apparatus, or device.

A computer readable signal medium may include a propagated data signal with computer readable program code embodied therein, for example, in baseband or as part of a carrier wave. Such a propagated data signal may take many forms, including, but not limited to, electro-magnetic, optical, or any suitable combination thereof. A computer readable signal medium may also be any computer readable medium that is not a computer readable storage medium and that can communicate, propagate, or transport a program for use by or in connection with an instruction execution system, apparatus, or device.

Program code embodied on a computer readable medium may be transmitted using any appropriate medium, including but not limited to wireless, wireline, optical fiber cable, Radio Frequency (RF), etc., or any suitable combination of the foregoing.

Computer program code for carrying out operations for aspects of the present invention may be written in any combination of one or more programming languages, including an object oriented programming language such as Java, Smalltalk, C + + or the like and conventional procedural programming languages, such as the "C" programming language or similar programming languages. The program code may execute entirely on the user's computer, partly on the user's computer, as a stand-alone software package, partly on the user's computer and partly on a remote computer or entirely on the remote computer or server. In the case of a remote computer, the remote computer may be connected to the user's computer through any type of network, including a Local Area Network (LAN) or a Wide Area Network (WAN), or the connection may be made to an external computer (for example, through the Internet using an Internet service provider).

It is to be noted that the foregoing is only illustrative of the preferred embodiments of the present invention and the technical principles employed. It will be understood by those skilled in the art that the present invention is not limited to the particular embodiments described herein, but is capable of various obvious changes, rearrangements and substitutions as will now become apparent to those skilled in the art without departing from the scope of the invention. Therefore, although the present invention has been described in greater detail by the above embodiments, the present invention is not limited to the above embodiments, and may include other equivalent embodiments without departing from the spirit of the present invention, and the scope of the present invention is determined by the scope of the appended claims.

Claims

1. A component management method is applied to a component ecosystem, and comprises the following steps:

2. The component management method according to claim 1, further comprising, before the developing a component according to a preset component development template:

acquiring system login information of the component development user login component ecosystem;

creating a component developer warehouse matched with the component development user according to the system login information of the component development user; wherein the component developer repository is to maintain component information developed by the component development user;

and in response to a component ecological scaffold starting instruction triggered by the component development user, installing the component development template through the component ecological scaffold.

3. The component management method according to claim 1, wherein the developing a component according to a preset component development template includes:

determining parameters to be configured of the component development template, and performing parameter configuration on the parameters to be configured to generate the newly-built component; and/or

And installing the existing component through the component development template, and modifying component parameters of the existing component to generate the secondary development component.

4. The component management method according to claim 1, wherein the verifying the packaged component uploaded by the component development user in the buffer to be verified of the component comprises:

performing security vulnerability scanning and attack scanning on the packaging component;

under the condition that the scanning is determined to be successful, the packaging assemblies are sent to a first preset number of examination and approval personnel, and examination and approval results of the set number of examination and approval personnel are accepted;

determining that the packaging assembly passes the examination and approval under the condition that all the examination and approval results are determined to pass the examination and approval;

and under the condition that the scanning fails or the approval result comprises that the approval is failed, determining that the packaged component is not approved, and sending component approval failure information to the component development user.

5. The component management method according to claim 1, further comprising, after storing the packaged component uploaded by the component development user in a component developer repository of the component development user:

determining a to-be-developed project template of a to-be-developed project in response to a project development instruction triggered by a project development user; the project templates to be developed comprise project templates stored in a system and project frame templates installed on component ecological scaffolds;

receiving a target component retrieval instruction sent by the project development user, and retrieving a matched target component for the project development user according to a target component retrieval statement input by the project development user in a component retrieval area;

and in response to a target component installation instruction triggered by the project development user, installing the target component in the project template to be developed.

6. The component management method according to claim 5, wherein the retrieving the matched target component for the project development user according to the target component retrieval statement input by the project development user in the component retrieval area comprises:

performing word segmentation processing on the target component retrieval statement;

extracting a second preset number of search keywords according to the word segmentation result;

and searching and matching all the components stored in the system according to the retrieval key words to obtain the target component.

7. The component management method according to claim 6, further comprising, after the extracting a second preset number of search keywords according to the segmentation result:

determining matched retrieval weight for each retrieval keyword according to the sequence of the retrieval keywords;

constructing a retrieval keyword vector according to the retrieval keyword and the retrieval weight;

the searching and matching of all the components stored in the system according to the retrieval keywords comprises the following steps:

and searching and matching all the components stored in the system according to the retrieval keyword vector by adopting a cosine similarity algorithm.

8. The component management method according to claim 7, further comprising, after the search matching is performed on all components stored in the system according to the search keyword vector by using a cosine similarity algorithm, the following steps:

obtaining a preliminary retrieval result of the target component;

sequentially screening a third preset number of alternative target assemblies from the preliminary retrieval result of the target assemblies according to the sequence of similarity from high to low;

determining component statistics for the candidate target component; wherein the component statistical information comprises the praise amount of the component and/or the installation amount of the component;

and sequencing each candidate target component according to the component statistical information, and feeding back a sequencing result of the candidate target components to the project development user so that the project development user selects the target component according to the sequencing result of the candidate target components.

9. The component management method according to claim 8, further comprising, after the sorting each of the candidate target components according to the component statistics,:

acquiring component screening conditions input by the project development user on the alternative target components; wherein the component filtering condition comprises a condition filtered according to component refreshing time and/or a condition filtered according to component updating frequency;

and screening the sorted candidate target components according to the component screening conditions.

10. The component management method according to claim 5, wherein the installing the target component in the to-be-developed project template comprises:

acquiring a source code of the target component, and installing the target component in the project template to be developed according to the source code; or

And in response to a component installation instruction triggered by the project development user, installing the target component in the to-be-developed project template.

11. A component management apparatus, configured in a component ecosystem, comprising:

12. A computer device, characterized in that the computer device comprises:

one or more processors;

storage means for storing one or more computer programs;

the component management method according to any of claims 1-10, when the one or more computer programs are executed by the one or more processors such that the one or more processors execute the computer programs.

13. A computer storage medium on which a computer program is stored, which computer program, when being executed by a processor, carries out the component management method according to any one of claims 1 to 10.