← Home

test-mixer

npm Repository Homepage
6
Versions
—
License
No
Install Scripts
Verified
Provenance

Supply chain provenance

Status for the latest visible version.

SLSA provenance attestation npm registry signatures gitHead linked

Maintainers

royston

Keywords

combinationshelpermixerobjectoptionsoptstestvariations

Accepted risks

Findings the reviewer chose to accept rather than block on.

SourceRuleReasonAccepted byWhen
provenance publisher-changed AI (provenance): Transition from manual publish to GitHub Actions CI with SLSA provenance; consistent with codsen monorepo CI migration. ai
phantom-deps phantom-dep:rfdc AI (phantom-deps): rfdc is a declared runtime dep in package.json; phantom-dep heuristic fires on config references, not a real missing import. ai
phantom-deps phantom-dep:object-boolean-combinations AI (phantom-deps): object-boolean-combinations is a declared runtime dep; phantom-dep heuristic fires on config references, not a real missing import. ai

Versions (showing 6 of 6)

Version Deps Published
4.2.3 2 / 0
4.2.0 2 / 0
4.1.29 2 / 0
4.1.28 2 / 0
4.1.27 2 / 0
4.1.18 2 / 0

v4.2.3

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.2.0

2 findings
HIGH Publisher changed: royston → GitHub Actions (on 2025-10-15) provenance

This version was published by a different npm account than previous versions on 2025-10-15. 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.

v4.1.29

2 findings
HIGH Publisher changed: royston → GitHub Actions (on 2025-10-12) provenance

This version was published by a different npm account than previous versions on 2025-10-12. 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.

v4.1.28

2 findings
HIGH Publisher changed: royston → GitHub Actions (on 2025-10-08) provenance

This version was published by a different npm account than previous versions on 2025-10-08. 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.

v4.1.27

2 findings
HIGH Publisher changed: royston → GitHub Actions (on 2025-10-07) provenance

This version was published by a different npm account than previous versions on 2025-10-07. 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.

v4.1.18

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.