@manuscripts/style-guide
Shared components for Manuscripts applications
Supply chain provenance
Status for the latest visible version.
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
Keywords
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| provenance | no-provenance | AI (provenance): Long-established package with consistent publish history; lack of Sigstore provenance is common and not a risk signal here. | ai | |
| phantom-deps | phantom-dep:react-dom | AI (phantom-deps): UI component library; react-dom is a peer/config dep, not directly imported in source. | ai | |
| phantom-deps | phantom-dep:@manuscripts/json-schema | AI (phantom-deps): Same org scope; used transitively or in config, stable false positive for this package. | ai | |
| phantom-deps | phantom-dep:react-dnd | AI (phantom-deps): Directly declared and used; false positive for this package. | ai | |
| phantom-deps | phantom-dep:prosemirror-view | AI (phantom-deps): Directly declared and used; false positive for this package. | ai | |
| phantom-deps | phantom-dep:prosemirror-model | AI (phantom-deps): Directly declared and used; false positive for this package. | ai | |
| phantom-deps | phantom-dep:prosemirror-state | AI (phantom-deps): Directly declared and used; false positive for this package. | ai | |
| phantom-deps | phantom-dep:lodash | AI (phantom-deps): Directly declared and used; false positive for this package. | ai | |
| phantom-deps | phantom-dep:prosemirror-history | AI (phantom-deps): Directly declared and used; false positive for this package. | ai | |
| phantom-deps | phantom-dep:prosemirror-commands | AI (phantom-deps): Directly declared and used; false positive for this package. | ai | |
| phantom-deps | phantom-dep:react-dnd-html5-backend | AI (phantom-deps): Directly declared and used; false positive for this package. | ai | |
| phantom-deps | phantom-dep:prosemirror-keymap | AI (phantom-deps): Directly declared and used; false positive for this package. | ai | |
| phantom-deps | phantom-dep:date-fns | AI (phantom-deps): Directly declared and used; false positive for this package. | ai | |
| phantom-deps | phantom-dep:react-is | AI (phantom-deps): Directly declared and used; false positive for this package. | ai |
Versions (showing 57 of 57)
| Version | Deps | Published |
|---|---|---|
| 3.5.28 | 20 / 49 | |
| 3.5.27 | 20 / 49 | |
| 3.5.26 | 20 / 49 | |
| 3.5.25 | 20 / 49 | |
| 3.5.23 | 20 / 49 | |
| 3.5.22 | 20 / 49 | |
| 3.5.21 | 20 / 51 | |
| 3.5.19 | 20 / 51 | |
| 3.5.18 | 20 / 51 | |
| 3.5.17 | 20 / 51 | |
| 3.5.16 | 20 / 51 | |
| 3.5.15 | 20 / 51 | |
| 3.5.14 | 20 / 51 | |
| 3.5.13 | 20 / 51 | |
| 3.5.12 | 20 / 51 | |
| 3.5.11 | 20 / 51 | |
| 3.5.10 | 20 / 51 | |
| 3.5.9 | 20 / 51 | |
| 3.5.8 | 20 / 51 | |
| 3.5.7 | 20 / 51 | |
| 3.5.6 | 20 / 51 | |
| 3.5.5 | 20 / 51 | |
| 3.5.4 | 21 / 52 | |
| 3.5.2 | 21 / 52 | |
| 3.5.1 | 22 / 52 | |
| 3.5.0 | 22 / 52 | |
| 3.4.7 | 22 / 52 | |
| 3.4.6 | 22 / 52 | |
| 3.4.5 | 21 / 51 | |
| 3.4.4 | 21 / 51 | |
| 3.4.3 | 21 / 51 | |
| 3.4.2 | 21 / 51 | |
| 3.4.1 | 21 / 51 | |
| 3.4.0 | 21 / 51 | |
| 3.3.15 | 21 / 51 | |
| 3.3.14 | 21 / 51 | |
| 3.3.13 | 21 / 51 | |
| 3.3.12 | 21 / 51 | |
| 3.3.11 | 21 / 51 | |
| 3.3.10 | 21 / 51 | |
| 3.3.9 | 21 / 51 | |
| 3.3.8 | 21 / 51 | |
| 3.3.7 | 23 / 49 | |
| 3.3.6 | 23 / 49 | |
| 3.3.2 | 23 / 46 | |
| 3.3.1 | 23 / 46 | |
| 3.3.0 | 23 / 46 | |
| 3.2.3 | 23 / 46 | |
| 3.2.2 | 23 / 46 | |
| 3.2.1 | 23 / 46 | |
| 3.1.6 | 23 / 46 | |
| 3.1.5 | 23 / 46 | |
| 3.1.4 | 23 / 46 | |
| 3.1.2 | 23 / 46 | |
| 3.1.0 | 23 / 46 | |
| 3.0.1 | 23 / 46 | |
| 3.0.0 | 23 / 46 |
v3.5.28
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.5.27
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.5.26
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.5.25
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.5.23
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.5.22
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.5.21
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.5.19
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.5.18
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.5.17
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.5.16
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.5.15
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.5.14
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.5.13
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.5.12
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.5.11
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.5.10
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.5.9
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.5.8
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.5.7
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.5.6
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.5.5
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.5.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.5.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.5.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.5.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.4.7
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.4.6
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.4.5
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.4.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.4.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.4.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.4.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.4.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.3.15
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.3.14
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.3.13
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.3.12
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.3.11
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.3.10
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.3.9
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.3.8
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.3.7
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.3.6
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.3.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.3.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.3.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.2.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.2.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.2.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.1.6
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.1.5
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.1.4
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.1.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.1.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.0.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.0.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.