@recogito/pdf-annotator
PDF annotation in the browser, using PDF.js and the Recogito Text Annotator
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
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| source-diff | encoded-string-file:dist/pdf-annotator.js | AI (source-diff): Base64 string is a PDF.js font-loading test blob; stable false positive for this package. | ai | |
| source-diff | encoded-string-file:dist/index.js | AI (source-diff): Base64 string is a PDF.js test font blob, not a malicious payload; stable pattern for this package. | ai | |
| provenance | no-provenance | AI (provenance): Established Recogito org package; lack of provenance is consistent across all versions and not a risk indicator here. | ai |
Versions (showing 23 of 23)
| Version | Deps | Published |
|---|---|---|
| 4.2.5 | 3 / 3 | |
| 4.2.4 | 3 / 3 | |
| 4.2.3 | 3 / 3 | |
| 4.2.2 | 3 / 3 | |
| 4.2.1 | 3 / 3 | |
| 4.2.0 | 3 / 3 | |
| 4.1.1 | 3 / 3 | |
| 4.1.0 | 3 / 3 | |
| 4.0.0 | 3 / 3 | |
| 1.6.0 | 3 / 3 | |
| 1.5.2 | 3 / 3 | |
| 1.5.1 | 3 / 3 | |
| 1.5.0 | 3 / 3 | |
| 1.4.0 | 3 / 3 | |
| 1.3.0 | 3 / 3 | |
| 1.2.0 | 3 / 3 | |
| 1.1.2 | 3 / 3 | |
| 1.1.1 | 3 / 3 | |
| 1.1.0 | 3 / 3 | |
| 1.0.3 | 3 / 3 | |
| 1.0.2 | 3 / 3 | |
| 1.0.1 | 3 / 3 | |
| 1.0.0 | 3 / 3 |
v1.5.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.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.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.