Use npm trusted publishing instead of auth tokens
Remove manual NPM_AUTH_TOKEN configuration in favor of npm's trusted
publishing feature, which uses GitHub's OIDC provider for secure
authentication. This eliminates the need to manage npm access tokens
as GitHub Secrets while maintaining provenance support.
by Hong MinheeNov 2, 05:49 AM
Completed
Mutations: 22
Killed: 0
Type Errors: 18
Survived: 4
Errors: 0
Timeouts: 0
Runtime: 70m 24s
version: jsr:@mutasaurus/mutasaurus@0.1.4
f3246d7main0%
Add repository field requirement for new packages
Updated AGENTS.md and CONTRIBUTING.md to include the requirement of adding
the `repository` field to `package.json` when adding a new package.
This is necessary for provenance information during npm publishing.
[ci skip]
by Hong MinheeOct 31, 09:49 AM
Completed
Mutations: 22
Killed: 0
Type Errors: 18
Survived: 4
Errors: 0
Timeouts: 0
Runtime: 70m 45s
version: jsr:@mutasaurus/mutasaurus@0.1.4
73f7cb4main0%
Version bump
[ci skip]
by Hong MinheeOct 14, 06:54 AM
Completed
Mutations: 22
Killed: 0
Type Errors: 18
Survived: 4
Errors: 0
Timeouts: 0
Runtime: 73m 26s
version: jsr:@mutasaurus/mutasaurus@0.1.3
Mutations are not run by their respective open source project maintainers. The mutation score does not tell the full story of a test suite, and while it may be a better proxy than traditional test coverage for quality, scores should be used as a guide, not a definitive measure.