@modusoperandi/licit-custom-styles
CustomStyle plugin built with ProseMirror
Supply chain provenance
Status for the latest visible version.
Maintainers
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| phantom-deps | phantom-dep:katex | AI (phantom-deps): Declared in dependencies; used by plugin config, not direct import. | ai | |
| phantom-deps | phantom-dep:react-dom | AI (phantom-deps): Declared in dependencies; used by plugin config, not direct import. | ai | |
| phantom-deps | phantom-dep:node-mathquill | AI (phantom-deps): Declared in dependencies; used by plugin config, not direct import. | ai | |
| provenance | missing-githead | AI (provenance): No behavioral signal; publish env variance for a long-standing trusted internal package. | ai | |
| publish-pattern | new-deps-added | AI (publish-pattern): uuid is a standard well-vetted dependency, no exec/exfil behavior. | ai |
Versions (showing 41 of 41)
| Version | Deps | Published |
|---|---|---|
| 1.4.1 | 3 / 26 | |
| 1.4.0 | 3 / 26 | |
| 1.3.14 | 3 / 26 | |
| 1.3.13 | 3 / 26 | |
| 1.3.12 | 3 / 26 | |
| 1.3.11 | 3 / 26 | |
| 1.3.10 | 3 / 26 | |
| 1.3.9 | 3 / 26 | |
| 1.3.8 | 3 / 26 | |
| 1.3.7 | 3 / 26 | |
| 1.3.6 | 3 / 26 | |
| 1.3.5 | 3 / 26 | |
| 1.3.4 | 3 / 27 | |
| 1.3.3 | 3 / 27 | |
| 1.3.2 | 3 / 27 | |
| 1.3.1 | 3 / 27 | |
| 1.3.0 | 3 / 27 | |
| 1.2.2 | 3 / 27 | |
| 1.2.1 | 3 / 27 | |
| 1.2.0 | 3 / 27 | |
| 1.1.7 | 3 / 27 | |
| 1.1.6 | 3 / 27 | |
| 1.1.5 | 3 / 27 | |
| 1.1.4 | 3 / 27 | |
| 1.1.3 | 3 / 27 | |
| 1.1.2 | 3 / 27 | |
| 1.1.1 | 3 / 27 | |
| 1.1.0 | 3 / 21 | |
| 1.0.17 | 3 / 27 | |
| 1.0.16 | 3 / 27 | |
| 1.0.15 | 3 / 27 | |
| 1.0.14 | 3 / 27 | |
| 1.0.13 | 2 / 27 | |
| 1.0.12 | 4 / 27 | |
| 1.0.11 | 6 / 28 | |
| 1.0.10 | 6 / 28 | |
| 1.0.9 | 6 / 28 | |
| 1.0.8 | 6 / 28 | |
| 1.0.6 | 6 / 27 | |
| 1.0.5 | 6 / 27 | |
| 1.0.4 | 6 / 27 |
v1.4.1
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v1.4.0
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v1.3.9
2 findingsPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
This version was published by a different npm account (GitHub Actions) than the most recent previously approved version (mobuilder) on 2025-10-17, but it carries Sigstore provenance attestation. This means the package moved to a trusted publisher (CI/CD with OIDC, e.g. GitHub Actions) — a supply-chain integrity improvement, not a compromise, since a stolen npm token cannot forge provenance bound to the source repository. Recorded as INFO for audit trail.
v1.3.8
2 findingsPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
This version was published by a different npm account (GitHub Actions) than the most recent previously approved version (mobuilder) on 2025-09-22, but it carries Sigstore provenance attestation. This means the package moved to a trusted publisher (CI/CD with OIDC, e.g. GitHub Actions) — a supply-chain integrity improvement, not a compromise, since a stolen npm token cannot forge provenance bound to the source repository. Recorded as INFO for audit trail.
v1.3.7
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v1.3.6
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v1.3.5
2 findingsPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
This version was published by a different npm account (mobuilder) than the most recent previously approved version (tezra) on 2025-08-07, but mobuilder 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.
v1.2.1
2 findingsThis version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: tezra.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.2.0
2 findingsThis version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: tezra.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.1.7
2 findingsThis version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: tezra.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.1.6
2 findingsThis version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: tezra.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.1.5
2 findingsThis version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: tezra.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.1.4
2 findingsThis version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: tezra.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.1.3
2 findingsThis version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: tezra.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.1.2
2 findingsThis version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: tezra.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.1.1
2 findingsThis version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: tezra.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.1.0
2 findingsThis version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: tezra.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.17
2 findingsThis version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: tezra.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.16
2 findingsThis version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: tezra.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.15
2 findingsThis version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: tezra.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.14
2 findingsThis version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: tezra.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.13
2 findingsThis version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: tezra.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.12
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.11
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.10
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.9
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.8
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.6
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.5
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.4
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.