Disclaimer & Assessment Methodology
This score was produced via LLM-assisted assessment of the repository structure and the supplied evidence bundle. These findings should be treated as a directional pilot signal rather than a verified rating. For more details on our pilot objectives and the development path toward rules-based human review, see the Development Roadmap. Raw files are accessible at the assessment report source.
InVEST Assessment
"Integrated Valuation of Ecosystem Services and Tradeoffs (InVEST) models map and value the goods and services from nature that sustain and fulfill human life."
InVEST shows a strong open-traceability profile as an open-source ecosystem-services modeling platform: official pages link users from downloads and sample datasets to public GitHub repositories, open dependencies, installation instructions, release notes, user-guide documentation, issue tracking, and a community forum. The strongest dimensions are open software, publications, and community review: the toolset and dependencies are public and version-controlled, the user guide documents models, data needs, limitations, interpretation, references, and citation/DOI information, and users can inspect active support and issue channels. The weaker dimensions are input-data provenance, exact execution reproducibility, and cross-artifact linkage: the evidence does not demonstrate dataset-level metadata, uncertainty, measurement provenance, licenses, or an exact reproducible run that binds particular input files, parameters, code commit, environment, outputs, and review records. Overall, the evidence supports a high-level open evidence chain for the InVEST toolset, but not a fully machine-verifiable provenance chain for each environmental output produced with it.
Claim Traceability Pathway
Inspection trail mapping the connections from raw inputs to the published claim.
Traceability Health Summary
Scan diagnosis of where the evidence chain stands and what requires attention first.
Open Publications and Communication
This stage provides solid evidence, making calculations and documentation highly inspectable and reusable for external actors.
Open Input Data and Measurement Evidence
This is the weakest segment of the evidence chain. Gaps in records or lack of linkage break the evidence chain here.
- Unique dataset DOIs & licenses
- Execution run configs & workflow logs
- Dynamic provenance graph mapping
Strengthen Open Input Data and Measurement Evidence
Register raw dataset bundles with persistent repositories (e.g. Zenodo) and define licensing metadata.
Evidence Linkage Summary
Open Linkage is not a standalone category; it is the connectivity of the evidence chain. Below is the connection status of the connection links between each step in this project's journey.
Are data input paths and schemas programmatically defined inside the code files or configurations?
Is code execution managed through versioned workflow scripts (e.g. Snakemake pipelines) rather than manual scripts?
Are execution outputs and logs tested automatically (CI/CD) and verified inside public pull request reviews?
Are peer reviews, community issues, and discussions linked directly to published methodology reports?
Does the final published paper cite the exact dataset identifiers, model hashes, and run logs that produced the results?
The overall evidence chain is visible but not fully explicit at run level. A plausible chain can be inspected from official sample data and data-source guidance, to the open InVEST repository and open dependencies, to installation/CI/release information, to public issues/forums, and finally to the user guide and release communications. There are also useful version anchors: InVEST 3.20.0 downloads, sample datasets for 3.20.0, a suggested citation/DOI for 3.20.0, and a release linked to commit fca8bf5. However, Open Linkage requires explicit, specific, versioned, externally verifiable connections between claims and exact datasets, code versions, model configurations, workflow runs, review records, and publications. The supplied evidence does not show a single machine-readable provenance record or manifest in the project repository that binds a specific environmental output to exact input files, parameters, code commit, dependency versions, CI/workflow run, expected outputs, and review discussion. The score is not lower because the official pages and repositories cross-reference enough artifacts to reconstruct a high-level traceability chain; it is not higher because the most important exact claim-to-evidence links remain implicit or analysis-dependent.
Detailed Dimension Inspection
Granular findings for each processing step in the Open Traceability framework.
Open Input Data and Measurement Evidence
Evidence Found
InVEST has moderate public input-data traceability for a general-purpose ecosystem-services modeling tool: the evidence identifies official sample datasets for every model and an official downloads/data-sources page that links users to sample datasets, a Natural Capital Alliance Data Hub, parameter-value and nutrient/sediment databases, and user-guide data guidance. This is enough to show that expected inputs are identifiable and that example data are available for reuse in at least some form. The score is not higher because the supplied evidence does not expose the contents of the Bitbucket sample-data repository, dataset-level metadata, licenses, version tags, measurement methods, provenance back to primary observations, uncertainty/quality-control fields, or transformations for all model inputs. Since many InVEST runs use user-supplied spatial datasets, traceability of actual environmental outputs depends heavily on whether a given analysis preserves and documents its own input data. The score is not lower because there is clear official infrastructure for sample inputs and data-source guidance, rather than no public data pathway.
Gaps Identified
No significant gaps identified. This stage is fully documented and verifiable.
"Curator note identifies this as versioned sample input datasets covering every InVEST model."
Relevance: Supports the existence of reusable example inputs across the model suite, but the bundle does not show metadata, licenses, or measurement provenance."The page lists 'Individual Sample Datasets for InVEST 3.20.0' and data-source resources including the Natural Capital Alliance Data Hub, Kc Calculator, Parameter Value Database, Nutrient Database, and Sediment Database."
Relevance: Shows official identification of input-data resources and guidance for users preparing model runs."Model sections include 'Data Needs' and appendices such as 'Data Sources' for multiple models, including Annual Water Yield, Carbon Storage and Sequestration, Coastal Blue Carbon, and others."
Relevance: Provides public documentation of required inputs and data-source guidance, though not full primary-data traceability for every possible analysis.Open-Source Models, Methods, and Software
Evidence Found
The software traceability is strong. The main InVEST repository is public on GitHub and identified as Apache-2.0 licensed; linked dependency repositories such as PyGeoprocessing and TaskGraph are also public, and PyGeoprocessing exposes substantial repository structure including source, tests, documentation, license, pyproject, requirements, setup files, and a README describing its raster, vector, and hydrological operations. Installation documentation lists major runtime dependencies and supported distri
Gaps Identified
bution channels. The score is not higher because the supplied evidence for the main InVEST repository page is mostly GitHub chrome and high-level repository metadata rather than direct inspection of all model source files, model equations, dependency lockfiles, build scripts, and infrastructure front-end code. It is not lower because the evidence clearly establishes open, version-controlled repositories, open-source licensing, public dependencies, and documented installation paths.
"Public GitHub repository described as 'InVEST®: models that map and value the goods and services from nature that sustain and fulfill human life,' with repository metadata showing issues, pull requests, discussions, actions, stars and forks; curator note identifies Apache-2.0 licensing."
Relevance: Primary evidence that the core model toolset is openly hosted in version control under an open-source license."README states PyGeoprocessing is a Python/Cython library providing raster, vector, and hydrological GIS operations and was developed to support InVEST; repository shows source, tests, docs, LICENSE.txt, requirements.txt, pyproject.toml, setup.py, and 4,189 commits."
Relevance: Shows that a major geospatial processing dependency is itself open, documented, version-controlled, and testable."Public GitHub repository under natcap with issues, pull requests, actions, projects, and security/quality tabs; curator note identifies it as the workflow engine used by InVEST models."
Relevance: Supports openness of execution/workflow infrastructure used by the model suite."Documentation states InVEST can be installed from conda-forge, PyPI, or directly from the git source tree, and lists dependencies including GDAL, pandas, numpy, shapely, scipy, pygeoprocessing, taskgraph, geopandas, matplotlib, and others."
Relevance: Provides inspectable software environment and dependency information needed to understand and run the software.Open Execution and Reproducibility
Evidence Found
Execution traceability is strong for reproducing the software environment
Gaps Identified
but weaker for reproducing a specific environmental claim or model output. The evidence includes a GitHub Actions build-and-test workflow, detailed installation instructions for conda-forge, PyPI, source installation, dependencies, CLI/tutorial/container topics, and release artifacts with versioned changes. These materials allow an external actor to install the package and inspect automated testing infrastructure. The score is not higher because the supplied bundle does not show the actual contents or run history of the CI workflow, a pinned computational environment such as a lockfile/container image digest for a particular release, executable notebooks or workflow scripts that run sample data end-to-end, preserved outputs, model parameters, or an exact run record linking specific inputs to specific reported outputs. It is not lower because installation, dependencies, CI, CLI, releases, and sample data create a credible partial path to re-execution.
"Curator note identifies this as a CI workflow that builds and tests InVEST on every change."
Relevance: Shows public automated execution/testing infrastructure, although the bundle does not expose workflow contents or run results."The page documents installation via conda-forge, pip/PyPI, and source from GitHub, explains GDAL requirements, lists dependencies, and includes navigation entries for CLI, batch processing, containers, model entry points, API reference, plugins, and changelog."
Relevance: Supports reproducibility by documenting how an external user can recreate the software environment and run models."Release 3.20.0 is dated 11 Jun, associated with commit fca8bf5, and contains a detailed changelog of model, Workbench, reporting, and bug-fix changes."
Relevance: Provides version anchors that users can use when attempting to reproduce analyses with a specific software release."The official downloads page links to 'Individual Sample Datasets for InVEST 3.20.0'."
Relevance: Sample inputs support practical re-execution, though the evidence does not show full workflows or expected outputs.Open Community and Review
Evidence Found
InVEST has strong visible community and review infrastructure. The main repository has a public issue tracker, pull requests, discussions, actions, projects, and wiki tabs, with 207 issues shown in the evidence. The Natural Capital Alliance community forum is active and includes software-support guidelines, announcements, user questions, model validation questions, bug/error reports, and responses across many InVEST model topics. Releases cite issue numbers for fixes and enhancements, making some correction history visible. The score is not higher because the supplied evidence does not document formal peer-review records for the software or individual model methods, governance decision logs, systematic correction notices, response-time metrics, or how affected communities participate in methodological decisions. It is not lower because users clearly have public channels to report errors, ask scientific/methodological questions, and inspect at least some issue-linked maintenance history.
Gaps Identified
No significant gaps identified. This stage is fully documented and verifiable.
"The repository page shows public Issues, Pull requests, Discussions, Actions, Projects, Wiki, and Security/quality tabs, with 207 issues visible in the repository metadata."
Relevance: Provides an inspectable public channel for bug reports, feature requests, and corrections."Forum homepage describes itself as 'A place for InVEST user support and collaboration' and shows active topics such as software support, model validation, InVEST release announcements, negative SDR outputs, and Workbench crashes, with replies and recent dates."
Relevance: Shows active public user-support and methodological discussion channels beyond GitHub."A pinned topic titled 'Guidelines for posting software support questions' says the team welcomes software support posts and provides guidance for effective error reporting."
Relevance: Indicates an open process for users to raise issues and seek support."The 3.20.0 release notes link changes and fixes to issue or pull-request numbers such as #2471, #2228, #2179, #2532, #2555, #2442, and #2573."
Relevance: Connects public maintenance history to specific tracked changes and corrections.Open Publications and Communication
Evidence Found
Publication and communication traceability is excellent for a software/model suite. The InVEST User Guide is openly accessible and functions as canonical documentation, with suggested citation and DOI for version 3.20.0, contri
Gaps Identified
butor attri
"The guide lists a suggested citation, 'Natural Capital Alliance, 2026. InVEST 3.20.0. https://doi.org/10.60793/natcap-invest-3.20.0,' names contributors, and organizes model documentation into sections including summaries, model descriptions, limitations, data needs, interpretation, appendices, and references."
Relevance: Primary open publication documenting claims, methods, inputs, limitations, and citation context for the toolset."The page provides Workbench downloads for InVEST 3.20.0, GitHub repository link, older/development versions, sample datasets, English/Spanish/Chinese user guides, plugin developer guide, data sources, attribution guidance, and usage-data notice."
Relevance: Central communication hub connecting users to documentation, software, data, attribution, and support resources."The 3.20.0 release notes provide release date, commit identifier fca8bf5, verification status, highlights, and detailed model-specific and Workbench changes."
Relevance: Supports version-aware communication and allows users to understand differences between software versions.Open Linkage
Evidence Found
The overall evidence chain is visible but not fully explicit at run level. A plausible chain can be inspected from official sample data and data-source guidance, to the open InVEST repository and open dependencies, to installation/CI/release information, to public issues/forums, and finally to the user guide and release communications. There are also useful version anchors: InVEST 3.20.0 downloads, sample datasets for 3.20.0, a suggested citation/DOI for 3.20.0, and a release linked to commit fca8bf5.
Gaps Identified
However, Open Linkage requires explicit, specific, versioned, externally verifiable connections between claims and exact datasets, code versions, model configurations, workflow runs, review records, and publications. The supplied evidence does not show a single machine-readable provenance record or manifest in the project repository that binds a specific environmental output to exact input files, parameters, code commit, dependency versions, CI/workflow run, expected outputs, and review discussion. The score is not lower because the official pages and repositories cross-reference enough artifacts to reconstruct a high-level traceability chain; it is not higher because the most important exact claim-to-evidence links remain implicit or analysis-dependent.
"The page combines downloads for InVEST 3.20.0, GitHub repository, older/development versions, sample datasets, user guides, plugin developer guide, data sources, attribution guidance, and usage-data notice."
Relevance: Provides the strongest central linkage across data, software, documentation, and communication artifacts."The guide gives a suggested citation for 'InVEST 3.20.0' with DOI https://doi.org/10.60793/natcap-invest-3.20.0 and documents models, limitations, data needs, interpretation, and references."
Relevance: Links published documentation and citation to a named software version."Release 3.20.0 is linked to commit fca8bf5 and includes detailed change notes with issue references."
Relevance: Links a public software version to a specific code state and maintenance/review artifacts."The page describes installing from conda-forge, PyPI, or directly from GitHub main and lists dependencies including pygeoprocessing and taskgraph."
Relevance: Connects software execution to dependency and environment information, but not to an exact completed analysis run."The forum contains active model-specific support and science/data discussions, while the linked GitHub project has public issues and pull requests."
Relevance: Supplies review/community artifacts in the chain, though not always linked to specific claims or released outputs.Critical Traceability Gaps
Inspection details of where the evidence chain breaks down and what that implies for public trust.
| Identified Gap | Impact on Traceability | Suggested Remediation |
|---|---|---|
| Dataset not linked or versioned | High ‐ Blocks inspection of inputs | Register raw datasets in Zenodo and cite unique DOIs in config files. |
| Workflow run details not archived | Critical ‐ Restricts computational reproducibility | Archive Snakemake workflow runs and publish log files on Zenodo. |
Remediation & Improvements Roadmap
Actionable roadmap prioritized by implementation complexity.
Quick Wins
Low effort, high immediate return.
- Add CITATION.cff file
Enables clear publication-to-repository citation schema.
- Commit top-level LICENSE
Resolves legal terms of software and dataset inspectability.
- Link communication channels
Add status/discord badges to repository README files.
Medium Effort
Standard engineering practices.
- Specify configurations in config files
Provide explicit parameters and dataset configurations in repository.
- Lock computational environments
Lock dependencies using Conda-lock or Docker image digests.
- Archive automated workflow logs
Publish CI test summaries and solver objective check values.
Strategic Upgrades
Highest traceability return.
- Publish workflow runs on Zenodo
Create persistent, immutable archives of the full execution outputs.
- Build claims-to-evidence provenance graphs
Establish a machine-readable map of the end-to-end evidence trail.
Framework Dimension Definitions
- Open Input Data and Measurement Evidence: Identifiable, documented, attributable, versioned raw measurement evidence inputs.
- Open-Source Models, Methods, and Software: Inspectability of Analytical logic via code repositories, configurations, and license files.
- Open Execution and Reproducibility: Computational environments, workflows, run logs, and outputs make rerun processes inspectable.
- Open Community and Review: Scrutiny, peer review, issue tracking, and responses to replication challenges are visible.
- Open Publications and Communication: Resulting reports, papers, and dashboards are openly accessible and reference source materials.
- Open Linkage: The versioned, explicit connectivity linking data, models, execution, review, and publication steps.
Human Review Notes
Human review of this assessment report is pending. An independent reviewer must inspect the repository references to verify the findings.
Target Claim Stated by Namespace
InVEST is an open-source toolset that maps and values ecosystem services (carbon storage, water yield, pollination, coastal protection, and more) to support environmental decision-making, with model outputs intended to be credible and reproducible.https://github.com/natcap/invest
Verified Namespace
Open Input Data and Measurement Evidence
Identifiable, documented, attributable, versioned raw measurement evidence inputs.
Versioned sample input datasets covering every InVEST model.
Official downloads page listing InVEST data sources and guidance.
Open-Source Models, Methods, and Software
Inspectability of Analytical logic via code repositories, configurations, and license files.
Main InVEST toolset source, Apache-2.0 licensed.
PyGeoprocessing — the geospatial processing library InVEST depends on.
TaskGraph — the workflow engine all InVEST models use to organise execution.
Open Execution and Reproducibility
Computational environments, workflows, run logs, and outputs make rerun processes inspectable.
CI workflow that builds and tests InVEST on every change.
Documented, versioned install procedure for reproducing the environment.
Open Community and Review
Scrutiny, peer review, issue tracking, and responses to replication challenges are visible.
Public issue tracker where bugs are reported, discussed, and corrected.
Community forum for user support and model questions.
Open Publications and Communication
Resulting reports, papers, and dashboards are openly accessible and reference source materials.
InVEST User Guide — the canonical documentation of models, methods, and data needs.
Versioned releases with changelogs, tying outputs to specific software versions.
Open Linkage
The versioned, explicit connectivity linking data, models, execution, review, and publication steps.
This Open Traceability manifesto acts as the versioned, machine-readable linkage artifact connecting all stages of the evidence chain.