5de65b8 · 34,317 commits · 4,487 files
Issued 2026-10-23
Reads strong: 4 of 6 rated dimensions are strong, 2 are adequate and none is significant.
102 checks ran across 6 assessable dimensions. Security & Reliability Posture and Observability & Operations are adequate. 8 findings, each with evidence. One dimension cannot be assessed without an acquirer.
This repository reads strong. Show it in your README: the badge links to a page where anyone can check the reading. If you embed it: link it to the report, remove it if the report is delisted, and do not present it as a certification or an endorsement.
[](https://borehole.dev/verify/DR90CYEZTXHZ?via=badge)- 05.61 8 files are named as enterprise-edition code plugins/PassboltEe/Ee/config/bootstrap.php
- 4 findings from checks Borehole's calibration found wrong more often than right are no longer published.
| Dimension | Rating | ||
|---|---|---|---|
| 01 | Architecture & Codebase — including AI provenance | strong | |
| 02 | Engineering Process & SDLC Maturity | strong | |
| 03 | Organization & Key-Person Risk | strong | |
| 04 | Product & Engineering Maturity | strong | |
| 05 | Security & Reliability Posture | adequate | |
| 06 | Observability & Operations | adequate | |
| 07 | Fit with the Acquirer | not assessable |
- 22% of non-merge commits carry any trailer at all
- low trailer coverage: the convention may not be in consistent use
- no widespread author/committer date divergence
Architecture & Codebase — including AI provenance
01 · strong · ratings ↑plugins/PassboltEe/Scim/src/Utility/Resource/UserScimResource.php is 1,145 lines, 13× this codebase's median file
adequateThe median source file here is 82 lines. 3 files exceed 1,000 lines, the largest being 1,145. Size is not a defect on its own — some problems genuinely live in one place — but these are where merge conflicts, review fatigue and single-owner knowledge concentrate, and they are the first thing that slows an inheriting engineer down.
A note that does not affect this rating: measured against its own codebase's median, it is below the 85th percentile of 382 surveyed projects' largest files, where this check begins to count.
| line-count | plugins/PassboltEe/Scim/src/Utility/Resource/UserScimResource.php:1 — 1,145 lines (13× median) |
| line-count | plugins/PassboltEe/DirectorySync/src/Actions/SyncAction.php:1 — 1,009 lines (12× median) |
| line-count | config/Migrations/20170830064410_V162InitialMigration.php:1 — 1,007 lines (12× median) |
Respond to this finding
Your response is published beside the finding, not instead of it. A finding you can argue with is the point — and a wrong one is calibration data we want.
An owner's response is removed only when it is unlawful, impersonates someone, publishes personal data or a credential, or is not about the finding. Disagreeing with the report is never a reason. To report a response, or to reach us about one, write to takedown@borehole.dev.
Engineering Process & SDLC Maturity
02 · strong · ratings ↑No finding. 16 checks ran and none fired; the rejection log below says why each did not.
Organization & Key-Person Risk
03 · strong · ratings ↑No finding. 10 checks ran and none fired; the rejection log below says why each did not.
Product & Engineering Maturity
04 · strong · ratings ↑Effort is shifting from building to rewriting
adequateDeleted lines per line added rose from 0.64 to 1.07 between the first and second halves of this history. Rework is normal and often healthy, but a rising ratio means an increasing share of the team's time is spent replacing code that already exists rather than building what does not. Whether that is deliberate repayment or churn is a question for the team.
A note that does not affect this rating: in Borehole's calibration, this check's notes were usually true but overstated.
| deletions-per-insertion | first half 0.64, second half 1.07 (split 2016-02-01) |
Respond to this finding
Your response is published beside the finding, not instead of it. A finding you can argue with is the point — and a wrong one is calibration data we want.
An owner's response is removed only when it is unlawful, impersonates someone, publishes personal data or a credential, or is not about the finding. Disagreeing with the report is never a reason. To report a response, or to reach us about one, write to takedown@borehole.dev.
32 files still carry code deprecated more than two years ago
adequate32 files were marked deprecated over two years ago and still are, the oldest since Oct 2018. A deprecation is a promise to remove. Ask what still depends on these, and whether removing them is scheduled.
A note that does not affect this rating: in Borehole's calibration, this check's notes were usually true but overstated.
| src/Utility/UserAccessControl.php | src/Utility/UserAccessControl.php — deprecated since Oct 2018 |
| config/bootstrap_plugins.php | config/bootstrap_plugins.php — deprecated since Mar 2019 |
| src/Model/Traits/Groups/GroupsFindersTrait.php | src/Model/Traits/Groups/GroupsFindersTrait.php — deprecated since Sep 2020 |
| src/Controller/Groups/GroupsIndexController.php | src/Controller/Groups/GroupsIndexController.php — deprecated since Sep 2020 |
| src/Controller/Groups/GroupsViewController.php | src/Controller/Groups/GroupsViewController.php — deprecated since Sep 2020 |
Respond to this finding
Your response is published beside the finding, not instead of it. A finding you can argue with is the point — and a wrong one is calibration data we want.
An owner's response is removed only when it is unlawful, impersonates someone, publishes personal data or a credential, or is not about the finding. Disagreeing with the report is never a reason. To report a response, or to reach us about one, write to takedown@borehole.dev.
Security & Reliability Posture
05 · adequate · ratings ↑8 files are named as enterprise-edition code
adequateFiles named `.ee.` are, by the common open-core convention, the paid edition's code, usually under a licence that is not open source even where the rest is. What the buyer may do with each part differs.
| plugins/PassboltEe/Ee/config/bootstrap.php | plugins/PassboltEe/Ee/config/bootstrap.php — enterprise-edition file |
| plugins/PassboltEe/Ee/config/config.php | plugins/PassboltEe/Ee/config/config.php — enterprise-edition file |
| plugins/PassboltEe/Ee/src/EePlugin.php | plugins/PassboltEe/Ee/src/EePlugin.php — enterprise-edition file |
Respond to this finding
Your response is published beside the finding, not instead of it. A finding you can argue with is the point — and a wrong one is calibration data we want.
An owner's response is removed only when it is unlawful, impersonates someone, publishes personal data or a credential, or is not about the finding. Disagreeing with the report is never a reason. To report a response, or to reach us about one, write to takedown@borehole.dev.
34 vendored components with no licence
adequateThird-party code is committed into this repository without any statement of the terms it arrived under. Unknown terms are harder to deal with than inconvenient ones: an awkward licence can be complied with, an absent one cannot. Each of these needs its origin established before the code changes hands.
A note that does not affect this rating: in Borehole's calibration, this check's notes were usually true but overstated.
| webroot/img/third_party/ChromeWebStore.png | webroot/img/third_party/ChromeWebStore.png — 1 tracked files, no licence file |
| webroot/img/third_party/ChromeWebStore_black.png | webroot/img/third_party/ChromeWebStore_black.png — 1 tracked files, no licence file |
| webroot/img/third_party/ChromeWebStore_black.svg | webroot/img/third_party/ChromeWebStore_black.svg — 1 tracked files, no licence file |
| webroot/img/third_party/ChromeWebStore_white.png | webroot/img/third_party/ChromeWebStore_white.png — 1 tracked files, no licence file |
| webroot/img/third_party/ChromeWebStore_white.svg | webroot/img/third_party/ChromeWebStore_white.svg — 1 tracked files, no licence file |
| webroot/img/third_party/FirefoxAMO_black.svg | webroot/img/third_party/FirefoxAMO_black.svg — 1 tracked files, no licence file |
Respond to this finding
Your response is published beside the finding, not instead of it. A finding you can argue with is the point — and a wrong one is calibration data we want.
An owner's response is removed only when it is unlawful, impersonates someone, publishes personal data or a credential, or is not about the finding. Disagreeing with the report is never a reason. To report a response, or to reach us about one, write to takedown@borehole.dev.
1 advisory against this project in the last 24 months
adequateThe newest was published on 2025-03-10. A project that publishes advisories is telling its users about its fixes, and the count and pace say how much security work it carries. Whether 1 of them are fixed in the code you ship could not be told from this history: its version is only known to be at least 5.17.0. Answer lives in: the release you run, set against each fixed version.
A note that does not affect this rating: it describes the project's advisory record, and no advisory in it is known to affect the surveyed commit.
| CVE-2025-27913 | 2025-03-10: CVE-2025-27913 (low): Passbolt API before 5, if the server is misconfigured (with an incorrect installation process and disregarding of Health Check results), can send email messages |
Respond to this finding
Your response is published beside the finding, not instead of it. A finding you can argue with is the point — and a wrong one is calibration data we want.
An owner's response is removed only when it is unlawful, impersonates someone, publishes personal data or a credential, or is not about the finding. Disagreeing with the report is never a reason. To report a response, or to reach us about one, write to takedown@borehole.dev.
Observability & Operations
06 · adequate · ratings ↑No structured logging library is in use
adequateNothing references a structured logging library. Logs that are written to be read by a person are not searchable by a machine, which means incident response here is proportional to how well someone remembers the codebase rather than to what the tooling can find.
| logging-scan | searched 3,690 files for 10 structured logging libraries; 0 matched |
Respond to this finding
Your response is published beside the finding, not instead of it. A finding you can argue with is the point — and a wrong one is calibration data we want.
An owner's response is removed only when it is unlawful, impersonates someone, publishes personal data or a credential, or is not about the finding. Disagreeing with the report is never a reason. To report a response, or to reach us about one, write to takedown@borehole.dev.
No error reporter is wired in
adequateNothing in the service initialises an error reporter (Sentry, Rollbar, Bugsnag, Honeybadger or an APM agent). An exception in production reaches a person only if someone is reading the logs, which usually means a customer reports it first.
A note that does not affect this rating: notes like it are common in well-run projects.
| error reporting | no error reporter initialised |
Respond to this finding
Your response is published beside the finding, not instead of it. A finding you can argue with is the point — and a wrong one is calibration data we want.
An owner's response is removed only when it is unlawful, impersonates someone, publishes personal data or a credential, or is not about the finding. Disagreeing with the report is never a reason. To report a response, or to reach us about one, write to takedown@borehole.dev.
Fit with the Acquirer
07 · not assessable · ratings ↑Not rated: structurally not assessable from a repository. What a person adds here.
Check it on the running system
4 checks against the running system follow from the findings above: what a buyer's engineer will try, how to run it first, and what to have ready. A paid survey of this repository includes them.
A paid survey of a public repository is also reviewed: a language model reads each finding against the code and withdraws only findings it judges the code contradicts, each listed with its reason. The review is a language model's reading of the findings against the code, and it can be wrong. It never adds a finding, never raises a band, and never removes a finding from a proven check or an advisory that affects the surveyed version.
What a person adds
The survey reads what the repository can show. The code cannot settle these questions, and on them this report states nothing. Each says where its answer lives: your own engineer, the company, or an assessor you choose can settle it. Questions marked measured open with something this repository shows.
Architecture & Codebase — including AI provenance
01 · full coverage- measured No architecture or design document is in the tree, across 2,402 product files. Where does the design live, and who holds it?
- Is the architecture right for the next three years of the product?
- Were the home-grown components reasonable choices when they were made, and are they now?
Engineering Process & SDLC Maturity
02 · high coverage- Is review real or a rubber stamp? Comment depth and time to approve need the pull request history.
- Is delivery planned and measured, or heroic?
- How are incidents run, reviewed and learned from?
Organization & Key-Person Risk
03 · partial coverage- measured 506 people have committed here. Which of them are you acquiring, and which are you replacing?
- Who mentors whom, and would that survive a departure?
- Can the team grow, and who stands behind the top three contributors?
- Is the seniority mix sound, and will pay survive your salary bands?
- Is the pace sustainable? Commit times cannot say: git keeps no reliable local time.
- Does the team want to stay after close?
- How are decisions made and disagreements resolved?
Product & Engineering Maturity
04 · minimal coverage- Can this team deliver the stated roadmap on the stated timeline?
- Does leadership know about the debt, and is time budgeted to repay it?
- Is the engineering shape consistent with the commercial story?
Security & Reliability Posture
05 · partial coverage- measured 05.5 found credential-shaped strings in this repository. Was each one revoked at the provider? Deleting it from the code revokes nothing; only the provider's audit log shows that it was.
- measured No threat model is in the tree of what looks like a running service. Does one exist elsewhere, and who owns it?
- What has actually broken, how often, and how badly?
- What did external testing find, and was it fixed?
- What is the SOC 2, ISO 27001 or GDPR status, and where is the evidence?
Observability & Operations
06 · partial coverage- measured Nothing in the tree backs up or restores data. How is data backed up, and has a restore ever been rehearsed?
- measured No alert rule is defined in the repository. Where are alerts defined, who receives them, and when did one last fire?
- Are the dashboards opened, the alerts acknowledged and the pages answered?
- Are the service-level objectives actually met?
- Who carries the pager, and how often does it go off?
- What does it cost to run, and how much headroom is there?
Fit with the Acquirer
07 · none coverageNot rated: structurally not assessable from a repository.
- This is primarily a PHP codebase. Does your engineering organisation already run PHP in production, or would this be the first?
- The bulk of this system sits in webroot/, plugins/, resources/. Which of your existing systems would each of those have to absorb or replace?
- The repository carries deployment configuration (.ddev/docker-compose.adminer.yaml and 5 more). Does that match your deployment and on-call model, or does it need rehosting first?
- What is your tolerance for the findings above remaining unaddressed for the first two quarters after close, given everything else that will compete for this team's time?
- Which of these systems duplicate yours, and which get retired?
- What will integration cost, and in what order?
- Where does the team land in your organisation, and who reports to whom?
- Are there earn-outs, retention packages or contractor IP to assign?
- Do customer contracts limit hosting, regions or vendors?
A human assessment is Borehole's own paid service, €12,000+ (total price is determined per engagement; travel billed at cost). It is not independent of this report: the same business produced both. It is a separate contract, with its own scope, terms and reliance.
Embed the badge
Tied to this commit and this date, and it fades after 90 days — an honest badge is one that expires. A repository with significant findings gets a neutral "read" badge rather than a red one: the library is where the range is visible, not someone else's README.
[](/r/passbolt/passbolt_api/5de65b8)If you embed it: link it to the report, remove it if the report is delisted, and do not present it as a certification or an endorsement.
Rejection log — 94 signals that ran and did not fire
Appendix: rejection log — 94 signals that ran and did not fire
Published on purpose. A signal that looked and decided not to fire has told you something, and this is the calibration data behind every threshold above.
Looked, and found nothing — 67
| Signal | What it found |
|---|---|
| 04.hotspot_concentration | change is spread across the codebase rather than pooling in a few filesfiles 33,440 · top5 share 0.015 |
| 04.debt_markers | debt markers are sparsemarkers 33 · per kloc 0.07 · lines read 477,690 |
| 04.dependency_sprawl | direct dependency counts are unremarkable |
| 04.test_growth | test effort kept pace with code writtenlate test per code 0.334 · early test per code 0.575 |
| 04.fixes_with_tests | fixes usually come with a testfixes 548 · share 0.617 · with tests 338 |
| 04.fix_share_trend | fixing is not crowding out building |
| 04.compat_layers | little code is kept for the old wayshare 0.0 · code files 2,140 · compat files 0 |
| 06.telemetry_presence | a telemetry or error-reporting library is referencednote presence only; whether anyone watches it is not visible here · matches 1 |
| 06.healthcheck_presence | a health or readiness check is defined |
| 06.correlation_ids | a request can be followed through the logstracing False · request id sites 13 |
| 06.usage_reporting_default | the product's code names no reporting hostsettings on 0 · settings off 0 |
| 06.deployed_image_floats | every deployed image names a versionimages 3 · floating 0 |
| 06.environment_branching | environment differences live in configurationsites 0 |
| 06.release_markers | releases are markedtags last year 44 · release commits 2 · changelog commits 105 |
| 06.migrate_on_start | migrations do not run at container start |
| 03.contributor_concentration | no single contributor dominates the last 24 monthsyears 21.4 · window last 24 months · authors 506 |
| 03.active_contributors | more than one contributor active in the trailing yearall time 506 · active 12mo 18 |
| 03.knowledge_silos | every substantial directory has been touched by more than one personauthors 506 · directories 7 |
| 03.drive_by_contributors | an open contributor base, where one-commit contributors are normalauthors 506 · one off share 0.364 |
| 03.contributor_attrition | no contributor dominates enough for their absence to matterauthors 506 · top share less than a quarter · top contributor last committed more than three years ago |
| 03.critical_path_ownership | more than one person changes the critical pathsauthors 28 |
| 03.second_contributor_attrition | the second and third contributors are still active |
| 03.bus_factor_trend | the team has not narrowed to one person |
| 03.joiners_and_leavers | the team is not shrinkingleft 6 · joined 3 · regular last year 12 |
| 02.merge_discipline | a meaningful share of recent change carries evidence of reviewmerges 1,694 · window last 24 months · with tracked 0 |
| 02.test_presence | tests are present in a normal proportion to sourcetests 1,478 · source 3,617 · test ratio 0.409 |
| 02.release_cadence | tags are presenttags 278 |
| 02.conventional_commits | commit subjects generally carry contentsampled 26,170 · low content share 0.011 |
| 02.branch_protection_hints | process scaffolding is present in the repository |
| 02.skipped_tests | few tests are switched offfocused 0 · skipped 0 · test files 2,078 |
| 02.revert_share | change is rarely undoneshare 0.002 · reverts 4 · recent commits 2,564 |
| 02.dependency_update_cadence | dependencies move with the codelockfiles 2 · commits since 3 · days since lockfile changed 3 |
| 02.flaky_test_markers | tests are not retried until they passtest retries 0 · suite retries 0 |
| 02.commit_size | changes arrive in reviewable sizesshare 0.007 · commits 2,287 · over 2000 lines 15 |
| 01.burst_import | the largest burst was a branch merged by a merge commit, developed on its own branch and landed in one piece (100% of it), which explains the rate: translations arrive from a vendor in bulk, dependencies and generated code are committed whole, a merged pull request is dated when it merged, not when it was written, a branch merged by a merge commit was reviewed as one piece, and an export or mirror tool dates history when it replays itlargest commits 7e9d056..287496d · bursts explained 2 · largest net added 11,646 |
| 01.initial_dump | first commit is not a disproportionate share of the codebaseinsertions 0 · share of insertions 0.0 |
| 01.message_uniformity | commit subjects vary in wording and lengthlength stdev 60.56 · repeat share 0.176 |
| 01.revision_depth | most files were revisited after they were first writtenfiles seen 2,135 · write once share 0.177 |
| 01.duplicated_blocks | little shipping code is repeated verbatim across filesshare 0.0201 · product files 2,138 · distinct blocks 80,912 |
| 01.swallowed_errors | errors are rarely thrown awayloc 481,336 · files 21 · per kloc 0.13 |
| 01.unfinished_migration | no language migration is stalled halfway |
| 01.weights_in_git | no model weights are committedfiles 0 |
| 05.committed_secrets | no credential-shaped strings outside test and fixture pathsnote the working tree only; the history is 05.5 · patterns 8 · files read 3,690 |
| 05.security_guardrails | at least one standard guard rail is configured |
| 05.dependency_pinning | a lockfile is committed, so builds are reproduciblelockfile True |
| 05.license_present | a licence file is presentfound True |
| 05.secrets_management_pattern | no environment file is committed outside tests and examplesenv files 0 |
| 05.sql_from_strings | no SQL is assembled from strings in product codefiles 0 · sites 0 · value interpolated 0 |
| 05.shell_from_strings | product code does not build shell commands from stringssites 0 |
| 05.unsafe_deserialization | no code-executing deserialiser in product codesites 0 |
| 05.tls_verification_off | no TLS verification is switched off in product codefiles 0 · sites 0 · pinned instead 0 |
| 05.known_vulnerabilities | no locked dependency has a published advisoryadvisories 0 · dependencies 121 · high or critical 0 |
| 05.privileged_workloads | no workload runs privileged or in the host's namespacessites 0 · behind a setting or built here 0 |
| 05.credentials_in_deploy_config | deployment configuration references secrets, never holds themfiles 0 · sites 0 |
| 05.signing_material | no signing keystore or profile is committedfiles 0 |
| 05.license_copyleft_inherited | every licence found in vendored code is permissive or weak-copyleftvendored paths 34 |
| 05.license_manifest_conflict | manifest and licence file agree on AGPL-3.0license AGPL-3.0 |
| 05.license_grant_unclear | the licence is recognisable as AGPL-3.0class network-copyleft · license AGPL-3.0 |
| 05.committed_native_libraries | no widely used compiled library is committed to the productlibraries 0 |
| 04.dependency_churn | few dependencies were added and dropped within 60 daysdependencies seen 90 · added in two years 12 · removed within 60 days 2 |
| 04.repository_status | the README's first screen states no end, move or freezestatements 0 |
| 02.development_elsewhere | nothing says development happens elsewhereno pr statements 0 · mirror statements 0 · replayed commit share 0.0 |
| 05.licence_changes | the root licence has not changed in the history readlicence versions 1 · unreleased changes 0 |
| 04.releases_stopped | releases keep pace with developmentmedian gap days 6.5 · days since last tag 3 · commits last 90 days 529 |
| 04.release_branch | the newest release was cut from the branch surveyedelsewhere 2 · on branch 177 · tags in window 179 |
| 03.single_maintainer | no file says one person maintains itstatements 0 |
| 05.project_exploited | no affecting advisory is on CISA's Known Exploited listexploited 0 |
Could not conclude, or did not apply — 27
Not a clean result. Each says why it could not answer here.
| Signal | Why |
|---|---|
| 04.eol_runtime | no pinned runtime version to check |
| 04.schema_churn | no schema migrations to read |
| 04.dependency_redundancy | no JavaScript manifest to read |
| 06.telemetry_depth | none at all is 06.1 |
| 06.print_logging | not assessed for PHP: its logger calls are not read |
| 06.alert_rules | no alert rules in the repository; they may live in a console |
| 06.probes_identical | no Kubernetes probes |
| 06.single_replica | no Kubernetes deployments |
| 06.feature_flags | no feature-flag service; flags may live elsewhere |
| 02.ci_runs_tests | no CI configuration to read |
| 02.ci_test_gating | no CI configuration to read |
| 02.lint_in_build | too small, or no CI to wire a linter into (02.2) |
| 01.build_reproducibility | no product Dockerfile to read |
| 01.notebook_outputs | not a data or machine-learning repository |
| 05.container_runs_as_root | no Dockerfile to read |
| 05.supply_chain_pinning | no CI actions or pipe-to-shell installs to check |
| 05.outbound_timeouts | not assessed for PHP, the language the product is written in: this check's patterns read other languages only |
| 05.migration_reversibility | too few migrations to judge |
| 05.resource_limits | no Kubernetes workload manifests |
| 05.public_env_secret | not a frontend |
| 05.unsafe_html | not a frontend |
| 05.source_maps_shipped | not a frontend |
| 05.cleartext_traffic | not a mobile app |
| 05.dataset_provenance | not a data or machine-learning repository |
| 04.flags_accumulating | few or no feature flags in the history |
| 04.api_versions_coexisting | one API version is served, or none |
| 05.project_advisories | could not tell whether 3 published advisories affect the surveyed code: its version could not be placed |
Anyone can check this report against the authoritative record — click the stamp, or enter DR90-CYEZ-TXHZ at borehole.dev/verify.
The code commits to the 106 checks this run performed, the bands they produced, and the commit they were read at. It does not cover checks written since.
Put the mark in your README
The image is wrapped in a link to the verification page, so a reader can check it rather than take it on trust. If you embed it: link it to the report, remove it if the report is delisted, and do not present it as a certification or an endorsement.
[](https://borehole.dev/verify/DR90CYEZTXHZ?via=badge)
Where this scan ran
This scan ran on ordinary cloud infrastructure (cloud-run), not in a hardware-isolated confidential VM. Nothing about it is attested by Google.
What an attested survey proves, and what it does not.
What this scan did with the repository — 7 steps
Written by the steps themselves as they ran, not described afterwards. A hand-written account of a data flow drifts the first time somebody changes the flow and not the account.
| At | Step | Detail |
|---|---|---|
| 0.0s | read repository metadata from the GitHub API | size mb: 178.5authenticated: False |
| 30.9s | cloned the repository to a temporary directory | depth: full |
| 67.9s | read the git history | commits: 34317tracked files: 4487 |
| 350.3s | ran the deterministic checks | blame pass: Falseread working tree: False |
| 350.3s | recorded where this scan ran | attested: Falseenvironment: cloud-run |
| 538.4s | kept the facts, never the source, for re-reading under new checks | |
| 538.4s | deleting the working copy |
Total 538.4s ·source content sent off this machine: none · calls to a language model: 0 · the clone was deleted when the survey ended
An automated reading of a repository's code and its history up to one commit, with public advisory records. It may be wrong, it is not legal, financial, investment or security advice, and it does not replace diligence by a qualified person. It is provided for information: nobody may rely on it (Borehole's terms, section 3).