@manuscripts/article-editor CPAL-1.0 35 versions

@manuscripts/article-editor

npm Repository Homepage

React components for editing and viewing manuscripts

35

Versions

CPAL-1.0

License

No

Install Scripts

Missing

Provenance

Supply chain provenance

Status for the latest visible version.

No SLSA provenance npm registry signatures gitHead linked

Without SLSA provenance there is no cryptographic link between this tarball and the public source — the axios compromise (March 2026) relied on exactly this gap.

Maintainers

maci

Accepted risks

Findings the reviewer chose to accept rather than block on.

Source	Rule	Reason	Accepted by	When
phantom-deps	phantom-dep:react-is	AI (phantom-deps): Referenced in config/peer context, not a missing import; stable pattern for this UI library.	ai	2026/05/29
phantom-deps	phantom-dep:react-dom	AI (phantom-deps): Peer dependency pattern for React component library; stable false positive.	ai	2026/05/29
phantom-deps	phantom-dep:jwt-decode	AI (phantom-deps): Declared dep used indirectly via re-export or config; stable for this package.	ai	2026/05/29
phantom-deps	phantom-dep:react-select	AI (phantom-deps): UI component library dep; referenced in config, stable false positive.	ai	2026/05/29
phantom-deps	phantom-dep:@popperjs/core	AI (phantom-deps): Transitive/peer dep for react-popper; stable false positive for this package.	ai	2026/05/29
phantom-deps	phantom-dep:html-react-parser	AI (phantom-deps): Declared runtime dep; heuristic false positive, stable for this package.	ai	2026/05/29

Versions (showing 35 of 35)

Version	Deps	Published
4.13.56	32 / 35	2026-06-04
4.13.55	32 / 35	2026-06-04
4.13.54	32 / 35	2026-06-04
4.13.53	32 / 35	2026-06-04
4.13.52	32 / 35	2026-06-02
4.13.51	32 / 35	2026-06-02
4.13.50	32 / 35	2026-05-31
4.13.49	32 / 35	2026-05-31
4.13.48	32 / 35	2026-05-24
4.13.47	32 / 35	2026-05-20
4.13.45	32 / 35	2026-05-20
4.13.44	32 / 35	2026-05-19
4.13.43	32 / 35	2026-05-18
4.13.42	32 / 35	2026-05-18
4.13.41	32 / 35	2026-05-17
4.13.40	32 / 41	2026-05-14
4.13.39	32 / 41	2026-05-12
4.13.38	32 / 41	2026-05-11
4.13.37	32 / 41	2026-05-11
4.13.36	32 / 41	2026-05-11
4.13.35	32 / 41	2026-05-08
4.13.34	32 / 41	2026-05-07
4.13.33	32 / 41	2026-05-07
4.13.32	32 / 41	2026-05-07
4.13.31	32 / 41	2026-05-07
4.12.10	32 / 41	2026-03-16
4.12.9	32 / 41	2026-03-11
4.9.18	33 / 40	2026-03-06
4.7.3	33 / 37	2025-11-11
4.7.2	33 / 37	2025-11-10
4.7.1	33 / 37	2025-11-09
4.7.0	33 / 37	2025-11-06
4.2.25	33 / 37	2025-07-13
4.2.24	33 / 37	2025-07-10
4.2.23	33 / 37	2025-07-10

v4.13.56

1 finding

LOW No provenance attestation provenance

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

v4.13.55

1 finding

LOW No provenance attestation provenance

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

v4.13.54

1 finding

LOW No provenance attestation provenance

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

v4.13.53

1 finding

LOW No provenance attestation provenance

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

v4.13.52

1 finding

LOW No provenance attestation provenance

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

v4.13.51

1 finding

LOW No provenance attestation provenance

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

v4.13.50

1 finding

LOW No provenance attestation provenance

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

v4.13.49

1 finding

LOW No provenance attestation provenance

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

v4.13.48

1 finding

LOW No provenance attestation provenance

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

v4.13.47

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.

v4.13.45

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.

v4.13.44

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.

v4.13.43

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.

v4.13.42

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.

v4.13.41

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.

v4.13.40

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.

v4.13.39

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.

v4.13.38

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.

v4.13.37

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.

v4.13.36

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.

v4.13.35

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.

v4.13.34

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.

v4.13.33

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.

v4.13.32

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.

v4.13.31

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.

v4.12.10

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.

v4.12.9

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.

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

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

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

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

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

v4.2.25

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.

v4.2.24

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.

v4.2.23

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.