@unified-latex/unified-latex-prettier
Prettier plugin for processing LaTeX code via unified-latex
Supply chain provenance
Status for the latest visible version.
Without SLSA provenance there is no cryptographic link between this tarball and the public source, so a manually published version cannot be tied back to a reviewed commit.
Maintainers
Keywords
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| source-diff | obfuscated-file:index.cjs | AI (source-diff): esbuild bundle banner, matches dual-module exports config; not true obfuscation. | ai | |
| phantom-deps | phantom-dep:unified | AI (phantom-deps): unified used as peer type/config dep in this monorepo package, stable FP. | ai | |
| dependencies | unvetted-dep:@unified-latex/unified-latex-util-trim | AI (dependencies): Same-monorepo sibling dep; version-locked to matching release. | ai | |
| dependencies | unvetted-dep:@unified-latex/unified-latex-util-align | AI (dependencies): Same-monorepo sibling dep; version-locked to matching release. | ai | |
| dependencies | unvetted-dep:@unified-latex/unified-latex-util-match | AI (dependencies): Same-monorepo sibling dep; version-locked to matching release. | ai | |
| dependencies | unvetted-dep:@unified-latex/unified-latex-util-parse | AI (dependencies): Same-monorepo sibling dep; version-locked to matching release. | ai | |
| dependencies | unvetted-dep:@unified-latex/unified-latex-ctan | AI (dependencies): Same-monorepo sibling dep; version-locked to matching release. | ai | |
| dependencies | unvetted-dep:@unified-latex/unified-latex-util-pgfkeys | AI (dependencies): Same-monorepo sibling dep; version-locked to matching release. | ai | |
| dependencies | unvetted-dep:@unified-latex/unified-latex-util-print-raw | AI (dependencies): Same-monorepo sibling dep; version-locked to matching release. | ai | |
| provenance | no-provenance | AI (provenance): Established package without provenance attestation; common for this ecosystem. | ai | |
| dependencies | unvetted-dep:@unified-latex/unified-latex-util-visit | AI (dependencies): Same-monorepo sibling dep; version-locked to matching release. | ai | |
| dependencies | unvetted-dep:@unified-latex/unified-latex-types | AI (dependencies): Same-monorepo sibling dep; version-locked to matching release. | ai |
Versions (showing 27 of 27)
| Version | Deps | Published |
|---|---|---|
| 1.8.4 | 10 / 0 | |
| 1.8.3 | 10 / 0 | |
| 1.8.2 | 10 / 0 | |
| 1.8.1 | 10 / 0 | |
| 1.8.0 | 10 / 0 | |
| 1.7.1 | 10 / 0 | |
| 1.7.0 | 10 / 0 | |
| 1.6.1 | 10 / 0 | |
| 1.6.0 | 10 / 0 | |
| 1.4.2 | 11 / 0 | |
| 1.4.1 | 11 / 0 | |
| 1.4.0 | 11 / 0 | |
| 1.3.2 | 11 / 0 | |
| 1.3.1 | 11 / 0 | |
| 1.3.0 | 11 / 0 | |
| 1.2.2 | 10 / 0 | |
| 1.2.1 | 10 / 0 | |
| 1.2.0 | 10 / 0 | |
| 1.1.0 | 10 / 0 | |
| 1.0.12 | 10 / 0 | |
| 1.0.11 | 10 / 0 | |
| 1.0.10 | 10 / 0 | |
| 1.0.9 | 10 / 0 | |
| 1.0.8 | 10 / 0 | |
| 1.0.7 | 10 / 0 | |
| 1.0.6 | 10 / 0 | |
| 1.0.5 | 10 / 0 |
v1.8.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.8.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.8.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.7.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.7.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.6.1
2 findingsNewly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.6.0
2 findingsNewly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.4.2
2 findingsNewly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.4.1
2 findingsNewly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.4.0
2 findingsNewly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.3.2
2 findingsNewly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.3.1
2 findingsNewly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.3.0
2 findingsNewly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.2.2
2 findingsNewly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.2.1
2 findingsNewly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.2.0
2 findingsNewly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.1.0
2 findingsNewly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.12
2 findingsNewly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.11
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.10
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.9
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.8
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.7
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.6
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.5
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.