Need an announcement or a README

An explainer is required on why "objection" on npm now points to this repo.

Is this going to be actively maintained?

There have been 496 commits to it since the fork, a diff of over 126k lines.

I know this repo is owned by the original author, but still, there needs to be some kind of an official post here.

@koskimas

Fair point, thanks. objection.js was created by @koskimas. I've maintained it at Vincit/objection.js since 2023. After Vincit removed my access earlier this year, development continues here, published as objection on npm with the publish rights I already had.

Is it maintained? Yes: 4.0 and 4.1 came out this week, and issues and PRs are handled here.
What's in the 126k lines? Mostly the ESM conversion, the vitest test suite, the rewritten graph upserts, the typings and the docs. I do this work with Claude Code and review the changes myself. All of it went through PRs here, and the changelog lists every change.
Can you trust the npm package? Releases are published from GitHub Actions with npm trusted publishing, so each version carries a provenance statement that links it to its tag and commit in this repo.
Want to stay where you are? 3.x keeps getting fixes on the 3.x branch, under the npm dist-tag legacy. 4.0 is a major release with a migration guide, so ^3 won't move you to it.

I've added a section to the README that explains this: #515

Explain in the README where objection is developed and published (#514)…

Yep, I can confirm that this is what happened. I know lehni and I know he only has good intentions.

Vincit was the software consultancy company I worked for when I wrote Objection. Due to a staggering amount of incompetency, they decided to kick me and all active maintainers out from the repo, and essentially kill it.

They have nobody to maintain Objection (or Tarn.js that suffered the same fate) and they have no plans to get anybody, so forks were necessary.

From discussions with their employees I've gathered that they didn't even realise objection or tarn had users (tarn especially has 10 million weekly downloads in npm).

Thanks for chiming in, Sami, much appreciated, and thanks for objection in the first place!

It's a shame how Vincit handled this, for objection and for tarn.js. Neither project got a handover, and their users were left with repositories that nobody maintains anymore.

Explain in the README where objection is developed and published (#514)…

Thanks for keeping it alive!

@koskimas

@koskimas did you remove your comment over at Vincit#2807 (comment) or has it been removed by somebody else? I read it earlier and I was going to reply to it, but now it's gone!

I deleted it 😅

Navigation Menu

Repository navigation

Need an announcement or a README #514

Metadata

Assignees

Labels

Type

Projects

Milestone

Relationships

Development

Need an announcement or a README #514

Description

Activity

lehni commented on Oct 18, 2026

koskimas commented on Oct 18, 2026

lehni commented on Oct 18, 2026

mjlehrke commented on Oct 22, 2026

lehni commented on Oct 25, 2026

koskimas commented on Oct 25, 2026

Metadata

Metadata

Assignees

Labels

Type

Projects

Milestone

Relationships

Development

Issue actions