What Data Belongs to This Category
This category’s data is generated around rights notices and compliance documents for open source projects. Data sources include code repository root directory files, third-party dependency lists, official license texts, and code contribution records. Regularly produced standard documents include four types: LICENSE files, NOTICE files, dependency license lists, and copyright notices. Data is updated each time a version is released or a dependency package is changed. Document fields include full license type names, copyright holder information, dependency package names and version numbers, and contributor attribution lists. No additional custom statistical fields are included.
Constraints Imposed on Tool Calling and Plugins
Data sources for this category are scattered, covering multiple channels such as code repositories, dependency lists, and license texts. Tool calling and plugins must connect to multiple types of data sources to pull required information. Data update frequency adjusts dynamically based on version or dependency changes. Plugins must bind to code commit and dependency package update events to trigger execution. Standard document structures are fixed. Plugins must strictly match preset fields when generating compliance files to avoid format deviations. Compliance check errors can block commercial use. Plugins must add a pre-check step to alert promptly for abnormal data.
Configuration Settings
| Configuration Item | Recommended Setting | Rationale |
|---|---|---|
toolChoice | auto | Adapts to FastGPT v4.17.0 plugin calling logic, automatically matches compliance check tools |
functionCall | Enabled | Triggers the automatic license compliance and copyright notice verification workflow |
| Data Pull Timeout Threshold | 30 seconds | Prevents task timeout and interruption due to slow external data source loading |
| Single Dependency Pull Limit | First 15 dependencies | Balances verification efficiency and coverage, avoids excessive system resource usage per call |
| Trigger Event Binding | Code commit, dependency change | Matches data update rhythm, executes verification only when data changes |
Three Common Configuration Mistakes
- Scenario: Plugin execution returns status code 400, with the
errorfield displaying "invalid parameter format". The cause is failure to format thetoolChoiceparameter value per FastGPT v4.17.0 requirements, preventing the plugin from correctly triggering compliance verification. - Scenario: The plugin fails to read LICENSE files, resulting in missing license statements in generated compliance documents. The cause is failure to point plugin configuration to the standard file path in the code repository root directory, only reading files from custom subdirectories.
- Scenario: Compliance verification is not triggered after a dependency change, resulting in generated dependency license lists missing compliance information for new dependencies. The cause is failure to bind dependency change events as plugin trigger conditions, only configuring scheduled pull tasks.
How to Verify Correct Configuration
- Submit a code change that includes new dependencies, then check plugin execution logs in the FastGPT workflow to confirm
functionCallis triggered normally. - Access the plugin configuration page, verify that the
toolChoiceparameter value is set toautoto ensure correct calling logic. - Manually pull the project’s LICENSE and NOTICE files, compare them against output generated by the plugin to confirm matching fields.
- Simulate a dependency package change operation, check if the generated dependency license list includes compliance information for new dependencies.
The values provided here are common starting points, and should be evaluated against the reader’s own samples.
Question material comes from public community discussions. Configuration values are common starting points and should be measured against your own samples. Verified on 2026-10-19.