← Home

better-dx

All the development dependencies you need.

16
Versions
MIT
License
No
Install Scripts
Verified
Provenance

Supply chain provenance

Status for the latest visible version.

SLSA provenance attestation npm registry signatures No source commit

Maintainers

chrisbreuer

Keywords

typescriptdevelopmentkitbunpackage

Accepted risks

Findings the reviewer chose to accept rather than block on.

SourceRuleReasonAccepted byWhen
dependencies unvetted-dep:@stacksjs/gitlint AI (dependencies): Phantom dep used only in config/tooling; not imported at runtime. Stable pattern for this package. ai
dependencies unvetted-dep:ts-error-handling AI (dependencies): Phantom dep; not directly imported at runtime. Tooling-only usage. ai
dependencies unvetted-dep:@stacksjs/bunpress AI (dependencies): Phantom dep used only in docs build scripts; not imported at runtime. ai
dependencies unvetted-dep:@stacksjs/logsmith AI (dependencies): Phantom dep used only in changelog scripts; not imported at runtime. ai
provenance publisher-changed AI (provenance): Transition to GitHub Actions publisher is consistent with SLSA provenance attestation; legitimate CI/CD publishing pattern for this package. ai
phantom-deps phantom-dep:bun-git-hooks AI (phantom-deps): Git hooks tool; referenced in config, not imported. ai
phantom-deps phantom-dep:@stacksjs/bumpx AI (phantom-deps): Release tooling; referenced in scripts, not imported. ai
phantom-deps phantom-dep:@stacksjs/clapp AI (phantom-deps): CLI tooling; referenced in scripts, not imported. ai
phantom-deps phantom-dep:bun-plugin-dtsx AI (phantom-deps): Build plugin; referenced in build config, not imported. ai
phantom-deps phantom-dep:bunfig AI (phantom-deps): Config-only tooling dep; not imported at runtime by design. ai
phantom-deps phantom-dep:@stacksjs/gitlint AI (phantom-deps): Git lint tool; referenced in config, not imported. ai
phantom-deps phantom-dep:ts-error-handling AI (phantom-deps): Utility dep; referenced in config, not imported. ai
phantom-deps phantom-dep:@stacksjs/bunpress AI (phantom-deps): Docs build tool; referenced in scripts, not imported. ai
phantom-deps phantom-dep:@stacksjs/logsmith AI (phantom-deps): Changelog tool; referenced in scripts, not imported. ai
phantom-deps phantom-dep:@stacksjs/clarity AI (phantom-deps): Tooling dep; referenced in config, not imported. ai
phantom-deps phantom-dep:pickier AI (phantom-deps): Linting tool referenced in scripts/config, not imported. ai
phantom-deps phantom-dep:buddy-bot AI (phantom-deps): Bot/automation tool referenced in config, not imported. ai
phantom-deps phantom-dep:@types/bun AI (phantom-deps): Type-only package; framework-scoped, not directly imported. ai
phantom-deps phantom-dep:typescript AI (phantom-deps): Build/type tooling; referenced in config, not imported at runtime. ai

Versions (showing 16 of 16)

Version Deps Published
0.2.15 14 / 0
0.2.14 14 / 0
0.2.12 14 / 0
0.2.11 0 / 3
0.2.8 0 / 0
0.2.7 0 / 0
0.2.6 0 / 0
0.2.5 0 / 0
0.2.4 0 / 0
0.2.3 0 / 0
0.2.2 0 / 0
0.2.1 0 / 0
0.2.0 0 / 0
0.1.7 0 / 0
0.1.5 0 / 0
0.1.4 0 / 0

v0.2.15

1 finding
INFO Has SLSA provenance attestation provenance

Published via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.

v0.2.14

1 finding
INFO Has SLSA provenance attestation provenance

Published via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.

v0.2.12

1 finding
INFO Has SLSA provenance attestation provenance

Published via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.

v0.2.11

1 finding
INFO Has SLSA provenance attestation provenance

Published via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.

v0.2.8

1 finding
INFO Has SLSA provenance attestation provenance

Published via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.

v0.2.7

2 findings
HIGH Publisher changed: chrisbreuer → GitHub Actions (on 2026-03-13) provenance

This version was published by a different npm account than previous versions on 2026-03-13. This could indicate a legitimate maintainer transition or an account compromise.

INFO Has SLSA provenance attestation provenance

Published via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.

v0.2.6

1 finding
INFO Has SLSA provenance attestation provenance

Published via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.

v0.2.5

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v0.2.4

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v0.2.3

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v0.2.2

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v0.2.1

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v0.2.0

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v0.1.7

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v0.1.5

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v0.1.4

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.