PartKeepr inventory authority must be checked across forks and APIs
PartKeepr is an inventory manager for electronic components. It records part numbers, stock, locations, suppliers, attachments, and the people who may change them. That makes it more sensitive than a simple catalogue, especially when the inventory supports purchasing or production.
The 2026-11-15 count-only observations used page 1, pagesize 1, and sub_type=all. app="PartKeepr" returned 0, title="PartKeepr" returned 591, and http.body="PartKeepr" returned 925. The title and body counts identify possible product references; the zero application count is not an absence claim.
Treat the fork as part of the product identity
The original PartKeepr repository is archived, and a maintained fork documents a role-based permission system. A deployment may run either lineage or a local modification. The software name alone does not establish the authorization behavior.
Record the repository and version, then review the account model actually in use. Confirm who can create and remove users, change stock, edit part records, and access uploads. Separate normal inventory work from administration and from API access.
Inventory API clients
Inventory clients may read or update records without a browser session. Record each client's owner, credential type, allowed operations, and retirement date. Test whether a user-scoped credential inherits the expected roles and whether disabled users lose access promptly.
Protect the API and web interface with HTTPS and a management boundary. If a reverse proxy supplies identity, confirm that it strips untrusted headers. Protect backups because they can contain the whole inventory and its attachments.
Validate a discovery candidate
Open the candidate page and confirm the PartKeepr login or a product-specific asset before assigning it to an owner. Check the title, login form, static paths, and certificate together. A title match can be documentation, a demo, or an old page.
For confirmed systems, test read, stock update, user administration, and API access with two roles. Confirm that a normal user cannot change another team's records or create a new administrator. Preserve the effective rule and the audit record.
PartKeepr is old enough that fork and version drift are part of the security review. The inventory should name the codebase, the permission model, and the API clients before it calls the asset known.
Top comments (0)