@unified-latex/unified-latex-util-parse
Tools for manipulating unified-latex ASTs
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 |
|---|---|---|---|---|
| dependencies | unvetted-dep:@unified-latex/unified-latex-ctan | AI (dependencies): Same-monorepo sibling package; stable false positive for this namespace. | ai | |
| dependencies | unvetted-dep:@unified-latex/unified-latex-util-trim | AI (dependencies): Same-monorepo sibling package; stable false positive for this namespace. | ai | |
| dependencies | unvetted-dep:@unified-latex/unified-latex-util-match | AI (dependencies): Same-monorepo sibling package; stable false positive for this namespace. | ai | |
| dependencies | unvetted-dep:@unified-latex/unified-latex-util-pegjs | AI (dependencies): Same-monorepo sibling package; stable false positive for this namespace. | ai | |
| dependencies | unvetted-dep:@unified-latex/unified-latex-util-visit | AI (dependencies): Same-monorepo sibling package; stable false positive for this namespace. | ai | |
| dependencies | unvetted-dep:@unified-latex/unified-latex-util-catcode | AI (dependencies): Same-monorepo sibling package; stable false positive for this namespace. | ai | |
| dependencies | unvetted-dep:@unified-latex/unified-latex-util-arguments | AI (dependencies): Same-monorepo sibling package; stable false positive for this namespace. | ai | |
| dependencies | unvetted-dep:@unified-latex/unified-latex-util-print-raw | AI (dependencies): Same-monorepo sibling package; stable false positive for this namespace. | ai | |
| dependencies | unvetted-dep:@unified-latex/unified-latex-util-environments | AI (dependencies): Same-monorepo sibling package; stable false positive for this namespace. | ai | |
| provenance | no-provenance | AI (provenance): No provenance is common; no other risk signals present for this package. | ai |
Versions (showing 28 of 28)
| Version | Deps | Published |
|---|---|---|
| 1.8.4 | 11 / 0 | |
| 1.8.3 | 11 / 0 | |
| 1.8.2 | 11 / 0 | |
| 1.8.1 | 11 / 0 | |
| 1.8.0 | 11 / 0 | |
| 1.7.1 | 11 / 0 | |
| 1.7.0 | 11 / 0 | |
| 1.6.1 | 11 / 0 | |
| 1.6.0 | 11 / 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 | 11 / 0 | |
| 1.2.1 | 11 / 0 | |
| 1.2.0 | 11 / 0 | |
| 1.1.0 | 11 / 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 | |
| 1.0.0 | 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. Only ~12% of npm packages have provenance, so this is common but not ideal.
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
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.6.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.4.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.4.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.4.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.3.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.3.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.3.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.2.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.2.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.2.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.1.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.12
1 finding[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. Consider requesting the maintainer enable provenance via CI/CD.
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.
v1.0.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.