← Home

brittle

A TAP test runner built for modern times

34
Versions
Apache-2.0
License
No
Install Scripts
Verified
Provenance

Supply chain provenance

Status for the latest visible version.

SLSA provenance attestation npm registry signatures gitHead linked

Maintainers

mafintosh

Accepted risks

Findings the reviewer chose to accept rather than block on.

SourceRuleReasonAccepted byWhen
publish-pattern dormant-publish AI (publish-pattern): Major version rewrite for Bare runtime support; SLSA provenance confirms legitimate CI/CD publish. ai
phantom-deps phantom-dep:bare-buffer AI (phantom-deps): bare-buffer is a Bare runtime polyfill referenced via package.json imports map, not direct require; stable pattern for this package. ai
publish-pattern new-deps-added AI (publish-pattern): New deps are all holepunchto/Bare ecosystem packages matching the stated v4 Bare runtime support goal. ai
maintainer-change maintainer-removed AI (maintainer-change): Org transitioned to GitHub Actions CI/CD publishing; consistent with holepunchto's workflow across their packages. ai
dependencies unvetted-dep:globbie AI (dependencies): holepunchto ecosystem dep consistent with this test runner's glob functionality; stable pattern across versions. ai
dependencies unvetted-dep:bare-cov AI (dependencies): bare-cov is a holepunchto coverage tool; expected dependency for a test runner targeting Bare runtime. ai
provenance publisher-changed AI (provenance): mafintosh is a co-maintainer in the holepunchto org; legitimate handoff. ai
phantom-deps phantom-dep:bare-assert AI (phantom-deps): Declared in package.json imports map as Bare runtime polyfill alias; not a direct import. ai
phantom-deps phantom-dep:bare-fs AI (phantom-deps): Declared in package.json imports map as Bare runtime polyfill alias; not a direct import. ai
phantom-deps phantom-dep:bare-os AI (phantom-deps): Declared in package.json imports map as Bare runtime polyfill alias; not a direct import. ai
phantom-deps phantom-dep:bare-url AI (phantom-deps): Declared in package.json imports map as Bare runtime polyfill alias; not a direct import. ai
semgrep semgrep:child-process-import AI (semgrep): CLI binary uses child_process to delegate to bare runtime; documented shim pattern, not arbitrary code execution. ai
phantom-deps phantom-dep:bare-subprocess AI (phantom-deps): Used via package.json imports map for Bare runtime; not directly imported in JS but legitimately declared. ai
phantom-deps phantom-dep:bare-process AI (phantom-deps): Used via package.json imports map for Bare runtime; not directly imported in JS but legitimately declared. ai
phantom-deps phantom-dep:bare-path AI (phantom-deps): Used via package.json imports map for Bare runtime; not directly imported in JS but legitimately declared. ai
semgrep semgrep:dynamic-require AI (semgrep): requireIfNode helper guards require() behind IS_NODE check; stable false positive for this package. ai

Versions (showing 34 of 34)

Version Deps Published
4.1.0 19 / 5
4.0.2 19 / 5
4.0.1 19 / 5
4.0.0 19 / 5
3.19.1 15 / 3
3.19.0 15 / 3
3.18.6 15 / 3
3.18.1 14 / 3
3.18.0 12 / 3
3.17.1 12 / 3
3.17.0 11 / 3
3.16.4 11 / 3
3.16.3 11 / 3
3.16.2 11 / 3
3.16.1 11 / 3
3.16.0 11 / 3
3.15.0 11 / 3
3.14.0 9 / 3
3.13.1 9 / 3
3.13.0 9 / 3
3.12.2 9 / 3
3.12.1 9 / 3
3.12.0 9 / 3
3.11.0 9 / 3
3.10.1 9 / 3
3.10.0 9 / 3
3.9.0 8 / 3
3.8.3 8 / 3
3.8.2 8 / 3
3.8.1 8 / 3
3.8.0 8 / 3
3.7.0 7 / 4
3.6.1 7 / 4
3.6.0 7 / 4

v4.1.0

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.

v4.0.2

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.

v3.16.2

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.

v3.16.1

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.

v3.16.0

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.

v3.15.0

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.

v3.14.0

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.

v3.13.1

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.

v3.13.0

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.

v3.12.2

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.

v3.12.1

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.

v3.12.0

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.

v3.11.0

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.

v3.10.1

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.

v3.10.0

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.

v3.9.0

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.

v3.8.3

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.

v3.8.2

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.

v3.8.1

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.

v3.8.0

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.

v3.7.0

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.

v3.6.1

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.

v3.6.0

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.