@majkapp/majk-chat-document-tools
Document processing tools for majk chat - PDF, Excel, Word, PowerPoint parsing and analysis
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 |
|---|---|---|---|---|
| provenance | no-provenance | AI (provenance): No provenance is common (~88% of npm); no other risk signals present to elevate this. | ai |
Versions (showing 13 of 13)
| Version | Deps | Published |
|---|---|---|
| 1.0.82 | 3 / 7 | |
| 1.0.81 | 3 / 7 | |
| 1.0.56 | 3 / 7 | |
| 1.0.53 | 3 / 7 | |
| 1.0.49 | 3 / 7 | |
| 1.0.44 | 3 / 7 | |
| 1.0.42 | 3 / 7 | |
| 1.0.39 | 3 / 7 | |
| 1.0.38 | 3 / 7 | |
| 1.0.33 | 3 / 7 | |
| 1.0.32 | 3 / 7 | |
| 1.0.31 | 3 / 7 | |
| 1.0.23 | 1 / 7 |
v1.0.81
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.56
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.53
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.49
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.44
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.39
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.38
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.32
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.31
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.