Inventaire is a book-inventory and sharing platform built around personal shelves, groups, friends, and public data. It can be self-hosted, and it exposes an API for clients that work with inventory and bibliographic entities. The security question is which books and relationships are visible to which audience.

The 2026-11-16 count-only observation found 0 app matches, 365 title matches, and 21,182 http.body matches for Inventaire. The queries used sub_type=all, page 1, and pagesize 1. The body count includes documentation, community pages, and project references. The title count is a narrower candidate set, but it still needs page and owner validation.

Inventaire's public wiki describes inventories whose visibility can be public, limited to friends, or limited to groups. Group creation produces a shareable group URL, and roles determine what a member can do. The service's own privacy page describes first-party session cookies and data exports through the API. These controls create several access paths: the browser session, API authentication, group membership, item visibility, and data export.

Check the audience for each record

A public profile does not have to imply a public inventory. Review the default visibility for new items, the set of fields exposed in search, whether a private item appears in aggregate counts, and whether an item can be read through the API without a session. If a book is marked available for exchange, verify which exact location or contact information is disclosed.

Group access needs an administrator who can remove members and revoke old invitations. A group URL is an invitation mechanism, not a durable authorization decision. Test the behavior after a user leaves the group, after an item changes visibility, and after an API token is revoked. Cached search results or a stale export can preserve access after the visible setting changes.

Review self-hosting dependencies

Self-hosting requires the application, its database, search or query components, and external bibliographic data sources. Keep the API and database private, restrict administrative endpoints, and document which outbound data sources receive user queries. If the instance imports images or metadata, validate the source and avoid turning URL fetching into unrestricted server-side access.

Data exports contain a concentrated copy of the inventory and social relationships. Store exports outside the web root, encrypt them at rest, and expire them after the requester downloads them. Record who requested the export and which account generated it. The same rule applies to backups, because a backup may include private shelves that were never public.

Validate the candidate

Open the root page and confirm the Inventaire application assets, API endpoint, and login route. Do not enumerate private inventories or submit another user's data. The owner should verify registration, group policy, item visibility, API clients, and export behavior. The reviewer should record the host, product evidence, authentication state, and observation time.

The 365-title observation is a candidate list, not a count of exposed reading histories. A title match may be a public project page, a documentation mirror, or a live inventory. The useful outcome is a map of who owns each instance and which sharing controls are active.

References