@recogito/react-text-annotator
Recogito Text Annotator React bindings
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 |
|---|---|---|---|---|
| phantom-deps | phantom-dep:CETEIcean | AI (phantom-deps): CETEIcean is a declared runtime dep used via TEI annotator; phantom-dep heuristic fires because it's not directly imported in this React bindings wrapper. | ai | |
| dependencies | unvetted-peer-dep:openseadragon | AI (dependencies): Optional peer dep for image viewer integration; well-known open-source library, stable for this package. | ai | |
| dependencies | unvetted-dep:CETEIcean | AI (dependencies): CETEIcean is a legitimate TEI processing library; its use is expected in a text annotation package. | ai | |
| provenance | no-provenance | AI (provenance): Established @recogito org package; lack of provenance is consistent across all versions. | ai |
Versions (showing 38 of 38)
| Version | Deps | Published |
|---|---|---|
| 4.2.5 | 7 / 9 | |
| 4.2.4 | 7 / 9 | |
| 4.2.3 | 7 / 9 | |
| 4.2.2 | 7 / 9 | |
| 4.2.1 | 7 / 9 | |
| 4.2.0 | 7 / 9 | |
| 4.1.1 | 7 / 9 | |
| 4.1.0 | 7 / 9 | |
| 4.0.0 | 7 / 9 | |
| 3.4.10 | 7 / 9 | |
| 3.4.9 | 7 / 9 | |
| 3.4.8 | 7 / 9 | |
| 3.4.7 | 7 / 9 | |
| 3.4.6 | 7 / 9 | |
| 3.4.5 | 7 / 9 | |
| 3.4.4 | 7 / 9 | |
| 3.4.3 | 7 / 9 | |
| 3.4.2 | 7 / 9 | |
| 3.4.1 | 7 / 9 | |
| 3.4.0 | 7 / 9 | |
| 3.3.3 | 6 / 10 | |
| 3.3.2 | 6 / 10 | |
| 3.3.1 | 6 / 10 | |
| 3.3.0 | 6 / 10 | |
| 3.2.0 | 6 / 10 | |
| 3.1.6 | 6 / 10 | |
| 3.1.5 | 6 / 10 | |
| 3.1.4 | 6 / 10 | |
| 3.1.3 | 6 / 10 | |
| 3.1.2 | 6 / 10 | |
| 3.1.1 | 6 / 9 | |
| 3.1.0 | 6 / 9 | |
| 3.0.5 | 6 / 9 | |
| 3.0.4 | 6 / 9 | |
| 3.0.3 | 6 / 9 | |
| 3.0.2 | 6 / 9 | |
| 3.0.1 | 6 / 9 | |
| 3.0.0 | 6 / 9 |
v3.0.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.0.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.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.