← Home

@mui/internal-test-utils

Utilities for MUI tests. This is an internal package not meant for general use.

13
Versions
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

janpotomsmichaldudakmnajdovadiegoandaibrijeshb42siriwatknpmj12albertaarongarciahdav-isoliviertassinari

Accepted risks

Findings the reviewer chose to accept rather than block on.

SourceRuleReasonAccepted byWhen
provenance slsa-provenance AI (provenance): MUI uses GitHub Actions CI/CD for releases; SLSA provenance is expected for this package. ai
bogus-package bogus-package AI (bogus-package): Internal test utility; sparse README and no keywords are expected for an internal-use package. ai
phantom-deps phantom-dep:lodash AI (phantom-deps): lodash is a declared runtime dep used in test utilities; phantom-dep heuristic is a false positive here. ai
phantom-deps phantom-dep:@babel/runtime AI (phantom-deps): Framework-scoped package loaded by convention in Babel-compiled output; stable false positive. ai

Versions (showing 13 of 13)

Version Deps Published
2.0.16 14 / 0
2.0.15 17 / 9
2.0.14 17 / 9
2.0.13 18 / 9
2.0.12 18 / 9
2.0.11 18 / 9
2.0.10 19 / 8
2.0.9 19 / 8
2.0.8 20 / 8
2.0.3 20 / 8
2.0.2 20 / 8
2.0.1 20 / 8
2.0.0 20 / 8

v2.0.3

2 findings
LOW No provenance attestation provenance

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

INFO Publisher changed: mnajdova → brijeshb42 (on 2025-03-05, known maintainer) provenance

This version was published by a different npm account (brijeshb42) than the most recent previously approved version (mnajdova) on 2025-03-05, but brijeshb42 is listed as a maintainer on prior approved versions (matched on name). This looks like a manual publish by a known maintainer rather than a publisher change. Recorded as INFO for audit trail.

v2.0.2

2 findings
LOW No provenance attestation provenance

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

INFO Publisher changed: mnajdova → aarongarciah (on 2025-02-18, known maintainer) provenance

This version was published by a different npm account (aarongarciah) than the most recent previously approved version (mnajdova) on 2025-02-18, but aarongarciah is listed as a maintainer on prior approved versions (matched on name). This looks like a manual publish by a known maintainer rather than a publisher change. Recorded as INFO for audit trail.

v2.0.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.

v2.0.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.