← Home

@mdxeditor/editor

51
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

petyosi

Keywords

mdxmarkdownrich-text-editorlexicalreact

Accepted risks

Findings the reviewer chose to accept rather than block on.

SourceRuleReasonAccepted byWhen
phantom-deps phantom-dep:@radix-ui/react-icons AI (phantom-deps): Declared dependency; referenced in config files. Stable pattern for this component library. ai
provenance no-provenance AI (provenance): Long-established package; lack of provenance is consistent across all prior versions and not a risk indicator here. ai
dependencies unvetted-dep:@radix-ui/react-popper AI (dependencies): @radix-ui/react-popper is a well-known Radix UI primitive; stable false positive for this package. ai
publish-pattern dormant-publish AI (publish-pattern): 277 versions published over package lifetime; SLSA provenance confirms CI/CD pipeline; not a dormant account. ai
phantom-deps phantom-dep:@radix-ui/react-popper AI (phantom-deps): Radix UI sub-package; likely consumed transitively or via dynamic patterns not detected statically. ai
phantom-deps phantom-dep:unidiff AI (phantom-deps): Listed in package.json dependencies; likely bundled into dist output by vite build. ai
phantom-deps phantom-dep:@radix-ui/react-toggle-group AI (phantom-deps): Radix UI sub-package; likely consumed transitively or via dynamic patterns not detected statically. ai
phantom-deps phantom-dep:@radix-ui/colors AI (phantom-deps): CSS design tokens package; likely consumed via CSS imports not detected by static import analysis. ai
phantom-deps phantom-dep:@lexical/clipboard AI (phantom-deps): Lexical sub-package likely used indirectly or bundled; stable false positive for this package. ai
phantom-deps phantom-dep:@lexical/plain-text AI (phantom-deps): Lexical sub-package likely used indirectly or bundled; stable false positive for this package. ai

Versions (showing 51 of 133)

View all versions
Version Deps Published
4.1.0 57 / 62
4.0.4 55 / 61
4.0.3 55 / 61
4.0.2 55 / 61
4.0.1 55 / 61
4.0.0 55 / 61
3.55.0 56 / 61
3.54.1 56 / 61
3.54.0 56 / 61
3.53.1 56 / 61
3.53.0 56 / 61
3.52.5 56 / 61
3.52.4 56 / 61
3.52.3 56 / 61
3.52.2 56 / 60
3.52.1 56 / 60
3.52.0 56 / 60
3.51.0 56 / 60
3.50.0 56 / 60
3.49.3 56 / 60
3.49.2 56 / 60
3.49.1 56 / 60
3.49.0 56 / 60
3.48.0 56 / 60
3.47.0 56 / 60
3.46.1 56 / 60
3.46.0 56 / 60
3.45.1 56 / 60
3.45.0 56 / 60
3.44.3 56 / 60
3.44.2 56 / 60
3.44.1 56 / 60
3.44.0 56 / 60
3.43.0 56 / 60
3.42.0 56 / 60
3.41.0 54 / 60
3.40.1 54 / 60
3.40.0 54 / 60
3.39.1 54 / 60
3.39.0 54 / 60
3.38.0 54 / 60
3.37.0 54 / 60
3.36.0 54 / 60
3.35.1 54 / 60
3.35.0 54 / 60
3.34.1 54 / 60
3.34.0 54 / 60
3.33.0 53 / 60
3.32.3 53 / 60
3.32.2 53 / 60
3.32.1 53 / 60

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

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

v4.0.1

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

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

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

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

1 finding
INFO No provenance attestation provenance

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

v3.49.0

1 finding
INFO No provenance attestation provenance

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

v3.48.0

1 finding
INFO No provenance attestation provenance

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

v3.46.1

1 finding
INFO No provenance attestation provenance

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

v3.45.1

1 finding
INFO No provenance attestation provenance

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

v3.44.3

1 finding
INFO No provenance attestation provenance

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

v3.44.1

1 finding
INFO No provenance attestation provenance

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

v3.44.0

1 finding
INFO No provenance attestation provenance

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

v3.43.0

1 finding
INFO No provenance attestation provenance

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

v3.42.0

1 finding
INFO No provenance attestation provenance

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

v3.40.0

1 finding
INFO No provenance attestation provenance

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

v3.38.0

1 finding
INFO No provenance attestation provenance

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

v3.37.0

1 finding
INFO No provenance attestation provenance

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

v3.34.1

1 finding
INFO No provenance attestation provenance

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

v3.33.0

1 finding
INFO No provenance attestation provenance

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