Close Open Privacy Scan
App Privacy Score
Medium risk · 3387 finding(s)
Based on: 3 first-party package(s) · 151/214 deps analyzed
Dependency score: 0 (High risk)
bar_chart Score Breakdown
list Scan Summary
swap_horiz Application data flows
External domains:
::ffff:192.168.0.1a9.comaccount.blob.core.windows.netaccounts.feishu.cnaccounts.google.comaclanthology.orgacme.comai.google.devaiplatform.googleapis.comaka.msalembic.sqlalchemy.orgalpinejs.devapi-inference.huggingface.coapi.anthropic.comapi.bing.microsoft.comapi.bochaai.comapi.cloudflare.comapi.deepgram.comapi.elevenlabs.ioapi.exa.aiapi.firecrawl.devapi.github.comapi.jina.aiapi.linkup.soapi.microsoft.aiapi.mistral.aiapi.mojeek.comapi.mongodb.orgapi.morphllm.comapi.open-meteo.comapi.openai.comapi.openwebui.comapi.perplexity.aiapi.python.langchain.comapi.search.brave.comapi.serphouse.comapi.serply.ioapi.tavily.comapi.themoviedb.orgapi.together.xyzapis.google.comapp.neptune.aiarxiv.orgattribution.omnilib.devauai.orgauth.exampleauthlib.orgaws.amazon.comazure.microsoft.comblocked.exampleblog.eleuther.aibrotlipy.readthedocs.iobugs.python.orgcdn-media.huggingface.cocdn.britannica.comcdn.jsdelivr.netcdnjs.cloudflare.comchat.googleapis.comchroma-onnx-models.s3.amazonaws.comchromium.googlesource.comclear.mlclip-cn-beijing.oss-cn-beijing.aliyuncs.comcloud.google.comcode.activestate.comcode.google.comcognitiveservices.azure.comcommonmark.orgconsole.cloud.google.comcookbook.openai.comcvs.pgfoundry.orgcx-oracle.readthedocs.iodagshub.comdatabase.windows.netdatatracker.ietf.orgday.js.orgdev-discuss.pytorch.orgdev.mysql.comdeveloper.mozilla.orgdevelopers.cloudflare.comdevelopers.google.comdiscord.comdiscord.ggdiscuss.huggingface.codiscuss.python.orgdiscuss.pytorch.orgdl.acm.orgdocs.aiohttp.orgdocs.anthropic.comdocs.aws.amazon.comdocs.claude.comdocs.langchain.comdocs.microsoft.comdocs.neptune.aidocs.nomic.aidocs.nvidia.comdocs.oasis-open.orgdocs.ollama.comdocs.openwebui.comdocs.parallel.aidocs.pydantic.devdocs.pyscript.netdocs.python-requests.orgdocs.python.orgdocs.pytorch.orgdocs.ray.iodocs.rsdocs.sqlalchemy.orgdocs.swanlab.cndocs.together.aidocs.trychroma.comdocs.wandb.aidoi.orgdownload.oracle.comdvc.orgembed.trychroma.comen.wikipedia.orgendpoint.openai.azure.comerrors.pydantic.devessentia.upf.eduevil.comexam_ple.comexamine.devexample-resource.azure.openai.comexample-resource.services.ai.azure.comfarm4.staticflickr.comfastapi.tiangolo.comfki.tic.heia-fr.chflyte.orgfonts.googleapis.comfoo.comgateway.ai.cloudflare.comgenerativelanguage.googleapis.comgeoip.maps.opensearch.orggiou.stanford.edugist.github.comgithub.comgoo.glgoogle-auth.readthedocs.iogoogle.aip.devgoogle.github.iogoogle.serper.devgoogleapis.devgraph.microsoft.comguillaumejaume.github.iohelp.openai.comhf.cohips.hearstapps.comhooks.slack.comhost.docker.internalhtml.spec.whatwg.orghttpbin.orghub-ci.huggingface.cohuggingface.cohypothesis.readthedocs.ioi.postimg.ccicml.ccimages.cocodataset.orgimages.pexels.cominfer.roboflow.comipython.readthedocs.iojson-schema.orgjsonlines.orgjsonplaceholder.typicode.comkagi.comkazoo.readthedocs.iokexue.fmkombu.readthedocs.orgkroki.ioleafletjs.comlearn.microsoft.comlegacy.python.orglicenses.api.openwebui.comlinux.die.netlisten-api.listennotes.comlocalhost.tiangolo.comlogin.chinacloudapi.cnlogin.microsoft.comlogin.microsoftonline.comlogin.microsoftonline.delogin.microsoftonline.uslogin.windows-ppe.netlucene.apache.orglucumr.pocoo.orgm.youtube.commagicstack.github.iomanagement.core.chinacloudapi.cnmanagement.core.usgovcloudapi.netmanagement.core.windows.netmarc.najork.orgmistralai.github.iomodelcontextprotocol.iomsdn.microsoft.commy-keyvault-name.vault.azure.netmy.sitemyaccount.blob.core.windows.netmypy.readthedocs.iomyservice.search.windows.netmüller.denats.ionew-url.comnineplanets.orgnlp.stanford.edunodatime.orgoauth.netollama-service.open-webui.svc.cluster.localollama.comomoindrot.github.ioonedrive.live.comopen.feishu.cnopenai.comopenaipublic.blob.core.windows.netopenid.netopenoffice.orgopenreview.netopensearch.orgopentelemetry.ioopenwebui.comoptuna.readthedocs.iooracle.github.iooss.redis.comother.comotheraccount.blob.core.windows.netpackaging.python.orgpaddle-model-ecology.bj.bcebos.compbs.twimg.compendulum.eustace.iopenghao-bdsc.github.iopeps.python.orgplatform.claude.complatform.openai.complg.uwaterloo.caproceedings.neurips.ccprosemirror.netproto-plus-python.readthedocs.iopublic.ukp.informatik.tu-darmstadt.depurl.oclc.orgpurl.orgpydantic-docs.helpmanual.iopyjwt.readthedocs.iopymysql.readthedocs.iopypi.orgpypika.readthedocs.iopyscript.github.iopython-devtools.helpmanual.iopython-etcd3.readthedocs.iopython-oracledb.readthedocs.iopython.langchain.compython.orgpythonhosted.orgpytorch.orgqianwen-res.oss-cn-beijing.aliyuncs.comqwenlm.github.ioraw.githubusercontent.comredis.comredis.ioredis.readthedocs.ioredisearch.ioreference.langchain.comreplit.comrequests.readthedocs.iorestrictedpython.readthedocs.iorich.readthedocs.iorrc.cvc.uab.ess.jina.ais3.amazonaws.comsafetensors-convert.hf.spacesans-io.readthedocs.iosbert.netschema.orgschemas.microsoft.comschemas.openid.netschemas.openxmlformats.orgschemas.zwobble.orgsearch.azure.comsearchapi.api.cloud.yandex.netserpapi.comsethmlarson.devsheetjs.openxmlformats.orgsmith.langchain.comsocket.iosourceforge.netspdx.devspec.openapis.orgsqlalche.mesqlite.orgstackoverflow.comstorage.azure.comstorage.googleapis.comstorage.mtls.googleapis.comstuk.github.iosuno-ai.notion.siteswagger.ioswanlab.cntartarus.orgtechnet.microsoft.comtechspot.zzzeek.orgthumbs.dreamstime.comtimeapi.iotools.ietf.orgtowardsdatascience.comtwitter.comtyper.tiangolo.comunpkg.comurllib3.readthedocs.iovega.github.iowebsockets.readthedocs.iowicg.github.iowww.aclweb.orgwww.apache.orgwww.comet.comwww.cs.cmu.eduwww.datalab.towww.deepmind.comwww.dvc.orgwww.example.珠宝www.freetds.orgwww.gevent.orgwww.github.comwww.google.comwww.googleapis.comwww.gravatar.comwww.gutenberg.orgwww.iana.orgwww.ietf.orgwww.ilankelman.orgwww.iso.orgwww.kxan.comwww.microsoft.comwww.mlflow.orgwww.mozilla.orgwww.nature.comwww.npmjs.comwww.opentable.comwww.oracle.comwww.paddleocr.aiwww.postgresql.orgwww.psycopg.orgwww.python.orgwww.researchgate.netwww.rethinkdb.comwww.rfc-editor.orgwww.sbert.netwww.searchapi.iowww.sqlite.orgwww.starlette.devwww.starlette.iowww.tensorflow.orgwww.w3.orgwww.wandb.comwww.xudongz.comwww.youtube-nocookie.comwww.youtube.comwww.zetetic.netxn--fiqs8s.icom.museumydc-index.ioyour-company.comyoutu.beyoutube.com
- 1source
repo/backend/open_webui/retrieval/loaders/datalab_marker.py:69 - 2sink
repo/backend/open_webui/retrieval/loaders/datalab_marker.py:71
- 1source
repo/backend/open_webui/retrieval/loaders/datalab_marker.py:89 - 2sink
repo/backend/open_webui/retrieval/loaders/datalab_marker.py:116
- 1source
repo/backend/open_webui/retrieval/loaders/datalab_marker.py:89 - 2sink
repo/backend/open_webui/retrieval/loaders/datalab_marker.py:147
- 1source
repo/backend/open_webui/retrieval/loaders/external_document.py:45 - 2sink
repo/backend/open_webui/retrieval/loaders/external_document.py:62
- 1source
repo/backend/open_webui/retrieval/loaders/main.py:195 - 2sink
repo/backend/open_webui/retrieval/loaders/main.py:211
- 1source
repo/backend/open_webui/retrieval/loaders/microsoft_web_iq.py:52 - 2sink
repo/backend/open_webui/retrieval/loaders/microsoft_web_iq.py:73
- 1source
repo/backend/open_webui/retrieval/loaders/mineru.py:216 - 2sink
repo/backend/open_webui/retrieval/loaders/mineru.py:241
- 1source
repo/backend/open_webui/retrieval/loaders/mineru.py:331 - 2sink
repo/backend/open_webui/retrieval/loaders/mineru.py:343
- 1source
repo/backend/open_webui/retrieval/loaders/paddleocr_vl.py:45 - 2sink
repo/backend/open_webui/retrieval/loaders/paddleocr_vl.py:61
- 1source
repo/backend/open_webui/retrieval/loaders/tavily.py:61 - 2sink
repo/backend/open_webui/retrieval/loaders/tavily.py:67
- 1source
repo/backend/open_webui/retrieval/models/external.py:43 - 2sink
repo/backend/open_webui/retrieval/models/external.py:51
hub Dependency data flows (643)
- 1source
pkgs/python/[email protected]/src/transformers/integrations/integration_utils.py:2444 - 2sink
pkgs/python/[email protected]/src/transformers/integrations/integration_utils.py:2446
- 1source
pkgs/python/[email protected]/azure/identity/_credentials/environment.py:66 - 2sink
pkgs/python/[email protected]/azure/identity/_credentials/environment.py:99
- 1source
pkgs/python/[email protected]/azure/identity/aio/_credentials/environment.py:60 - 2sink
pkgs/python/[email protected]/azure/identity/aio/_credentials/environment.py:77
- 1source
pkgs/python/[email protected]/samples/sample_agentic_retrieval.py:45 - 2sink
pkgs/python/[email protected]/samples/sample_agentic_retrieval.py:70
- 1source
pkgs/python/[email protected]/samples/sample_agentic_retrieval.py:45 - 2sink
pkgs/python/[email protected]/samples/sample_agentic_retrieval.py:127
- 1source
pkgs/python/[email protected]/samples/sample_agentic_retrieval_async.py:46 - 2sink
pkgs/python/[email protected]/samples/sample_agentic_retrieval_async.py:73
- 1source
pkgs/python/[email protected]/samples/sample_agentic_retrieval_async.py:46 - 2sink
pkgs/python/[email protected]/samples/sample_agentic_retrieval_async.py:134
- 1source
pkgs/python/[email protected]/samples/sample_authentication.py:32 - 2sink
pkgs/python/[email protected]/samples/sample_authentication.py:39
- 1source
pkgs/python/[email protected]/samples/sample_authentication.py:48 - 2sink
pkgs/python/[email protected]/samples/sample_authentication.py:55
- 1source
pkgs/python/[email protected]/samples/sample_authentication_async.py:33 - 2sink
pkgs/python/[email protected]/samples/sample_authentication_async.py:41
- 1source
pkgs/python/[email protected]/samples/sample_authentication_async.py:50 - 2sink
pkgs/python/[email protected]/samples/sample_authentication_async.py:58
- 1source
pkgs/python/[email protected]/samples/sample_documents_crud.py:26 - 2sink
pkgs/python/[email protected]/samples/sample_documents_crud.py:59
- 1source
pkgs/python/[email protected]/samples/sample_documents_crud.py:26 - 2sink
pkgs/python/[email protected]/samples/sample_documents_crud.py:72
- 1source
pkgs/python/[email protected]/samples/sample_documents_crud.py:26 - 2sink
pkgs/python/[email protected]/samples/sample_documents_crud.py:87
- 1source
pkgs/python/[email protected]/samples/sample_documents_crud.py:26 - 2sink
pkgs/python/[email protected]/samples/sample_documents_crud.py:100
- 1source
pkgs/python/[email protected]/samples/sample_documents_crud.py:26 - 2sink
pkgs/python/[email protected]/samples/sample_documents_crud.py:115
- 1source
pkgs/python/[email protected]/samples/sample_documents_crud_async.py:27 - 2sink
pkgs/python/[email protected]/samples/sample_documents_crud_async.py:61
- 1source
pkgs/python/[email protected]/samples/sample_documents_crud_async.py:27 - 2sink
pkgs/python/[email protected]/samples/sample_documents_crud_async.py:77
- 1source
pkgs/python/[email protected]/samples/sample_documents_crud_async.py:27 - 2sink
pkgs/python/[email protected]/samples/sample_documents_crud_async.py:93
- 1source
pkgs/python/[email protected]/samples/sample_documents_crud_async.py:27 - 2sink
pkgs/python/[email protected]/samples/sample_documents_crud_async.py:107
- 1source
pkgs/python/[email protected]/samples/sample_documents_crud_async.py:27 - 2sink
pkgs/python/[email protected]/samples/sample_documents_crud_async.py:123
- 1source
pkgs/python/[email protected]/samples/sample_index_alias_crud.py:27 - 2sink
pkgs/python/[email protected]/samples/sample_index_alias_crud.py:42
- 1source
pkgs/python/[email protected]/samples/sample_index_alias_crud.py:27 - 2sink
pkgs/python/[email protected]/samples/sample_index_alias_crud.py:54
- 1source
pkgs/python/[email protected]/samples/sample_index_alias_crud.py:27 - 2sink
pkgs/python/[email protected]/samples/sample_index_alias_crud.py:108
- 1source
pkgs/python/[email protected]/samples/sample_index_alias_crud_async.py:28 - 2sink
pkgs/python/[email protected]/samples/sample_index_alias_crud_async.py:44
- 1source
pkgs/python/[email protected]/samples/sample_index_alias_crud_async.py:28 - 2sink
pkgs/python/[email protected]/samples/sample_index_alias_crud_async.py:57
- 1source
pkgs/python/[email protected]/samples/sample_index_alias_crud_async.py:28 - 2sink
pkgs/python/[email protected]/samples/sample_index_alias_crud_async.py:112
- 1source
pkgs/python/[email protected]/samples/sample_index_analyze_text.py:26 - 2sink
pkgs/python/[email protected]/samples/sample_index_analyze_text.py:43
- 1source
pkgs/python/[email protected]/samples/sample_index_analyze_text_async.py:27 - 2sink
pkgs/python/[email protected]/samples/sample_index_analyze_text_async.py:45
- 1source
pkgs/python/[email protected]/samples/sample_index_client_custom_request.py:33 - 2sink
pkgs/python/[email protected]/samples/sample_index_client_custom_request.py:46
- 1source
pkgs/python/[email protected]/samples/sample_index_client_custom_request_async.py:37 - 2sink
pkgs/python/[email protected]/samples/sample_index_client_custom_request_async.py:51
- 1source
pkgs/python/[email protected]/samples/sample_index_crud.py:26 - 2sink
pkgs/python/[email protected]/samples/sample_index_crud.py:69
- 1source
pkgs/python/[email protected]/samples/sample_index_crud.py:26 - 2sink
pkgs/python/[email protected]/samples/sample_index_crud.py:80
- 1source
pkgs/python/[email protected]/samples/sample_index_crud.py:26 - 2sink
pkgs/python/[email protected]/samples/sample_index_crud.py:126
- 1source
pkgs/python/[email protected]/samples/sample_index_crud.py:26 - 2sink
pkgs/python/[email protected]/samples/sample_index_crud.py:139
- 1source
pkgs/python/[email protected]/samples/sample_index_crud_async.py:27 - 2sink
pkgs/python/[email protected]/samples/sample_index_crud_async.py:72
- 1source
pkgs/python/[email protected]/samples/sample_index_crud_async.py:27 - 2sink
pkgs/python/[email protected]/samples/sample_index_crud_async.py:84
- 1source
pkgs/python/[email protected]/samples/sample_index_crud_async.py:27 - 2sink
pkgs/python/[email protected]/samples/sample_index_crud_async.py:132
- 1source
pkgs/python/[email protected]/samples/sample_index_synonym_map_crud.py:23 - 2sink
pkgs/python/[email protected]/samples/sample_index_synonym_map_crud.py:43
- 1source
pkgs/python/[email protected]/samples/sample_index_synonym_map_crud.py:23 - 2sink
pkgs/python/[email protected]/samples/sample_index_synonym_map_crud.py:59
- 1source
pkgs/python/[email protected]/samples/sample_index_synonym_map_crud.py:23 - 2sink
pkgs/python/[email protected]/samples/sample_index_synonym_map_crud.py:71
- 1source
pkgs/python/[email protected]/samples/sample_index_synonym_map_crud.py:23 - 2sink
pkgs/python/[email protected]/samples/sample_index_synonym_map_crud.py:85
- 1source
pkgs/python/[email protected]/samples/sample_index_synonym_map_crud_async.py:24 - 2sink
pkgs/python/[email protected]/samples/sample_index_synonym_map_crud_async.py:45
- 1source
pkgs/python/[email protected]/samples/sample_index_synonym_map_crud_async.py:24 - 2sink
pkgs/python/[email protected]/samples/sample_index_synonym_map_crud_async.py:62
- 1source
pkgs/python/[email protected]/samples/sample_index_synonym_map_crud_async.py:24 - 2sink
pkgs/python/[email protected]/samples/sample_index_synonym_map_crud_async.py:75
- 1source
pkgs/python/[email protected]/samples/sample_index_synonym_map_crud_async.py:24 - 2sink
pkgs/python/[email protected]/samples/sample_index_synonym_map_crud_async.py:90
- 1source
pkgs/python/[email protected]/samples/sample_indexer_crud.py:25 - 2sink
pkgs/python/[email protected]/samples/sample_indexer_crud.py:74
- 1source
pkgs/python/[email protected]/samples/sample_indexer_crud.py:25 - 2sink
pkgs/python/[email protected]/samples/sample_indexer_crud.py:87
- 1source
pkgs/python/[email protected]/samples/sample_indexer_crud.py:25 - 2sink
pkgs/python/[email protected]/samples/sample_indexer_crud.py:99
- 1source
pkgs/python/[email protected]/samples/sample_indexer_crud.py:25 - 2sink
pkgs/python/[email protected]/samples/sample_indexer_crud.py:112
- 1source
pkgs/python/[email protected]/samples/sample_indexer_crud_async.py:26 - 2sink
pkgs/python/[email protected]/samples/sample_indexer_crud_async.py:80
- 1source
pkgs/python/[email protected]/samples/sample_indexer_crud_async.py:26 - 2sink
pkgs/python/[email protected]/samples/sample_indexer_crud_async.py:94
- 1source
pkgs/python/[email protected]/samples/sample_indexer_crud_async.py:26 - 2sink
pkgs/python/[email protected]/samples/sample_indexer_crud_async.py:107
- 1source
pkgs/python/[email protected]/samples/sample_indexer_crud_async.py:26 - 2sink
pkgs/python/[email protected]/samples/sample_indexer_crud_async.py:121
- 1source
pkgs/python/[email protected]/samples/sample_indexer_datasource_crud.py:25 - 2sink
pkgs/python/[email protected]/samples/sample_indexer_datasource_crud.py:51
- 1source
pkgs/python/[email protected]/samples/sample_indexer_datasource_crud.py:25 - 2sink
pkgs/python/[email protected]/samples/sample_indexer_datasource_crud.py:64
- 1source
pkgs/python/[email protected]/samples/sample_indexer_datasource_crud.py:25 - 2sink
pkgs/python/[email protected]/samples/sample_indexer_datasource_crud.py:76
- 1source
pkgs/python/[email protected]/samples/sample_indexer_datasource_crud_async.py:26 - 2sink
pkgs/python/[email protected]/samples/sample_indexer_datasource_crud_async.py:52
- 1source
pkgs/python/[email protected]/samples/sample_indexer_datasource_crud_async.py:26 - 2sink
pkgs/python/[email protected]/samples/sample_indexer_datasource_crud_async.py:66
- 1source
pkgs/python/[email protected]/samples/sample_indexer_datasource_crud_async.py:26 - 2sink
pkgs/python/[email protected]/samples/sample_indexer_datasource_crud_async.py:79
- 1source
pkgs/python/[email protected]/samples/sample_indexer_workflow.py:25 - 2sink
pkgs/python/[email protected]/samples/sample_indexer_workflow.py:119
- 1source
pkgs/python/[email protected]/samples/sample_indexer_workflow.py:25 - 2sink
pkgs/python/[email protected]/samples/sample_indexer_workflow.py:130
- 1source
pkgs/python/[email protected]/samples/sample_indexer_workflow.py:25 - 2sink
pkgs/python/[email protected]/samples/sample_indexer_workflow.py:134
- 1source
pkgs/python/[email protected]/samples/sample_query_autocomplete.py:26 - 2sink
pkgs/python/[email protected]/samples/sample_query_autocomplete.py:40
- 1source
pkgs/python/[email protected]/samples/sample_query_autocomplete_async.py:28 - 2sink
pkgs/python/[email protected]/samples/sample_query_autocomplete_async.py:43
- 1source
pkgs/python/[email protected]/samples/sample_query_facets.py:26 - 2sink
pkgs/python/[email protected]/samples/sample_query_facets.py:43
- 1source
pkgs/python/[email protected]/samples/sample_query_facets_async.py:28 - 2sink
pkgs/python/[email protected]/samples/sample_query_facets_async.py:46
- 1source
pkgs/python/[email protected]/samples/sample_query_filter.py:26 - 2sink
pkgs/python/[email protected]/samples/sample_query_filter.py:45
- 1source
pkgs/python/[email protected]/samples/sample_query_filter_async.py:28 - 2sink
pkgs/python/[email protected]/samples/sample_query_filter_async.py:48
- 1source
pkgs/python/[email protected]/samples/sample_query_semantic.py:24 - 2sink
pkgs/python/[email protected]/samples/sample_query_semantic.py:66
- 1source
pkgs/python/[email protected]/samples/sample_query_semantic.py:24 - 2sink
pkgs/python/[email protected]/samples/sample_query_semantic.py:67
- 1source
pkgs/python/[email protected]/samples/sample_query_semantic.py:24 - 2sink
pkgs/python/[email protected]/samples/sample_query_semantic.py:89
- 1source
pkgs/python/[email protected]/samples/sample_query_semantic.py:24 - 2sink
pkgs/python/[email protected]/samples/sample_query_semantic.py:90
- 1source
pkgs/python/[email protected]/samples/sample_query_semantic_async.py:25 - 2sink
pkgs/python/[email protected]/samples/sample_query_semantic_async.py:69
- 1source
pkgs/python/[email protected]/samples/sample_query_semantic_async.py:25 - 2sink
pkgs/python/[email protected]/samples/sample_query_semantic_async.py:70
- 1source
pkgs/python/[email protected]/samples/sample_query_semantic_async.py:25 - 2sink
pkgs/python/[email protected]/samples/sample_query_semantic_async.py:91
- 1source
pkgs/python/[email protected]/samples/sample_query_semantic_async.py:25 - 2sink
pkgs/python/[email protected]/samples/sample_query_semantic_async.py:92
- 1source
pkgs/python/[email protected]/samples/sample_query_session.py:24 - 2sink
pkgs/python/[email protected]/samples/sample_query_session.py:38
- 1source
pkgs/python/[email protected]/samples/sample_query_session_async.py:25 - 2sink
pkgs/python/[email protected]/samples/sample_query_session_async.py:40
- 1source
pkgs/python/[email protected]/samples/sample_query_simple.py:24 - 2sink
pkgs/python/[email protected]/samples/sample_query_simple.py:38
- 1source
pkgs/python/[email protected]/samples/sample_query_simple_async.py:26 - 2sink
pkgs/python/[email protected]/samples/sample_query_simple_async.py:41
- 1source
pkgs/python/[email protected]/samples/sample_query_suggestions.py:24 - 2sink
pkgs/python/[email protected]/samples/sample_query_suggestions.py:39
- 1source
pkgs/python/[email protected]/samples/sample_query_suggestions_async.py:26 - 2sink
pkgs/python/[email protected]/samples/sample_query_suggestions_async.py:42
- 1source
pkgs/python/[email protected]/samples/sample_query_vector.py:50 - 2sink
pkgs/python/[email protected]/samples/sample_query_vector.py:130
- 1source
pkgs/python/[email protected]/samples/sample_query_vector.py:50 - 2sink
pkgs/python/[email protected]/samples/sample_query_vector.py:148
- 1source
pkgs/python/[email protected]/samples/sample_query_vector.py:50 - 2sink
pkgs/python/[email protected]/samples/sample_query_vector.py:170
- 1source
pkgs/python/[email protected]/samples/sample_query_vector.py:50 - 2sink
pkgs/python/[email protected]/samples/sample_query_vector.py:196
- 1source
pkgs/python/[email protected]/samples/sample_query_vector.py:50 - 2sink
pkgs/python/[email protected]/samples/sample_query_vector.py:221
- 1source
pkgs/python/[email protected]/samples/sample_query_vector.py:50 - 2sink
pkgs/python/[email protected]/samples/sample_query_vector.py:222
- 1source
pkgs/python/[email protected]/samples/sample_query_vector.py:50 - 2sink
pkgs/python/[email protected]/samples/sample_query_vector.py:223
- 1source
pkgs/python/[email protected]/samples/sample_query_vector.py:50 - 2sink
pkgs/python/[email protected]/samples/sample_query_vector.py:224
- 1source
pkgs/python/[email protected]/samples/sample_query_vector.py:50 - 2sink
pkgs/python/[email protected]/samples/sample_query_vector.py:225
- 1source
pkgs/python/[email protected]/samples/sample_query_vector.py:50 - 2sink
pkgs/python/[email protected]/samples/sample_query_vector.py:226
- 1source
pkgs/python/[email protected]/samples/sample_query_vector_async.py:52 - 2sink
pkgs/python/[email protected]/samples/sample_query_vector_async.py:134
- 1source
pkgs/python/[email protected]/samples/sample_query_vector_async.py:52 - 2sink
pkgs/python/[email protected]/samples/sample_query_vector_async.py:153
- 1source
pkgs/python/[email protected]/samples/sample_query_vector_async.py:52 - 2sink
pkgs/python/[email protected]/samples/sample_query_vector_async.py:176
- 1source
pkgs/python/[email protected]/samples/sample_query_vector_async.py:52 - 2sink
pkgs/python/[email protected]/samples/sample_query_vector_async.py:204
- 1source
pkgs/python/[email protected]/samples/sample_query_vector_async.py:52 - 2sink
pkgs/python/[email protected]/samples/sample_query_vector_async.py:230
- 1source
pkgs/python/[email protected]/samples/sample_query_vector_async.py:52 - 2sink
pkgs/python/[email protected]/samples/sample_query_vector_async.py:231
- 1source
pkgs/python/[email protected]/samples/sample_query_vector_async.py:52 - 2sink
pkgs/python/[email protected]/samples/sample_query_vector_async.py:232
- 1source
pkgs/python/[email protected]/samples/sample_query_vector_async.py:52 - 2sink
pkgs/python/[email protected]/samples/sample_query_vector_async.py:233
- 1source
pkgs/python/[email protected]/samples/sample_query_vector_async.py:52 - 2sink
pkgs/python/[email protected]/samples/sample_query_vector_async.py:234
- 1source
pkgs/python/[email protected]/samples/sample_query_vector_async.py:52 - 2sink
pkgs/python/[email protected]/samples/sample_query_vector_async.py:235
- 1source
pkgs/python/[email protected]/samples/sample_search_client_custom_request.py:25 - 2sink
pkgs/python/[email protected]/samples/sample_search_client_custom_request.py:42
- 1source
pkgs/python/[email protected]/samples/sample_search_client_custom_request_async.py:26 - 2sink
pkgs/python/[email protected]/samples/sample_search_client_custom_request_async.py:48
- 1source
pkgs/python/[email protected]/samples/async_samples/sample_analyze_addon_barcodes_async.py:66 - 2sink
pkgs/python/[email protected]/samples/async_samples/sample_analyze_addon_barcodes_async.py:82
- 1source
pkgs/python/[email protected]/samples/async_samples/sample_analyze_addon_barcodes_async.py:66 - 2sink
pkgs/python/[email protected]/samples/async_samples/sample_analyze_addon_barcodes_async.py:84
- 1source
pkgs/python/[email protected]/samples/async_samples/sample_analyze_addon_barcodes_async.py:66 - 2sink
pkgs/python/[email protected]/samples/async_samples/sample_analyze_addon_barcodes_async.py:86
- 1source
pkgs/python/[email protected]/samples/async_samples/sample_analyze_addon_barcodes_async.py:66 - 2sink
pkgs/python/[email protected]/samples/async_samples/sample_analyze_addon_barcodes_async.py:87
- 1source
pkgs/python/[email protected]/samples/async_samples/sample_analyze_addon_barcodes_async.py:66 - 2sink
pkgs/python/[email protected]/samples/async_samples/sample_analyze_addon_barcodes_async.py:88
- 1source
pkgs/python/[email protected]/samples/async_samples/sample_analyze_addon_barcodes_async.py:66 - 2sink
pkgs/python/[email protected]/samples/async_samples/sample_analyze_addon_barcodes_async.py:89
- 1source
pkgs/python/[email protected]/samples/async_samples/sample_analyze_addon_fonts_async.py:68 - 2sink
pkgs/python/[email protected]/samples/async_samples/sample_analyze_addon_fonts_async.py:112
- 1source
pkgs/python/[email protected]/samples/async_samples/sample_analyze_addon_fonts_async.py:68 - 2sink
pkgs/python/[email protected]/samples/async_samples/sample_analyze_addon_fonts_async.py:117
- 1source
pkgs/python/[email protected]/samples/async_samples/sample_analyze_addon_fonts_async.py:68 - 2sink
pkgs/python/[email protected]/samples/async_samples/sample_analyze_addon_fonts_async.py:122
- 1source
pkgs/python/[email protected]/samples/async_samples/sample_analyze_addon_fonts_async.py:68 - 2sink
pkgs/python/[email protected]/samples/async_samples/sample_analyze_addon_fonts_async.py:127
- 1source
pkgs/python/[email protected]/samples/async_samples/sample_analyze_addon_fonts_async.py:68 - 2sink
pkgs/python/[email protected]/samples/async_samples/sample_analyze_addon_fonts_async.py:132
- 1source
pkgs/python/[email protected]/samples/async_samples/sample_analyze_addon_formulas_async.py:66 - 2sink
pkgs/python/[email protected]/samples/async_samples/sample_analyze_addon_formulas_async.py:83
- 1source
pkgs/python/[email protected]/samples/async_samples/sample_analyze_addon_formulas_async.py:66 - 2sink
pkgs/python/[email protected]/samples/async_samples/sample_analyze_addon_formulas_async.py:88
- 1source
pkgs/python/[email protected]/samples/async_samples/sample_analyze_addon_formulas_async.py:66 - 2sink
pkgs/python/[email protected]/samples/async_samples/sample_analyze_addon_formulas_async.py:90
- 1source
pkgs/python/[email protected]/samples/async_samples/sample_analyze_addon_formulas_async.py:66 - 2sink
pkgs/python/[email protected]/samples/async_samples/sample_analyze_addon_formulas_async.py:91
- 1source
pkgs/python/[email protected]/samples/async_samples/sample_analyze_addon_formulas_async.py:66 - 2sink
pkgs/python/[email protected]/samples/async_samples/sample_analyze_addon_formulas_async.py:92
- 1source
pkgs/python/[email protected]/samples/async_samples/sample_analyze_addon_formulas_async.py:66 - 2sink
pkgs/python/[email protected]/samples/async_samples/sample_analyze_addon_formulas_async.py:94
- 1source
pkgs/python/[email protected]/samples/async_samples/sample_analyze_addon_formulas_async.py:66 - 2sink
pkgs/python/[email protected]/samples/async_samples/sample_analyze_addon_formulas_async.py:96
- 1source
pkgs/python/[email protected]/samples/async_samples/sample_analyze_addon_formulas_async.py:66 - 2sink
pkgs/python/[email protected]/samples/async_samples/sample_analyze_addon_formulas_async.py:97
- 1source
pkgs/python/[email protected]/samples/async_samples/sample_analyze_addon_formulas_async.py:66 - 2sink
pkgs/python/[email protected]/samples/async_samples/sample_analyze_addon_formulas_async.py:98
- 1source
pkgs/python/[email protected]/samples/async_samples/sample_analyze_addon_highres_async.py:81 - 2sink
pkgs/python/[email protected]/samples/async_samples/sample_analyze_addon_highres_async.py:101
- 1source
pkgs/python/[email protected]/samples/async_samples/sample_analyze_addon_highres_async.py:81 - 2sink
pkgs/python/[email protected]/samples/async_samples/sample_analyze_addon_highres_async.py:102
- 1source
pkgs/python/[email protected]/samples/async_samples/sample_analyze_addon_highres_async.py:81 - 2sink
pkgs/python/[email protected]/samples/async_samples/sample_analyze_addon_highres_async.py:107
- 1source
pkgs/python/[email protected]/samples/async_samples/sample_analyze_addon_highres_async.py:81 - 2sink
pkgs/python/[email protected]/samples/async_samples/sample_analyze_addon_highres_async.py:114
- 1source
pkgs/python/[email protected]/samples/async_samples/sample_analyze_addon_highres_async.py:81 - 2sink
pkgs/python/[email protected]/samples/async_samples/sample_analyze_addon_highres_async.py:118
- 1source
pkgs/python/[email protected]/samples/async_samples/sample_analyze_addon_highres_async.py:81 - 2sink
pkgs/python/[email protected]/samples/async_samples/sample_analyze_addon_highres_async.py:125
- 1source
pkgs/python/[email protected]/samples/async_samples/sample_analyze_addon_highres_async.py:81 - 2sink
pkgs/python/[email protected]/samples/async_samples/sample_analyze_addon_highres_async.py:128
- 1source
pkgs/python/[email protected]/samples/async_samples/sample_analyze_addon_highres_async.py:81 - 2sink
pkgs/python/[email protected]/samples/async_samples/sample_analyze_addon_highres_async.py:132
- 1source
pkgs/python/[email protected]/samples/async_samples/sample_analyze_addon_highres_async.py:81 - 2sink
pkgs/python/[email protected]/samples/async_samples/sample_analyze_addon_highres_async.py:135
- 1source
pkgs/python/[email protected]/samples/async_samples/sample_analyze_addon_languages_async.py:60 - 2sink
pkgs/python/[email protected]/samples/async_samples/sample_analyze_addon_languages_async.py:76
- 1source
pkgs/python/[email protected]/samples/async_samples/sample_analyze_addon_languages_async.py:60 - 2sink
pkgs/python/[email protected]/samples/async_samples/sample_analyze_addon_languages_async.py:78
- 1source
pkgs/python/[email protected]/samples/async_samples/sample_analyze_addon_languages_async.py:60 - 2sink
pkgs/python/[email protected]/samples/async_samples/sample_analyze_addon_languages_async.py:79
- 1source
pkgs/python/[email protected]/samples/async_samples/sample_analyze_addon_query_fields_async.py:52 - 2sink
pkgs/python/[email protected]/samples/async_samples/sample_analyze_addon_query_fields_async.py:70
- 1source
pkgs/python/[email protected]/samples/async_samples/sample_analyze_addon_query_fields_async.py:52 - 2sink
pkgs/python/[email protected]/samples/async_samples/sample_analyze_addon_query_fields_async.py:72
- 1source
pkgs/python/[email protected]/samples/async_samples/sample_analyze_batch_documents_async.py:54 - 2sink
pkgs/python/[email protected]/samples/async_samples/sample_analyze_batch_documents_async.py:77
- 1source
pkgs/python/[email protected]/samples/async_samples/sample_analyze_batch_documents_async.py:54 - 2sink
pkgs/python/[email protected]/samples/async_samples/sample_analyze_batch_documents_async.py:78
- 1source
pkgs/python/[email protected]/samples/async_samples/sample_analyze_batch_documents_async.py:54 - 2sink
pkgs/python/[email protected]/samples/async_samples/sample_analyze_batch_documents_async.py:79
- 1source
pkgs/python/[email protected]/samples/async_samples/sample_analyze_custom_documents_async.py:66 - 2sink
pkgs/python/[email protected]/samples/async_samples/sample_analyze_custom_documents_async.py:78
- 1source
pkgs/python/[email protected]/samples/async_samples/sample_analyze_custom_documents_async.py:66 - 2sink
pkgs/python/[email protected]/samples/async_samples/sample_analyze_custom_documents_async.py:79
- 1source
pkgs/python/[email protected]/samples/async_samples/sample_analyze_custom_documents_async.py:66 - 2sink
pkgs/python/[email protected]/samples/async_samples/sample_analyze_custom_documents_async.py:80
- 1source
pkgs/python/[email protected]/samples/async_samples/sample_analyze_custom_documents_async.py:66 - 2sink
pkgs/python/[email protected]/samples/async_samples/sample_analyze_custom_documents_async.py:81
- 1source
pkgs/python/[email protected]/samples/async_samples/sample_analyze_custom_documents_async.py:66 - 2sink
pkgs/python/[email protected]/samples/async_samples/sample_analyze_custom_documents_async.py:85
- 1source
pkgs/python/[email protected]/samples/async_samples/sample_analyze_documents_output_in_markdown_async.py:33 - 2sink
pkgs/python/[email protected]/samples/async_samples/sample_analyze_documents_output_in_markdown_async.py:45
- 1source
pkgs/python/[email protected]/samples/async_samples/sample_analyze_documents_output_in_markdown_async.py:33 - 2sink
pkgs/python/[email protected]/samples/async_samples/sample_analyze_documents_output_in_markdown_async.py:46
- 1source
pkgs/python/[email protected]/samples/async_samples/sample_analyze_general_documents_async.py:70 - 2sink
pkgs/python/[email protected]/samples/async_samples/sample_analyze_general_documents_async.py:92
- 1source
pkgs/python/[email protected]/samples/async_samples/sample_analyze_general_documents_async.py:70 - 2sink
pkgs/python/[email protected]/samples/async_samples/sample_analyze_general_documents_async.py:97
- 1source
pkgs/python/[email protected]/samples/async_samples/sample_analyze_general_documents_async.py:70 - 2sink
pkgs/python/[email protected]/samples/async_samples/sample_analyze_general_documents_async.py:103
- 1source
pkgs/python/[email protected]/samples/async_samples/sample_analyze_general_documents_async.py:70 - 2sink
pkgs/python/[email protected]/samples/async_samples/sample_analyze_general_documents_async.py:104
- 1source
pkgs/python/[email protected]/samples/async_samples/sample_analyze_general_documents_async.py:70 - 2sink
pkgs/python/[email protected]/samples/async_samples/sample_analyze_general_documents_async.py:109
- 1source
pkgs/python/[email protected]/samples/async_samples/sample_analyze_general_documents_async.py:70 - 2sink
pkgs/python/[email protected]/samples/async_samples/sample_analyze_general_documents_async.py:116
- 1source
pkgs/python/[email protected]/samples/async_samples/sample_analyze_general_documents_async.py:70 - 2sink
pkgs/python/[email protected]/samples/async_samples/sample_analyze_general_documents_async.py:120
- 1source
pkgs/python/[email protected]/samples/async_samples/sample_analyze_general_documents_async.py:70 - 2sink
pkgs/python/[email protected]/samples/async_samples/sample_analyze_general_documents_async.py:128
- 1source
pkgs/python/[email protected]/samples/async_samples/sample_analyze_general_documents_async.py:70 - 2sink
pkgs/python/[email protected]/samples/async_samples/sample_analyze_general_documents_async.py:131
- 1source
pkgs/python/[email protected]/samples/async_samples/sample_analyze_general_documents_async.py:70 - 2sink
pkgs/python/[email protected]/samples/async_samples/sample_analyze_general_documents_async.py:135
- 1source
pkgs/python/[email protected]/samples/async_samples/sample_analyze_general_documents_async.py:70 - 2sink
pkgs/python/[email protected]/samples/async_samples/sample_analyze_general_documents_async.py:138
- 1source
pkgs/python/[email protected]/samples/async_samples/sample_analyze_identity_documents_async.py:45 - 2sink
pkgs/python/[email protected]/samples/async_samples/sample_analyze_identity_documents_async.py:55
- 1source
pkgs/python/[email protected]/samples/async_samples/sample_analyze_identity_documents_async.py:45 - 2sink
pkgs/python/[email protected]/samples/async_samples/sample_analyze_identity_documents_async.py:59
- 1source
pkgs/python/[email protected]/samples/async_samples/sample_analyze_identity_documents_async.py:45 - 2sink
pkgs/python/[email protected]/samples/async_samples/sample_analyze_identity_documents_async.py:62
- 1source
pkgs/python/[email protected]/samples/async_samples/sample_analyze_identity_documents_async.py:45 - 2sink
pkgs/python/[email protected]/samples/async_samples/sample_analyze_identity_documents_async.py:65
- 1source
pkgs/python/[email protected]/samples/async_samples/sample_analyze_identity_documents_async.py:45 - 2sink
pkgs/python/[email protected]/samples/async_samples/sample_analyze_identity_documents_async.py:70
- 1source
pkgs/python/[email protected]/samples/async_samples/sample_analyze_identity_documents_async.py:45 - 2sink
pkgs/python/[email protected]/samples/async_samples/sample_analyze_identity_documents_async.py:73
- 1source
pkgs/python/[email protected]/samples/async_samples/sample_analyze_identity_documents_async.py:45 - 2sink
pkgs/python/[email protected]/samples/async_samples/sample_analyze_identity_documents_async.py:76
- 1source
pkgs/python/[email protected]/samples/async_samples/sample_analyze_identity_documents_async.py:45 - 2sink
pkgs/python/[email protected]/samples/async_samples/sample_analyze_identity_documents_async.py:79
- 1source
pkgs/python/[email protected]/samples/async_samples/sample_analyze_identity_documents_async.py:45 - 2sink
pkgs/python/[email protected]/samples/async_samples/sample_analyze_identity_documents_async.py:82
- 1source
pkgs/python/[email protected]/samples/async_samples/sample_analyze_identity_documents_async.py:45 - 2sink
pkgs/python/[email protected]/samples/async_samples/sample_analyze_identity_documents_async.py:87
- 1source
pkgs/python/[email protected]/samples/async_samples/sample_analyze_invoices_async.py:45 - 2sink
pkgs/python/[email protected]/samples/async_samples/sample_analyze_invoices_async.py:57
- 1source
pkgs/python/[email protected]/samples/async_samples/sample_analyze_invoices_async.py:45 - 2sink
pkgs/python/[email protected]/samples/async_samples/sample_analyze_invoices_async.py:61
- 1source
pkgs/python/[email protected]/samples/async_samples/sample_analyze_invoices_async.py:45 - 2sink
pkgs/python/[email protected]/samples/async_samples/sample_analyze_invoices_async.py:64
- 1source
pkgs/python/[email protected]/samples/async_samples/sample_analyze_invoices_async.py:45 - 2sink
pkgs/python/[email protected]/samples/async_samples/sample_analyze_invoices_async.py:69
- 1source
pkgs/python/[email protected]/samples/async_samples/sample_analyze_invoices_async.py:45 - 2sink
pkgs/python/[email protected]/samples/async_samples/sample_analyze_invoices_async.py:74
- 1source
pkgs/python/[email protected]/samples/async_samples/sample_analyze_invoices_async.py:45 - 2sink
pkgs/python/[email protected]/samples/async_samples/sample_analyze_invoices_async.py:79
- 1source
pkgs/python/[email protected]/samples/async_samples/sample_analyze_invoices_async.py:45 - 2sink
pkgs/python/[email protected]/samples/async_samples/sample_analyze_invoices_async.py:82
- 1source
pkgs/python/[email protected]/samples/async_samples/sample_analyze_invoices_async.py:45 - 2sink
pkgs/python/[email protected]/samples/async_samples/sample_analyze_invoices_async.py:87
- 1source
pkgs/python/[email protected]/samples/async_samples/sample_analyze_invoices_async.py:45 - 2sink
pkgs/python/[email protected]/samples/async_samples/sample_analyze_invoices_async.py:92
- 1source
pkgs/python/[email protected]/samples/async_samples/sample_analyze_invoices_async.py:45 - 2sink
pkgs/python/[email protected]/samples/async_samples/sample_analyze_invoices_async.py:95
- 1source
pkgs/python/[email protected]/samples/async_samples/sample_analyze_invoices_async.py:45 - 2sink
pkgs/python/[email protected]/samples/async_samples/sample_analyze_invoices_async.py:100
- 1source
pkgs/python/[email protected]/samples/async_samples/sample_analyze_invoices_async.py:45 - 2sink
pkgs/python/[email protected]/samples/async_samples/sample_analyze_invoices_async.py:105
- 1source
pkgs/python/[email protected]/samples/async_samples/sample_analyze_invoices_async.py:45 - 2sink
pkgs/python/[email protected]/samples/async_samples/sample_analyze_invoices_async.py:108
- 1source
pkgs/python/[email protected]/samples/async_samples/sample_analyze_invoices_async.py:45 - 2sink
pkgs/python/[email protected]/samples/async_samples/sample_analyze_invoices_async.py:113
- 1source
pkgs/python/[email protected]/samples/async_samples/sample_analyze_invoices_async.py:45 - 2sink
pkgs/python/[email protected]/samples/async_samples/sample_analyze_invoices_async.py:118
- 1source
pkgs/python/[email protected]/samples/async_samples/sample_analyze_invoices_async.py:45 - 2sink
pkgs/python/[email protected]/samples/async_samples/sample_analyze_invoices_async.py:123
- 1source
pkgs/python/[email protected]/samples/async_samples/sample_analyze_invoices_async.py:45 - 2sink
pkgs/python/[email protected]/samples/async_samples/sample_analyze_invoices_async.py:128
- 1source
pkgs/python/[email protected]/samples/async_samples/sample_analyze_invoices_async.py:45 - 2sink
pkgs/python/[email protected]/samples/async_samples/sample_analyze_invoices_async.py:135
- 1source
pkgs/python/[email protected]/samples/async_samples/sample_analyze_invoices_async.py:45 - 2sink
pkgs/python/[email protected]/samples/async_samples/sample_analyze_invoices_async.py:138
- 1source
pkgs/python/[email protected]/samples/async_samples/sample_analyze_invoices_async.py:45 - 2sink
pkgs/python/[email protected]/samples/async_samples/sample_analyze_invoices_async.py:143
- 1source
pkgs/python/[email protected]/samples/async_samples/sample_analyze_invoices_async.py:45 - 2sink
pkgs/python/[email protected]/samples/async_samples/sample_analyze_invoices_async.py:148
- 1source
pkgs/python/[email protected]/samples/async_samples/sample_analyze_invoices_async.py:45 - 2sink
pkgs/python/[email protected]/samples/async_samples/sample_analyze_invoices_async.py:156
- 1source
pkgs/python/[email protected]/samples/async_samples/sample_analyze_invoices_async.py:45 - 2sink
pkgs/python/[email protected]/samples/async_samples/sample_analyze_invoices_async.py:161
- 1source
pkgs/python/[email protected]/samples/async_samples/sample_analyze_invoices_async.py:45 - 2sink
pkgs/python/[email protected]/samples/async_samples/sample_analyze_invoices_async.py:166
- 1source
pkgs/python/[email protected]/samples/async_samples/sample_analyze_invoices_async.py:45 - 2sink
pkgs/python/[email protected]/samples/async_samples/sample_analyze_invoices_async.py:171
- 1source
pkgs/python/[email protected]/samples/async_samples/sample_analyze_invoices_async.py:45 - 2sink
pkgs/python/[email protected]/samples/async_samples/sample_analyze_invoices_async.py:174
- 1source
pkgs/python/[email protected]/samples/async_samples/sample_analyze_invoices_async.py:45 - 2sink
pkgs/python/[email protected]/samples/async_samples/sample_analyze_invoices_async.py:177
- 1source
pkgs/python/[email protected]/samples/async_samples/sample_analyze_invoices_async.py:45 - 2sink
pkgs/python/[email protected]/samples/async_samples/sample_analyze_invoices_async.py:180
- 1source
pkgs/python/[email protected]/samples/async_samples/sample_analyze_invoices_async.py:45 - 2sink
pkgs/python/[email protected]/samples/async_samples/sample_analyze_invoices_async.py:183
- 1source
pkgs/python/[email protected]/samples/async_samples/sample_analyze_invoices_async.py:45 - 2sink
pkgs/python/[email protected]/samples/async_samples/sample_analyze_invoices_async.py:188
- 1source
pkgs/python/[email protected]/samples/async_samples/sample_analyze_invoices_async.py:45 - 2sink
pkgs/python/[email protected]/samples/async_samples/sample_analyze_invoices_async.py:191
- 1source
pkgs/python/[email protected]/samples/async_samples/sample_analyze_invoices_async.py:45 - 2sink
pkgs/python/[email protected]/samples/async_samples/sample_analyze_invoices_async.py:196
- 1source
pkgs/python/[email protected]/samples/async_samples/sample_analyze_invoices_async.py:45 - 2sink
pkgs/python/[email protected]/samples/async_samples/sample_analyze_invoices_async.py:201
- 1source
pkgs/python/[email protected]/samples/async_samples/sample_analyze_invoices_async.py:45 - 2sink
pkgs/python/[email protected]/samples/async_samples/sample_analyze_invoices_async.py:206
- 1source
pkgs/python/[email protected]/samples/async_samples/sample_analyze_invoices_async.py:45 - 2sink
pkgs/python/[email protected]/samples/async_samples/sample_analyze_invoices_async.py:211
- 1source
pkgs/python/[email protected]/samples/async_samples/sample_analyze_invoices_async.py:45 - 2sink
pkgs/python/[email protected]/samples/async_samples/sample_analyze_invoices_async.py:216
- 1source
pkgs/python/[email protected]/samples/async_samples/sample_analyze_invoices_from_bytes_source_async.py:45 - 2sink
pkgs/python/[email protected]/samples/async_samples/sample_analyze_invoices_from_bytes_source_async.py:57
- 1source
pkgs/python/[email protected]/samples/async_samples/sample_analyze_invoices_from_bytes_source_async.py:45 - 2sink
pkgs/python/[email protected]/samples/async_samples/sample_analyze_invoices_from_bytes_source_async.py:61
- 1source
pkgs/python/[email protected]/samples/async_samples/sample_analyze_invoices_from_bytes_source_async.py:45 - 2sink
pkgs/python/[email protected]/samples/async_samples/sample_analyze_invoices_from_bytes_source_async.py:64
- 1source
pkgs/python/[email protected]/samples/async_samples/sample_analyze_invoices_from_bytes_source_async.py:45 - 2sink
pkgs/python/[email protected]/samples/async_samples/sample_analyze_invoices_from_bytes_source_async.py:69
- 1source
pkgs/python/[email protected]/samples/async_samples/sample_analyze_invoices_from_bytes_source_async.py:45 - 2sink
pkgs/python/[email protected]/samples/async_samples/sample_analyze_invoices_from_bytes_source_async.py:74
- 1source
pkgs/python/[email protected]/samples/async_samples/sample_analyze_invoices_from_bytes_source_async.py:45 - 2sink
pkgs/python/[email protected]/samples/async_samples/sample_analyze_invoices_from_bytes_source_async.py:79
- 1source
pkgs/python/[email protected]/samples/async_samples/sample_analyze_invoices_from_bytes_source_async.py:45 - 2sink
pkgs/python/[email protected]/samples/async_samples/sample_analyze_invoices_from_bytes_source_async.py:82
- 1source
pkgs/python/[email protected]/samples/async_samples/sample_analyze_invoices_from_bytes_source_async.py:45 - 2sink
pkgs/python/[email protected]/samples/async_samples/sample_analyze_invoices_from_bytes_source_async.py:87
- 1source
pkgs/python/[email protected]/samples/async_samples/sample_analyze_invoices_from_bytes_source_async.py:45 - 2sink
pkgs/python/[email protected]/samples/async_samples/sample_analyze_invoices_from_bytes_source_async.py:92
- 1source
pkgs/python/[email protected]/samples/async_samples/sample_analyze_invoices_from_bytes_source_async.py:45 - 2sink
pkgs/python/[email protected]/samples/async_samples/sample_analyze_invoices_from_bytes_source_async.py:95
- 1source
pkgs/python/[email protected]/samples/async_samples/sample_analyze_invoices_from_bytes_source_async.py:45 - 2sink
pkgs/python/[email protected]/samples/async_samples/sample_analyze_invoices_from_bytes_source_async.py:100
- 1source
pkgs/python/[email protected]/samples/async_samples/sample_analyze_invoices_from_bytes_source_async.py:45 - 2sink
pkgs/python/[email protected]/samples/async_samples/sample_analyze_invoices_from_bytes_source_async.py:105
- 1source
pkgs/python/[email protected]/samples/async_samples/sample_analyze_invoices_from_bytes_source_async.py:45 - 2sink
pkgs/python/[email protected]/samples/async_samples/sample_analyze_invoices_from_bytes_source_async.py:108
- 1source
pkgs/python/[email protected]/samples/async_samples/sample_analyze_invoices_from_bytes_source_async.py:45 - 2sink
pkgs/python/[email protected]/samples/async_samples/sample_analyze_invoices_from_bytes_source_async.py:113
- 1source
pkgs/python/[email protected]/samples/async_samples/sample_analyze_invoices_from_bytes_source_async.py:45 - 2sink
pkgs/python/[email protected]/samples/async_samples/sample_analyze_invoices_from_bytes_source_async.py:118
- 1source
pkgs/python/[email protected]/samples/async_samples/sample_analyze_invoices_from_bytes_source_async.py:45 - 2sink
pkgs/python/[email protected]/samples/async_samples/sample_analyze_invoices_from_bytes_source_async.py:123
- 1source
pkgs/python/[email protected]/samples/async_samples/sample_analyze_invoices_from_bytes_source_async.py:45 - 2sink
pkgs/python/[email protected]/samples/async_samples/sample_analyze_invoices_from_bytes_source_async.py:128
- 1source
pkgs/python/[email protected]/samples/async_samples/sample_analyze_invoices_from_bytes_source_async.py:45 - 2sink
pkgs/python/[email protected]/samples/async_samples/sample_analyze_invoices_from_bytes_source_async.py:135
- 1source
pkgs/python/[email protected]/samples/async_samples/sample_analyze_invoices_from_bytes_source_async.py:45 - 2sink
pkgs/python/[email protected]/samples/async_samples/sample_analyze_invoices_from_bytes_source_async.py:138
- 1source
pkgs/python/[email protected]/samples/async_samples/sample_analyze_invoices_from_bytes_source_async.py:45 - 2sink
pkgs/python/[email protected]/samples/async_samples/sample_analyze_invoices_from_bytes_source_async.py:143
- 1source
pkgs/python/[email protected]/samples/async_samples/sample_analyze_invoices_from_bytes_source_async.py:45 - 2sink
pkgs/python/[email protected]/samples/async_samples/sample_analyze_invoices_from_bytes_source_async.py:148
- 1source
pkgs/python/[email protected]/samples/async_samples/sample_analyze_invoices_from_bytes_source_async.py:45 - 2sink
pkgs/python/[email protected]/samples/async_samples/sample_analyze_invoices_from_bytes_source_async.py:156
- 1source
pkgs/python/[email protected]/samples/async_samples/sample_analyze_invoices_from_bytes_source_async.py:45 - 2sink
pkgs/python/[email protected]/samples/async_samples/sample_analyze_invoices_from_bytes_source_async.py:161
- 1source
pkgs/python/[email protected]/samples/async_samples/sample_analyze_invoices_from_bytes_source_async.py:45 - 2sink
pkgs/python/[email protected]/samples/async_samples/sample_analyze_invoices_from_bytes_source_async.py:166
- 1source
pkgs/python/[email protected]/samples/async_samples/sample_analyze_invoices_from_bytes_source_async.py:45 - 2sink
pkgs/python/[email protected]/samples/async_samples/sample_analyze_invoices_from_bytes_source_async.py:171
- 1source
pkgs/python/[email protected]/samples/async_samples/sample_analyze_invoices_from_bytes_source_async.py:45 - 2sink
pkgs/python/[email protected]/samples/async_samples/sample_analyze_invoices_from_bytes_source_async.py:174
- 1source
pkgs/python/[email protected]/samples/async_samples/sample_analyze_invoices_from_bytes_source_async.py:45 - 2sink
pkgs/python/[email protected]/samples/async_samples/sample_analyze_invoices_from_bytes_source_async.py:177
- 1source
pkgs/python/[email protected]/samples/async_samples/sample_analyze_invoices_from_bytes_source_async.py:45 - 2sink
pkgs/python/[email protected]/samples/async_samples/sample_analyze_invoices_from_bytes_source_async.py:180
- 1source
pkgs/python/[email protected]/samples/async_samples/sample_analyze_invoices_from_bytes_source_async.py:45 - 2sink
pkgs/python/[email protected]/samples/async_samples/sample_analyze_invoices_from_bytes_source_async.py:183
- 1source
pkgs/python/[email protected]/samples/async_samples/sample_analyze_invoices_from_bytes_source_async.py:45 - 2sink
pkgs/python/[email protected]/samples/async_samples/sample_analyze_invoices_from_bytes_source_async.py:188
- 1source
pkgs/python/[email protected]/samples/async_samples/sample_analyze_invoices_from_bytes_source_async.py:45 - 2sink
pkgs/python/[email protected]/samples/async_samples/sample_analyze_invoices_from_bytes_source_async.py:191
- 1source
pkgs/python/[email protected]/samples/async_samples/sample_analyze_invoices_from_bytes_source_async.py:45 - 2sink
pkgs/python/[email protected]/samples/async_samples/sample_analyze_invoices_from_bytes_source_async.py:196
- 1source
pkgs/python/[email protected]/samples/async_samples/sample_analyze_invoices_from_bytes_source_async.py:45 - 2sink
pkgs/python/[email protected]/samples/async_samples/sample_analyze_invoices_from_bytes_source_async.py:201
- 1source
pkgs/python/[email protected]/samples/async_samples/sample_analyze_invoices_from_bytes_source_async.py:45 - 2sink
pkgs/python/[email protected]/samples/async_samples/sample_analyze_invoices_from_bytes_source_async.py:206
- 1source
pkgs/python/[email protected]/samples/async_samples/sample_analyze_invoices_from_bytes_source_async.py:45 - 2sink
pkgs/python/[email protected]/samples/async_samples/sample_analyze_invoices_from_bytes_source_async.py:211
- 1source
pkgs/python/[email protected]/samples/async_samples/sample_analyze_invoices_from_bytes_source_async.py:45 - 2sink
pkgs/python/[email protected]/samples/async_samples/sample_analyze_invoices_from_bytes_source_async.py:216
- 1source
pkgs/python/[email protected]/samples/async_samples/sample_analyze_layout_async.py:74 - 2sink
pkgs/python/[email protected]/samples/async_samples/sample_analyze_layout_async.py:88
- 1source
pkgs/python/[email protected]/samples/async_samples/sample_analyze_layout_async.py:74 - 2sink
pkgs/python/[email protected]/samples/async_samples/sample_analyze_layout_async.py:89
- 1source
pkgs/python/[email protected]/samples/async_samples/sample_analyze_layout_async.py:74 - 2sink
pkgs/python/[email protected]/samples/async_samples/sample_analyze_layout_async.py:94
- 1source
pkgs/python/[email protected]/samples/async_samples/sample_analyze_layout_async.py:74 - 2sink
pkgs/python/[email protected]/samples/async_samples/sample_analyze_layout_async.py:101
- 1source
pkgs/python/[email protected]/samples/async_samples/sample_analyze_layout_async.py:74 - 2sink
pkgs/python/[email protected]/samples/async_samples/sample_analyze_layout_async.py:105
- 1source
pkgs/python/[email protected]/samples/async_samples/sample_analyze_layout_async.py:74 - 2sink
pkgs/python/[email protected]/samples/async_samples/sample_analyze_layout_async.py:111
- 1source
pkgs/python/[email protected]/samples/async_samples/sample_analyze_layout_async.py:74 - 2sink
pkgs/python/[email protected]/samples/async_samples/sample_analyze_layout_async.py:116
- 1source
pkgs/python/[email protected]/samples/async_samples/sample_analyze_layout_async.py:74 - 2sink
pkgs/python/[email protected]/samples/async_samples/sample_analyze_layout_async.py:119
- 1source
pkgs/python/[email protected]/samples/async_samples/sample_analyze_layout_async.py:74 - 2sink
pkgs/python/[email protected]/samples/async_samples/sample_analyze_layout_async.py:120
- 1source
pkgs/python/[email protected]/samples/async_samples/sample_analyze_layout_async.py:74 - 2sink
pkgs/python/[email protected]/samples/async_samples/sample_analyze_layout_async.py:124
- 1source
pkgs/python/[email protected]/samples/async_samples/sample_analyze_layout_async.py:74 - 2sink
pkgs/python/[email protected]/samples/async_samples/sample_analyze_layout_async.py:127
- 1source
pkgs/python/[email protected]/samples/async_samples/sample_analyze_layout_async.py:74 - 2sink
pkgs/python/[email protected]/samples/async_samples/sample_analyze_layout_async.py:131
- 1source
pkgs/python/[email protected]/samples/async_samples/sample_analyze_layout_async.py:74 - 2sink
pkgs/python/[email protected]/samples/async_samples/sample_analyze_layout_async.py:134
- 1source
pkgs/python/[email protected]/samples/async_samples/sample_analyze_read_async.py:70 - 2sink
pkgs/python/[email protected]/samples/async_samples/sample_analyze_read_async.py:85
- 1source
pkgs/python/[email protected]/samples/async_samples/sample_analyze_read_async.py:70 - 2sink
pkgs/python/[email protected]/samples/async_samples/sample_analyze_read_async.py:94
- 1source
pkgs/python/[email protected]/samples/async_samples/sample_analyze_read_async.py:70 - 2sink
pkgs/python/[email protected]/samples/async_samples/sample_analyze_read_async.py:98
- 1source
pkgs/python/[email protected]/samples/async_samples/sample_analyze_read_async.py:70 - 2sink
pkgs/python/[email protected]/samples/async_samples/sample_analyze_read_async.py:99
- 1source
pkgs/python/[email protected]/samples/async_samples/sample_analyze_read_async.py:70 - 2sink
pkgs/python/[email protected]/samples/async_samples/sample_analyze_read_async.py:104
- 1source
pkgs/python/[email protected]/samples/async_samples/sample_analyze_read_async.py:70 - 2sink
pkgs/python/[email protected]/samples/async_samples/sample_analyze_read_async.py:109
- 1source
pkgs/python/[email protected]/samples/async_samples/sample_analyze_read_async.py:70 - 2sink
pkgs/python/[email protected]/samples/async_samples/sample_analyze_read_async.py:113
- 1source
pkgs/python/[email protected]/samples/async_samples/sample_analyze_read_async.py:70 - 2sink
pkgs/python/[email protected]/samples/async_samples/sample_analyze_read_async.py:119
- 1source
pkgs/python/[email protected]/samples/async_samples/sample_analyze_read_async.py:70 - 2sink
pkgs/python/[email protected]/samples/async_samples/sample_analyze_read_async.py:124
- 1source
pkgs/python/[email protected]/samples/async_samples/sample_analyze_read_async.py:70 - 2sink
pkgs/python/[email protected]/samples/async_samples/sample_analyze_read_async.py:127
- 1source
pkgs/python/[email protected]/samples/async_samples/sample_analyze_read_async.py:70 - 2sink
pkgs/python/[email protected]/samples/async_samples/sample_analyze_read_async.py:128
- 1source
pkgs/python/[email protected]/samples/async_samples/sample_analyze_receipts_async.py:52 - 2sink
pkgs/python/[email protected]/samples/async_samples/sample_analyze_receipts_async.py:64
- 1source
pkgs/python/[email protected]/samples/async_samples/sample_analyze_receipts_async.py:52 - 2sink
pkgs/python/[email protected]/samples/async_samples/sample_analyze_receipts_async.py:65
- 1source
pkgs/python/[email protected]/samples/async_samples/sample_analyze_receipts_async.py:52 - 2sink
pkgs/python/[email protected]/samples/async_samples/sample_analyze_receipts_async.py:69
- 1source
pkgs/python/[email protected]/samples/async_samples/sample_analyze_receipts_async.py:52 - 2sink
pkgs/python/[email protected]/samples/async_samples/sample_analyze_receipts_async.py:75
- 1source
pkgs/python/[email protected]/samples/async_samples/sample_analyze_receipts_async.py:52 - 2sink
pkgs/python/[email protected]/samples/async_samples/sample_analyze_receipts_async.py:83
- 1source
pkgs/python/[email protected]/samples/async_samples/sample_analyze_receipts_async.py:52 - 2sink
pkgs/python/[email protected]/samples/async_samples/sample_analyze_receipts_async.py:86
- 1source
pkgs/python/[email protected]/samples/async_samples/sample_analyze_receipts_async.py:52 - 2sink
pkgs/python/[email protected]/samples/async_samples/sample_analyze_receipts_async.py:92
- 1source
pkgs/python/[email protected]/samples/async_samples/sample_analyze_receipts_async.py:52 - 2sink
pkgs/python/[email protected]/samples/async_samples/sample_analyze_receipts_async.py:98
- 1source
pkgs/python/[email protected]/samples/async_samples/sample_analyze_receipts_async.py:52 - 2sink
pkgs/python/[email protected]/samples/async_samples/sample_analyze_receipts_async.py:104
- 1source
pkgs/python/[email protected]/samples/async_samples/sample_analyze_receipts_async.py:52 - 2sink
pkgs/python/[email protected]/samples/async_samples/sample_analyze_receipts_async.py:109
- 1source
pkgs/python/[email protected]/samples/async_samples/sample_analyze_receipts_async.py:52 - 2sink
pkgs/python/[email protected]/samples/async_samples/sample_analyze_receipts_async.py:112
- 1source
pkgs/python/[email protected]/samples/async_samples/sample_analyze_receipts_async.py:52 - 2sink
pkgs/python/[email protected]/samples/async_samples/sample_analyze_receipts_async.py:115
- 1source
pkgs/python/[email protected]/samples/async_samples/sample_analyze_receipts_from_url_async.py:41 - 2sink
pkgs/python/[email protected]/samples/async_samples/sample_analyze_receipts_from_url_async.py:53
- 1source
pkgs/python/[email protected]/samples/async_samples/sample_analyze_receipts_from_url_async.py:41 - 2sink
pkgs/python/[email protected]/samples/async_samples/sample_analyze_receipts_from_url_async.py:54
- 1source
pkgs/python/[email protected]/samples/async_samples/sample_analyze_receipts_from_url_async.py:41 - 2sink
pkgs/python/[email protected]/samples/async_samples/sample_analyze_receipts_from_url_async.py:58
- 1source
pkgs/python/[email protected]/samples/async_samples/sample_analyze_receipts_from_url_async.py:41 - 2sink
pkgs/python/[email protected]/samples/async_samples/sample_analyze_receipts_from_url_async.py:64
- 1source
pkgs/python/[email protected]/samples/async_samples/sample_analyze_receipts_from_url_async.py:41 - 2sink
pkgs/python/[email protected]/samples/async_samples/sample_analyze_receipts_from_url_async.py:72
- 1source
pkgs/python/[email protected]/samples/async_samples/sample_analyze_receipts_from_url_async.py:41 - 2sink
pkgs/python/[email protected]/samples/async_samples/sample_analyze_receipts_from_url_async.py:75
- 1source
pkgs/python/[email protected]/samples/async_samples/sample_analyze_receipts_from_url_async.py:41 - 2sink
pkgs/python/[email protected]/samples/async_samples/sample_analyze_receipts_from_url_async.py:81
- 1source
pkgs/python/[email protected]/samples/async_samples/sample_analyze_receipts_from_url_async.py:41 - 2sink
pkgs/python/[email protected]/samples/async_samples/sample_analyze_receipts_from_url_async.py:87
- 1source
pkgs/python/[email protected]/samples/async_samples/sample_analyze_receipts_from_url_async.py:41 - 2sink
pkgs/python/[email protected]/samples/async_samples/sample_analyze_receipts_from_url_async.py:93
- 1source
pkgs/python/[email protected]/samples/async_samples/sample_analyze_receipts_from_url_async.py:41 - 2sink
pkgs/python/[email protected]/samples/async_samples/sample_analyze_receipts_from_url_async.py:98
- 1source
pkgs/python/[email protected]/samples/async_samples/sample_analyze_receipts_from_url_async.py:41 - 2sink
pkgs/python/[email protected]/samples/async_samples/sample_analyze_receipts_from_url_async.py:101
- 1source
pkgs/python/[email protected]/samples/async_samples/sample_analyze_receipts_from_url_async.py:41 - 2sink
pkgs/python/[email protected]/samples/async_samples/sample_analyze_receipts_from_url_async.py:104
- 1source
pkgs/python/[email protected]/samples/async_samples/sample_analyze_tax_us_w2_async.py:49 - 2sink
pkgs/python/[email protected]/samples/async_samples/sample_analyze_tax_us_w2_async.py:61
- 1source
pkgs/python/[email protected]/samples/async_samples/sample_analyze_tax_us_w2_async.py:49 - 2sink
pkgs/python/[email protected]/samples/async_samples/sample_analyze_tax_us_w2_async.py:65
- 1source
pkgs/python/[email protected]/samples/async_samples/sample_analyze_tax_us_w2_async.py:49 - 2sink
pkgs/python/[email protected]/samples/async_samples/sample_analyze_tax_us_w2_async.py:70
- 1source
pkgs/python/[email protected]/samples/async_samples/sample_analyze_tax_us_w2_async.py:49 - 2sink
pkgs/python/[email protected]/samples/async_samples/sample_analyze_tax_us_w2_async.py:73
- 1source
pkgs/python/[email protected]/samples/async_samples/sample_analyze_tax_us_w2_async.py:49 - 2sink
pkgs/python/[email protected]/samples/async_samples/sample_analyze_tax_us_w2_async.py:79
- 1source
pkgs/python/[email protected]/samples/async_samples/sample_analyze_tax_us_w2_async.py:49 - 2sink
pkgs/python/[email protected]/samples/async_samples/sample_analyze_tax_us_w2_async.py:82
- 1source
pkgs/python/[email protected]/samples/async_samples/sample_analyze_tax_us_w2_async.py:49 - 2sink
pkgs/python/[email protected]/samples/async_samples/sample_analyze_tax_us_w2_async.py:85
- 1source
pkgs/python/[email protected]/samples/async_samples/sample_analyze_tax_us_w2_async.py:49 - 2sink
pkgs/python/[email protected]/samples/async_samples/sample_analyze_tax_us_w2_async.py:86
- 1source
pkgs/python/[email protected]/samples/async_samples/sample_analyze_tax_us_w2_async.py:49 - 2sink
pkgs/python/[email protected]/samples/async_samples/sample_analyze_tax_us_w2_async.py:89
- 1source
pkgs/python/[email protected]/samples/async_samples/sample_analyze_tax_us_w2_async.py:49 - 2sink
pkgs/python/[email protected]/samples/async_samples/sample_analyze_tax_us_w2_async.py:92
- 1source
pkgs/python/[email protected]/samples/async_samples/sample_analyze_tax_us_w2_async.py:49 - 2sink
pkgs/python/[email protected]/samples/async_samples/sample_analyze_tax_us_w2_async.py:101
- 1source
pkgs/python/[email protected]/samples/async_samples/sample_analyze_tax_us_w2_async.py:49 - 2sink
pkgs/python/[email protected]/samples/async_samples/sample_analyze_tax_us_w2_async.py:104
- 1source
pkgs/python/[email protected]/samples/async_samples/sample_analyze_tax_us_w2_async.py:49 - 2sink
pkgs/python/[email protected]/samples/async_samples/sample_analyze_tax_us_w2_async.py:109
- 1source
pkgs/python/[email protected]/samples/async_samples/sample_analyze_tax_us_w2_async.py:49 - 2sink
pkgs/python/[email protected]/samples/async_samples/sample_analyze_tax_us_w2_async.py:110
- 1source
pkgs/python/[email protected]/samples/async_samples/sample_analyze_tax_us_w2_async.py:49 - 2sink
pkgs/python/[email protected]/samples/async_samples/sample_analyze_tax_us_w2_async.py:113
- 1source
pkgs/python/[email protected]/samples/async_samples/sample_analyze_tax_us_w2_async.py:49 - 2sink
pkgs/python/[email protected]/samples/async_samples/sample_analyze_tax_us_w2_async.py:116
- 1source
pkgs/python/[email protected]/samples/async_samples/sample_analyze_tax_us_w2_async.py:49 - 2sink
pkgs/python/[email protected]/samples/async_samples/sample_analyze_tax_us_w2_async.py:122
- 1source
pkgs/python/[email protected]/samples/async_samples/sample_analyze_tax_us_w2_async.py:49 - 2sink
pkgs/python/[email protected]/samples/async_samples/sample_analyze_tax_us_w2_async.py:128
- 1source
pkgs/python/[email protected]/samples/async_samples/sample_analyze_tax_us_w2_async.py:49 - 2sink
pkgs/python/[email protected]/samples/async_samples/sample_analyze_tax_us_w2_async.py:134
- 1source
pkgs/python/[email protected]/samples/async_samples/sample_analyze_tax_us_w2_async.py:49 - 2sink
pkgs/python/[email protected]/samples/async_samples/sample_analyze_tax_us_w2_async.py:140
- 1source
pkgs/python/[email protected]/samples/async_samples/sample_analyze_tax_us_w2_async.py:49 - 2sink
pkgs/python/[email protected]/samples/async_samples/sample_analyze_tax_us_w2_async.py:146
- 1source
pkgs/python/[email protected]/samples/async_samples/sample_analyze_tax_us_w2_async.py:49 - 2sink
pkgs/python/[email protected]/samples/async_samples/sample_analyze_tax_us_w2_async.py:152
- 1source
pkgs/python/[email protected]/samples/async_samples/sample_analyze_tax_us_w2_async.py:49 - 2sink
pkgs/python/[email protected]/samples/async_samples/sample_analyze_tax_us_w2_async.py:158
- 1source
pkgs/python/[email protected]/samples/async_samples/sample_analyze_tax_us_w2_async.py:49 - 2sink
pkgs/python/[email protected]/samples/async_samples/sample_analyze_tax_us_w2_async.py:163
- 1source
pkgs/python/[email protected]/samples/async_samples/sample_analyze_tax_us_w2_async.py:49 - 2sink
pkgs/python/[email protected]/samples/async_samples/sample_analyze_tax_us_w2_async.py:168
- 1source
pkgs/python/[email protected]/samples/async_samples/sample_analyze_tax_us_w2_async.py:49 - 2sink
pkgs/python/[email protected]/samples/async_samples/sample_analyze_tax_us_w2_async.py:173
- 1source
pkgs/python/[email protected]/samples/async_samples/sample_analyze_tax_us_w2_async.py:49 - 2sink
pkgs/python/[email protected]/samples/async_samples/sample_analyze_tax_us_w2_async.py:182
- 1source
pkgs/python/[email protected]/samples/async_samples/sample_analyze_tax_us_w2_async.py:49 - 2sink
pkgs/python/[email protected]/samples/async_samples/sample_analyze_tax_us_w2_async.py:187
- 1source
pkgs/python/[email protected]/samples/async_samples/sample_analyze_tax_us_w2_async.py:49 - 2sink
pkgs/python/[email protected]/samples/async_samples/sample_analyze_tax_us_w2_async.py:190
- 1source
pkgs/python/[email protected]/samples/async_samples/sample_analyze_tax_us_w2_async.py:49 - 2sink
pkgs/python/[email protected]/samples/async_samples/sample_analyze_tax_us_w2_async.py:195
- 1source
pkgs/python/[email protected]/samples/async_samples/sample_analyze_tax_us_w2_async.py:49 - 2sink
pkgs/python/[email protected]/samples/async_samples/sample_analyze_tax_us_w2_async.py:200
- 1source
pkgs/python/[email protected]/samples/async_samples/sample_analyze_tax_us_w2_async.py:49 - 2sink
pkgs/python/[email protected]/samples/async_samples/sample_analyze_tax_us_w2_async.py:205
- 1source
pkgs/python/[email protected]/samples/async_samples/sample_analyze_tax_us_w2_async.py:49 - 2sink
pkgs/python/[email protected]/samples/async_samples/sample_analyze_tax_us_w2_async.py:212
- 1source
pkgs/python/[email protected]/samples/async_samples/sample_analyze_tax_us_w2_async.py:49 - 2sink
pkgs/python/[email protected]/samples/async_samples/sample_analyze_tax_us_w2_async.py:215
- 1source
pkgs/python/[email protected]/samples/async_samples/sample_analyze_tax_us_w2_async.py:49 - 2sink
pkgs/python/[email protected]/samples/async_samples/sample_analyze_tax_us_w2_async.py:221
- 1source
pkgs/python/[email protected]/samples/async_samples/sample_analyze_tax_us_w2_async.py:49 - 2sink
pkgs/python/[email protected]/samples/async_samples/sample_analyze_tax_us_w2_async.py:227
- 1source
pkgs/python/[email protected]/samples/async_samples/sample_analyze_tax_us_w2_async.py:49 - 2sink
pkgs/python/[email protected]/samples/async_samples/sample_analyze_tax_us_w2_async.py:237
- 1source
pkgs/python/[email protected]/samples/async_samples/sample_analyze_tax_us_w2_async.py:49 - 2sink
pkgs/python/[email protected]/samples/async_samples/sample_analyze_tax_us_w2_async.py:243
- 1source
pkgs/python/[email protected]/samples/async_samples/sample_analyze_tax_us_w2_async.py:49 - 2sink
pkgs/python/[email protected]/samples/async_samples/sample_analyze_tax_us_w2_async.py:249
- 1source
pkgs/python/[email protected]/samples/async_samples/sample_classify_document_async.py:50 - 2sink
pkgs/python/[email protected]/samples/async_samples/sample_classify_document_async.py:63
- 1source
pkgs/python/[email protected]/samples/async_samples/sample_compose_model_async.py:56 - 2sink
pkgs/python/[email protected]/samples/async_samples/sample_compose_model_async.py:116
- 1source
pkgs/python/[email protected]/samples/async_samples/sample_compose_model_async.py:56 - 2sink
pkgs/python/[email protected]/samples/async_samples/sample_compose_model_async.py:117
- 1source
pkgs/python/[email protected]/samples/async_samples/sample_compose_model_async.py:56 - 2sink
pkgs/python/[email protected]/samples/async_samples/sample_compose_model_async.py:118
- 1source
pkgs/python/[email protected]/samples/async_samples/sample_compose_model_async.py:56 - 2sink
pkgs/python/[email protected]/samples/async_samples/sample_compose_model_async.py:119
- 1source
pkgs/python/[email protected]/samples/async_samples/sample_compose_model_async.py:56 - 2sink
pkgs/python/[email protected]/samples/async_samples/sample_compose_model_async.py:123
- 1source
pkgs/python/[email protected]/samples/async_samples/sample_compose_model_async.py:56 - 2sink
pkgs/python/[email protected]/samples/async_samples/sample_compose_model_async.py:126
- 1source
pkgs/python/[email protected]/samples/async_samples/sample_compose_model_async.py:56 - 2sink
pkgs/python/[email protected]/samples/async_samples/sample_compose_model_async.py:133
- 1source
pkgs/python/[email protected]/samples/async_samples/sample_convert_to_and_from_dict_async.py:45 - 2sink
pkgs/python/[email protected]/samples/async_samples/sample_convert_to_and_from_dict_async.py:65
- 1source
pkgs/python/[email protected]/samples/async_samples/sample_convert_to_and_from_dict_async.py:45 - 2sink
pkgs/python/[email protected]/samples/async_samples/sample_convert_to_and_from_dict_async.py:66
- 1source
pkgs/python/[email protected]/samples/async_samples/sample_convert_to_and_from_dict_async.py:45 - 2sink
pkgs/python/[email protected]/samples/async_samples/sample_convert_to_and_from_dict_async.py:67
- 1source
pkgs/python/[email protected]/samples/async_samples/sample_copy_model_to_async.py:41 - 2sink
pkgs/python/[email protected]/samples/async_samples/sample_copy_model_to_async.py:67
- 1source
pkgs/python/[email protected]/samples/async_samples/sample_copy_model_to_async.py:41 - 2sink
pkgs/python/[email protected]/samples/async_samples/sample_copy_model_to_async.py:68
- 1source
pkgs/python/[email protected]/samples/async_samples/sample_copy_model_to_async.py:41 - 2sink
pkgs/python/[email protected]/samples/async_samples/sample_copy_model_to_async.py:69
- 1source
pkgs/python/[email protected]/samples/async_samples/sample_copy_model_to_async.py:41 - 2sink
pkgs/python/[email protected]/samples/async_samples/sample_copy_model_to_async.py:70
- 1source
pkgs/python/[email protected]/samples/async_samples/sample_copy_model_to_async.py:41 - 2sink
pkgs/python/[email protected]/samples/async_samples/sample_copy_model_to_async.py:74
- 1source
pkgs/python/[email protected]/samples/async_samples/sample_copy_model_to_async.py:41 - 2sink
pkgs/python/[email protected]/samples/async_samples/sample_copy_model_to_async.py:78
- 1source
pkgs/python/[email protected]/samples/async_samples/sample_copy_model_to_async.py:41 - 2sink
pkgs/python/[email protected]/samples/async_samples/sample_copy_model_to_async.py:85
- 1source
pkgs/python/[email protected]/samples/async_samples/sample_manage_classifiers_async.py:41 - 2sink
pkgs/python/[email protected]/samples/async_samples/sample_manage_classifiers_async.py:68
- 1source
pkgs/python/[email protected]/samples/async_samples/sample_manage_classifiers_async.py:41 - 2sink
pkgs/python/[email protected]/samples/async_samples/sample_manage_classifiers_async.py:69
- 1source
pkgs/python/[email protected]/samples/async_samples/sample_manage_classifiers_async.py:41 - 2sink
pkgs/python/[email protected]/samples/async_samples/sample_manage_classifiers_async.py:70
- 1source
pkgs/python/[email protected]/samples/async_samples/sample_manage_classifiers_async.py:41 - 2sink
pkgs/python/[email protected]/samples/async_samples/sample_manage_classifiers_async.py:73
- 1source
pkgs/python/[email protected]/samples/async_samples/sample_manage_classifiers_async.py:41 - 2sink
pkgs/python/[email protected]/samples/async_samples/sample_manage_classifiers_async.py:75
- 1source
pkgs/python/[email protected]/samples/async_samples/sample_manage_classifiers_async.py:41 - 2sink
pkgs/python/[email protected]/samples/async_samples/sample_manage_classifiers_async.py:82
- 1source
pkgs/python/[email protected]/samples/async_samples/sample_manage_classifiers_async.py:41 - 2sink
pkgs/python/[email protected]/samples/async_samples/sample_manage_classifiers_async.py:85
- 1source
pkgs/python/[email protected]/samples/async_samples/sample_manage_classifiers_async.py:41 - 2sink
pkgs/python/[email protected]/samples/async_samples/sample_manage_classifiers_async.py:86
- 1source
pkgs/python/[email protected]/samples/async_samples/sample_manage_classifiers_async.py:41 - 2sink
pkgs/python/[email protected]/samples/async_samples/sample_manage_classifiers_async.py:87
- 1source
pkgs/python/[email protected]/samples/async_samples/sample_manage_classifiers_async.py:41 - 2sink
pkgs/python/[email protected]/samples/async_samples/sample_manage_classifiers_async.py:88
- 1source
pkgs/python/[email protected]/samples/async_samples/sample_manage_classifiers_async.py:41 - 2sink
pkgs/python/[email protected]/samples/async_samples/sample_manage_classifiers_async.py:98
- 1source
pkgs/python/[email protected]/samples/async_samples/sample_manage_models_async.py:42 - 2sink
pkgs/python/[email protected]/samples/async_samples/sample_manage_models_async.py:57
- 1source
pkgs/python/[email protected]/samples/async_samples/sample_manage_models_async.py:42 - 2sink
pkgs/python/[email protected]/samples/async_samples/sample_manage_models_async.py:58
- 1source
pkgs/python/[email protected]/samples/async_samples/sample_manage_models_async.py:42 - 2sink
pkgs/python/[email protected]/samples/async_samples/sample_manage_models_async.py:59
- 1source
pkgs/python/[email protected]/samples/async_samples/sample_manage_models_async.py:42 - 2sink
pkgs/python/[email protected]/samples/async_samples/sample_manage_models_async.py:60
- 1source
pkgs/python/[email protected]/samples/async_samples/sample_manage_models_async.py:42 - 2sink
pkgs/python/[email protected]/samples/async_samples/sample_manage_models_async.py:64
- 1source
pkgs/python/[email protected]/samples/async_samples/sample_manage_models_async.py:42 - 2sink
pkgs/python/[email protected]/samples/async_samples/sample_manage_models_async.py:68
- 1source
pkgs/python/[email protected]/samples/async_samples/sample_manage_models_async.py:42 - 2sink
pkgs/python/[email protected]/samples/async_samples/sample_manage_models_async.py:75
- 1source
pkgs/python/[email protected]/samples/async_samples/sample_manage_models_async.py:42 - 2sink
pkgs/python/[email protected]/samples/async_samples/sample_manage_models_async.py:80
- 1source
pkgs/python/[email protected]/samples/async_samples/sample_manage_models_async.py:42 - 2sink
pkgs/python/[email protected]/samples/async_samples/sample_manage_models_async.py:90
- 1source
pkgs/python/[email protected]/samples/async_samples/sample_manage_models_async.py:42 - 2sink
pkgs/python/[email protected]/samples/async_samples/sample_manage_models_async.py:93
- 1source
pkgs/python/[email protected]/samples/async_samples/sample_manage_models_async.py:42 - 2sink
pkgs/python/[email protected]/samples/async_samples/sample_manage_models_async.py:94
- 1source
pkgs/python/[email protected]/samples/async_samples/sample_manage_models_async.py:42 - 2sink
pkgs/python/[email protected]/samples/async_samples/sample_manage_models_async.py:95
- 1source
pkgs/python/[email protected]/samples/async_samples/sample_manage_models_async.py:42 - 2sink
pkgs/python/[email protected]/samples/async_samples/sample_manage_models_async.py:96
- 1source
pkgs/python/[email protected]/samples/async_samples/sample_manage_models_async.py:42 - 2sink
pkgs/python/[email protected]/samples/async_samples/sample_manage_models_async.py:106
- 1source
pkgs/python/[email protected]/samples/async_samples/sample_send_request_async.py:32 - 2sink
pkgs/python/[email protected]/samples/async_samples/sample_send_request_async.py:44
- 1source
pkgs/python/[email protected]/samples/sample_analyze_addon_barcodes.py:59 - 2sink
pkgs/python/[email protected]/samples/sample_analyze_addon_barcodes.py:74
- 1source
pkgs/python/[email protected]/samples/sample_analyze_addon_barcodes.py:59 - 2sink
pkgs/python/[email protected]/samples/sample_analyze_addon_barcodes.py:76
- 1source
pkgs/python/[email protected]/samples/sample_analyze_addon_barcodes.py:59 - 2sink
pkgs/python/[email protected]/samples/sample_analyze_addon_barcodes.py:78
- 1source
pkgs/python/[email protected]/samples/sample_analyze_addon_barcodes.py:59 - 2sink
pkgs/python/[email protected]/samples/sample_analyze_addon_barcodes.py:79
- 1source
pkgs/python/[email protected]/samples/sample_analyze_addon_barcodes.py:59 - 2sink
pkgs/python/[email protected]/samples/sample_analyze_addon_barcodes.py:80
- 1source
pkgs/python/[email protected]/samples/sample_analyze_addon_barcodes.py:59 - 2sink
pkgs/python/[email protected]/samples/sample_analyze_addon_barcodes.py:85
- 1source
pkgs/python/[email protected]/samples/sample_analyze_addon_fonts.py:66 - 2sink
pkgs/python/[email protected]/samples/sample_analyze_addon_fonts.py:109
- 1source
pkgs/python/[email protected]/samples/sample_analyze_addon_fonts.py:66 - 2sink
pkgs/python/[email protected]/samples/sample_analyze_addon_fonts.py:114
- 1source
pkgs/python/[email protected]/samples/sample_analyze_addon_fonts.py:66 - 2sink
pkgs/python/[email protected]/samples/sample_analyze_addon_fonts.py:119
- 1source
pkgs/python/[email protected]/samples/sample_analyze_addon_fonts.py:66 - 2sink
pkgs/python/[email protected]/samples/sample_analyze_addon_fonts.py:124
- 1source
pkgs/python/[email protected]/samples/sample_analyze_addon_fonts.py:66 - 2sink
pkgs/python/[email protected]/samples/sample_analyze_addon_fonts.py:129
- 1source
pkgs/python/[email protected]/samples/sample_analyze_addon_formulas.py:64 - 2sink
pkgs/python/[email protected]/samples/sample_analyze_addon_formulas.py:80
- 1source
pkgs/python/[email protected]/samples/sample_analyze_addon_formulas.py:64 - 2sink
pkgs/python/[email protected]/samples/sample_analyze_addon_formulas.py:85
- 1source
pkgs/python/[email protected]/samples/sample_analyze_addon_formulas.py:64 - 2sink
pkgs/python/[email protected]/samples/sample_analyze_addon_formulas.py:87
- 1source
pkgs/python/[email protected]/samples/sample_analyze_addon_formulas.py:64 - 2sink
pkgs/python/[email protected]/samples/sample_analyze_addon_formulas.py:88
- 1source
pkgs/python/[email protected]/samples/sample_analyze_addon_formulas.py:64 - 2sink
pkgs/python/[email protected]/samples/sample_analyze_addon_formulas.py:89
- 1source
pkgs/python/[email protected]/samples/sample_analyze_addon_formulas.py:64 - 2sink
pkgs/python/[email protected]/samples/sample_analyze_addon_formulas.py:91
- 1source
pkgs/python/[email protected]/samples/sample_analyze_addon_formulas.py:64 - 2sink
pkgs/python/[email protected]/samples/sample_analyze_addon_formulas.py:93
- 1source
pkgs/python/[email protected]/samples/sample_analyze_addon_formulas.py:64 - 2sink
pkgs/python/[email protected]/samples/sample_analyze_addon_formulas.py:94
- 1source
pkgs/python/[email protected]/samples/sample_analyze_addon_formulas.py:64 - 2sink
pkgs/python/[email protected]/samples/sample_analyze_addon_formulas.py:95
- 1source
pkgs/python/[email protected]/samples/sample_analyze_addon_highres.py:70 - 2sink
pkgs/python/[email protected]/samples/sample_analyze_addon_highres.py:89
- 1source
pkgs/python/[email protected]/samples/sample_analyze_addon_highres.py:70 - 2sink
pkgs/python/[email protected]/samples/sample_analyze_addon_highres.py:90
- 1source
pkgs/python/[email protected]/samples/sample_analyze_addon_highres.py:70 - 2sink
pkgs/python/[email protected]/samples/sample_analyze_addon_highres.py:97
- 1source
pkgs/python/[email protected]/samples/sample_analyze_addon_highres.py:70 - 2sink
pkgs/python/[email protected]/samples/sample_analyze_addon_highres.py:100
- 1source
pkgs/python/[email protected]/samples/sample_analyze_addon_highres.py:70 - 2sink
pkgs/python/[email protected]/samples/sample_analyze_addon_highres.py:107
- 1source
pkgs/python/[email protected]/samples/sample_analyze_addon_highres.py:70 - 2sink
pkgs/python/[email protected]/samples/sample_analyze_addon_highres.py:114
- 1source
pkgs/python/[email protected]/samples/sample_analyze_addon_highres.py:70 - 2sink
pkgs/python/[email protected]/samples/sample_analyze_addon_highres.py:117
- 1source
pkgs/python/[email protected]/samples/sample_analyze_addon_highres.py:70 - 2sink
pkgs/python/[email protected]/samples/sample_analyze_addon_highres.py:121
- 1source
pkgs/python/[email protected]/samples/sample_analyze_addon_highres.py:70 - 2sink
pkgs/python/[email protected]/samples/sample_analyze_addon_highres.py:124
- 1source
pkgs/python/[email protected]/samples/sample_analyze_addon_languages.py:59 - 2sink
pkgs/python/[email protected]/samples/sample_analyze_addon_languages.py:74
- 1source
pkgs/python/[email protected]/samples/sample_analyze_addon_languages.py:59 - 2sink
pkgs/python/[email protected]/samples/sample_analyze_addon_languages.py:76
- 1source
pkgs/python/[email protected]/samples/sample_analyze_addon_languages.py:59 - 2sink
pkgs/python/[email protected]/samples/sample_analyze_addon_languages.py:77
- 1source
pkgs/python/[email protected]/samples/sample_analyze_addon_query_fields.py:52 - 2sink
pkgs/python/[email protected]/samples/sample_analyze_addon_query_fields.py:69
- 1source
pkgs/python/[email protected]/samples/sample_analyze_addon_query_fields.py:52 - 2sink
pkgs/python/[email protected]/samples/sample_analyze_addon_query_fields.py:71
- 1source
pkgs/python/[email protected]/samples/sample_analyze_batch_documents.py:53 - 2sink
pkgs/python/[email protected]/samples/sample_analyze_batch_documents.py:73
- 1source
pkgs/python/[email protected]/samples/sample_analyze_batch_documents.py:53 - 2sink
pkgs/python/[email protected]/samples/sample_analyze_batch_documents.py:74
- 1source
pkgs/python/[email protected]/samples/sample_analyze_batch_documents.py:53 - 2sink
pkgs/python/[email protected]/samples/sample_analyze_batch_documents.py:75
- 1source
pkgs/python/[email protected]/samples/sample_analyze_custom_documents.py:65 - 2sink
pkgs/python/[email protected]/samples/sample_analyze_custom_documents.py:77
- 1source
pkgs/python/[email protected]/samples/sample_analyze_custom_documents.py:65 - 2sink
pkgs/python/[email protected]/samples/sample_analyze_custom_documents.py:78
- 1source
pkgs/python/[email protected]/samples/sample_analyze_custom_documents.py:65 - 2sink
pkgs/python/[email protected]/samples/sample_analyze_custom_documents.py:79
- 1source
pkgs/python/[email protected]/samples/sample_analyze_custom_documents.py:65 - 2sink
pkgs/python/[email protected]/samples/sample_analyze_custom_documents.py:80
- 1source
pkgs/python/[email protected]/samples/sample_analyze_custom_documents.py:65 - 2sink
pkgs/python/[email protected]/samples/sample_analyze_custom_documents.py:84
- 1source
pkgs/python/[email protected]/samples/sample_analyze_documents_output_in_markdown.py:33 - 2sink
pkgs/python/[email protected]/samples/sample_analyze_documents_output_in_markdown.py:44
- 1source
pkgs/python/[email protected]/samples/sample_analyze_documents_output_in_markdown.py:33 - 2sink
pkgs/python/[email protected]/samples/sample_analyze_documents_output_in_markdown.py:45
- 1source
pkgs/python/[email protected]/samples/sample_analyze_general_documents.py:60 - 2sink
pkgs/python/[email protected]/samples/sample_analyze_general_documents.py:81
- 1source
pkgs/python/[email protected]/samples/sample_analyze_general_documents.py:60 - 2sink
pkgs/python/[email protected]/samples/sample_analyze_general_documents.py:86
- 1source
pkgs/python/[email protected]/samples/sample_analyze_general_documents.py:60 - 2sink
pkgs/python/[email protected]/samples/sample_analyze_general_documents.py:92
- 1source
pkgs/python/[email protected]/samples/sample_analyze_general_documents.py:60 - 2sink
pkgs/python/[email protected]/samples/sample_analyze_general_documents.py:93
- 1source
pkgs/python/[email protected]/samples/sample_analyze_general_documents.py:60 - 2sink
pkgs/python/[email protected]/samples/sample_analyze_general_documents.py:100
- 1source
pkgs/python/[email protected]/samples/sample_analyze_general_documents.py:60 - 2sink
pkgs/python/[email protected]/samples/sample_analyze_general_documents.py:103
- 1source
pkgs/python/[email protected]/samples/sample_analyze_general_documents.py:60 - 2sink
pkgs/python/[email protected]/samples/sample_analyze_general_documents.py:110
- 1source
pkgs/python/[email protected]/samples/sample_analyze_general_documents.py:60 - 2sink
pkgs/python/[email protected]/samples/sample_analyze_general_documents.py:118
- 1source
pkgs/python/[email protected]/samples/sample_analyze_general_documents.py:60 - 2sink
pkgs/python/[email protected]/samples/sample_analyze_general_documents.py:121
- 1source
pkgs/python/[email protected]/samples/sample_analyze_general_documents.py:60 - 2sink
pkgs/python/[email protected]/samples/sample_analyze_general_documents.py:125
- 1source
pkgs/python/[email protected]/samples/sample_analyze_general_documents.py:60 - 2sink
pkgs/python/[email protected]/samples/sample_analyze_general_documents.py:128
- 1source
pkgs/python/[email protected]/samples/sample_analyze_identity_documents.py:43 - 2sink
pkgs/python/[email protected]/samples/sample_analyze_identity_documents.py:52
- 1source
pkgs/python/[email protected]/samples/sample_analyze_identity_documents.py:43 - 2sink
pkgs/python/[email protected]/samples/sample_analyze_identity_documents.py:56
- 1source
pkgs/python/[email protected]/samples/sample_analyze_identity_documents.py:43 - 2sink
pkgs/python/[email protected]/samples/sample_analyze_identity_documents.py:59
- 1source
pkgs/python/[email protected]/samples/sample_analyze_identity_documents.py:43 - 2sink
pkgs/python/[email protected]/samples/sample_analyze_identity_documents.py:62
- 1source
pkgs/python/[email protected]/samples/sample_analyze_identity_documents.py:43 - 2sink
pkgs/python/[email protected]/samples/sample_analyze_identity_documents.py:67
- 1source
pkgs/python/[email protected]/samples/sample_analyze_identity_documents.py:43 - 2sink
pkgs/python/[email protected]/samples/sample_analyze_identity_documents.py:70
- 1source
pkgs/python/[email protected]/samples/sample_analyze_identity_documents.py:43 - 2sink
pkgs/python/[email protected]/samples/sample_analyze_identity_documents.py:73
- 1source
pkgs/python/[email protected]/samples/sample_analyze_identity_documents.py:43 - 2sink
pkgs/python/[email protected]/samples/sample_analyze_identity_documents.py:76
- 1source
pkgs/python/[email protected]/samples/sample_analyze_identity_documents.py:43 - 2sink
pkgs/python/[email protected]/samples/sample_analyze_identity_documents.py:79
- 1source
pkgs/python/[email protected]/samples/sample_analyze_identity_documents.py:43 - 2sink
pkgs/python/[email protected]/samples/sample_analyze_identity_documents.py:84
- 1source
pkgs/python/[email protected]/samples/sample_analyze_invoices.py:44 - 2sink
pkgs/python/[email protected]/samples/sample_analyze_invoices.py:53
- 1source
pkgs/python/[email protected]/samples/sample_analyze_invoices.py:44 - 2sink
pkgs/python/[email protected]/samples/sample_analyze_invoices.py:57
- 1source
pkgs/python/[email protected]/samples/sample_analyze_invoices.py:44 - 2sink
pkgs/python/[email protected]/samples/sample_analyze_invoices.py:60
- 1source
pkgs/python/[email protected]/samples/sample_analyze_invoices.py:44 - 2sink
pkgs/python/[email protected]/samples/sample_analyze_invoices.py:65
- 1source
pkgs/python/[email protected]/samples/sample_analyze_invoices.py:44 - 2sink
pkgs/python/[email protected]/samples/sample_analyze_invoices.py:70
- 1source
pkgs/python/[email protected]/samples/sample_analyze_invoices.py:44 - 2sink
pkgs/python/[email protected]/samples/sample_analyze_invoices.py:75
- 1source
pkgs/python/[email protected]/samples/sample_analyze_invoices.py:44 - 2sink
pkgs/python/[email protected]/samples/sample_analyze_invoices.py:78
- 1source
pkgs/python/[email protected]/samples/sample_analyze_invoices.py:44 - 2sink
pkgs/python/[email protected]/samples/sample_analyze_invoices.py:83
- 1source
pkgs/python/[email protected]/samples/sample_analyze_invoices.py:44 - 2sink
pkgs/python/[email protected]/samples/sample_analyze_invoices.py:88
- 1source
pkgs/python/[email protected]/samples/sample_analyze_invoices.py:44 - 2sink
pkgs/python/[email protected]/samples/sample_analyze_invoices.py:91
- 1source
pkgs/python/[email protected]/samples/sample_analyze_invoices.py:44 - 2sink
pkgs/python/[email protected]/samples/sample_analyze_invoices.py:96
- 1source
pkgs/python/[email protected]/samples/sample_analyze_invoices.py:44 - 2sink
pkgs/python/[email protected]/samples/sample_analyze_invoices.py:101
- 1source
pkgs/python/[email protected]/samples/sample_analyze_invoices.py:44 - 2sink
pkgs/python/[email protected]/samples/sample_analyze_invoices.py:104
- 1source
pkgs/python/[email protected]/samples/sample_analyze_invoices.py:44 - 2sink
pkgs/python/[email protected]/samples/sample_analyze_invoices.py:109
- 1source
pkgs/python/[email protected]/samples/sample_analyze_invoices.py:44 - 2sink
pkgs/python/[email protected]/samples/sample_analyze_invoices.py:114
- 1source
pkgs/python/[email protected]/samples/sample_analyze_invoices.py:44 - 2sink
pkgs/python/[email protected]/samples/sample_analyze_invoices.py:119
- 1source
pkgs/python/[email protected]/samples/sample_analyze_invoices.py:44 - 2sink
pkgs/python/[email protected]/samples/sample_analyze_invoices.py:124
- 1source
pkgs/python/[email protected]/samples/sample_analyze_invoices.py:44 - 2sink
pkgs/python/[email protected]/samples/sample_analyze_invoices.py:131
- 1source
pkgs/python/[email protected]/samples/sample_analyze_invoices.py:44 - 2sink
pkgs/python/[email protected]/samples/sample_analyze_invoices.py:134
- 1source
pkgs/python/[email protected]/samples/sample_analyze_invoices.py:44 - 2sink
pkgs/python/[email protected]/samples/sample_analyze_invoices.py:139
- 1source
pkgs/python/[email protected]/samples/sample_analyze_invoices.py:44 - 2sink
pkgs/python/[email protected]/samples/sample_analyze_invoices.py:144
- 1source
pkgs/python/[email protected]/samples/sample_analyze_invoices.py:44 - 2sink
pkgs/python/[email protected]/samples/sample_analyze_invoices.py:152
- 1source
pkgs/python/[email protected]/samples/sample_analyze_invoices.py:44 - 2sink
pkgs/python/[email protected]/samples/sample_analyze_invoices.py:157
- 1source
pkgs/python/[email protected]/samples/sample_analyze_invoices.py:44 - 2sink
pkgs/python/[email protected]/samples/sample_analyze_invoices.py:162
- 1source
pkgs/python/[email protected]/samples/sample_analyze_invoices.py:44 - 2sink
pkgs/python/[email protected]/samples/sample_analyze_invoices.py:167
- 1source
pkgs/python/[email protected]/samples/sample_analyze_invoices.py:44 - 2sink
pkgs/python/[email protected]/samples/sample_analyze_invoices.py:170
- 1source
pkgs/python/[email protected]/samples/sample_analyze_invoices.py:44 - 2sink
pkgs/python/[email protected]/samples/sample_analyze_invoices.py:173
- 1source
pkgs/python/[email protected]/samples/sample_analyze_invoices.py:44 - 2sink
pkgs/python/[email protected]/samples/sample_analyze_invoices.py:176
- 1source
pkgs/python/[email protected]/samples/sample_analyze_invoices.py:44 - 2sink
pkgs/python/[email protected]/samples/sample_analyze_invoices.py:179
- 1source
pkgs/python/[email protected]/samples/sample_analyze_invoices.py:44 - 2sink
pkgs/python/[email protected]/samples/sample_analyze_invoices.py:184
- 1source
pkgs/python/[email protected]/samples/sample_analyze_invoices.py:44 - 2sink
pkgs/python/[email protected]/samples/sample_analyze_invoices.py:187
- 1source
pkgs/python/[email protected]/samples/sample_analyze_invoices.py:44 - 2sink
pkgs/python/[email protected]/samples/sample_analyze_invoices.py:192
- 1source
pkgs/python/[email protected]/samples/sample_analyze_invoices.py:44 - 2sink
pkgs/python/[email protected]/samples/sample_analyze_invoices.py:197
- 1source
pkgs/python/[email protected]/samples/sample_analyze_invoices.py:44 - 2sink
pkgs/python/[email protected]/samples/sample_analyze_invoices.py:202
- 1source
pkgs/python/[email protected]/samples/sample_analyze_invoices.py:44 - 2sink
pkgs/python/[email protected]/samples/sample_analyze_invoices.py:207
- 1source
pkgs/python/[email protected]/samples/sample_analyze_invoices.py:44 - 2sink
pkgs/python/[email protected]/samples/sample_analyze_invoices.py:212
- 1source
pkgs/python/[email protected]/samples/sample_analyze_invoices_from_bytes_source.py:43 - 2sink
pkgs/python/[email protected]/samples/sample_analyze_invoices_from_bytes_source.py:54
- 1source
pkgs/python/[email protected]/samples/sample_analyze_invoices_from_bytes_source.py:43 - 2sink
pkgs/python/[email protected]/samples/sample_analyze_invoices_from_bytes_source.py:58
- 1source
pkgs/python/[email protected]/samples/sample_analyze_invoices_from_bytes_source.py:43 - 2sink
pkgs/python/[email protected]/samples/sample_analyze_invoices_from_bytes_source.py:61
- 1source
pkgs/python/[email protected]/samples/sample_analyze_invoices_from_bytes_source.py:43 - 2sink
pkgs/python/[email protected]/samples/sample_analyze_invoices_from_bytes_source.py:66
- 1source
pkgs/python/[email protected]/samples/sample_analyze_invoices_from_bytes_source.py:43 - 2sink
pkgs/python/[email protected]/samples/sample_analyze_invoices_from_bytes_source.py:71
- 1source
pkgs/python/[email protected]/samples/sample_analyze_invoices_from_bytes_source.py:43 - 2sink
pkgs/python/[email protected]/samples/sample_analyze_invoices_from_bytes_source.py:76
- 1source
pkgs/python/[email protected]/samples/sample_analyze_invoices_from_bytes_source.py:43 - 2sink
pkgs/python/[email protected]/samples/sample_analyze_invoices_from_bytes_source.py:79
- 1source
pkgs/python/[email protected]/samples/sample_analyze_invoices_from_bytes_source.py:43 - 2sink
pkgs/python/[email protected]/samples/sample_analyze_invoices_from_bytes_source.py:84
- 1source
pkgs/python/[email protected]/samples/sample_analyze_invoices_from_bytes_source.py:43 - 2sink
pkgs/python/[email protected]/samples/sample_analyze_invoices_from_bytes_source.py:89
- 1source
pkgs/python/[email protected]/samples/sample_analyze_invoices_from_bytes_source.py:43 - 2sink
pkgs/python/[email protected]/samples/sample_analyze_invoices_from_bytes_source.py:92
- 1source
pkgs/python/[email protected]/samples/sample_analyze_invoices_from_bytes_source.py:43 - 2sink
pkgs/python/[email protected]/samples/sample_analyze_invoices_from_bytes_source.py:97
- 1source
pkgs/python/[email protected]/samples/sample_analyze_invoices_from_bytes_source.py:43 - 2sink
pkgs/python/[email protected]/samples/sample_analyze_invoices_from_bytes_source.py:102
- 1source
pkgs/python/[email protected]/samples/sample_analyze_invoices_from_bytes_source.py:43 - 2sink
pkgs/python/[email protected]/samples/sample_analyze_invoices_from_bytes_source.py:105
- 1source
pkgs/python/[email protected]/samples/sample_analyze_invoices_from_bytes_source.py:43 - 2sink
pkgs/python/[email protected]/samples/sample_analyze_invoices_from_bytes_source.py:110
- 1source
pkgs/python/[email protected]/samples/sample_analyze_invoices_from_bytes_source.py:43 - 2sink
pkgs/python/[email protected]/samples/sample_analyze_invoices_from_bytes_source.py:115
- 1source
pkgs/python/[email protected]/samples/sample_analyze_invoices_from_bytes_source.py:43 - 2sink
pkgs/python/[email protected]/samples/sample_analyze_invoices_from_bytes_source.py:120
- 1source
pkgs/python/[email protected]/samples/sample_analyze_invoices_from_bytes_source.py:43 - 2sink
pkgs/python/[email protected]/samples/sample_analyze_invoices_from_bytes_source.py:125
- 1source
pkgs/python/[email protected]/samples/sample_analyze_invoices_from_bytes_source.py:43 - 2sink
pkgs/python/[email protected]/samples/sample_analyze_invoices_from_bytes_source.py:132
- 1source
pkgs/python/[email protected]/samples/sample_analyze_invoices_from_bytes_source.py:43 - 2sink
pkgs/python/[email protected]/samples/sample_analyze_invoices_from_bytes_source.py:135
- 1source
pkgs/python/[email protected]/samples/sample_analyze_invoices_from_bytes_source.py:43 - 2sink
pkgs/python/[email protected]/samples/sample_analyze_invoices_from_bytes_source.py:140
- 1source
pkgs/python/[email protected]/samples/sample_analyze_invoices_from_bytes_source.py:43 - 2sink
pkgs/python/[email protected]/samples/sample_analyze_invoices_from_bytes_source.py:145
- 1source
pkgs/python/[email protected]/samples/sample_analyze_invoices_from_bytes_source.py:43 - 2sink
pkgs/python/[email protected]/samples/sample_analyze_invoices_from_bytes_source.py:153
- 1source
pkgs/python/[email protected]/samples/sample_analyze_invoices_from_bytes_source.py:43 - 2sink
pkgs/python/[email protected]/samples/sample_analyze_invoices_from_bytes_source.py:158
- 1source
pkgs/python/[email protected]/samples/sample_analyze_invoices_from_bytes_source.py:43 - 2sink
pkgs/python/[email protected]/samples/sample_analyze_invoices_from_bytes_source.py:163
- 1source
pkgs/python/[email protected]/samples/sample_analyze_invoices_from_bytes_source.py:43 - 2sink
pkgs/python/[email protected]/samples/sample_analyze_invoices_from_bytes_source.py:168
- 1source
pkgs/python/[email protected]/samples/sample_analyze_invoices_from_bytes_source.py:43 - 2sink
pkgs/python/[email protected]/samples/sample_analyze_invoices_from_bytes_source.py:171
- 1source
pkgs/python/[email protected]/samples/sample_analyze_invoices_from_bytes_source.py:43 - 2sink
pkgs/python/[email protected]/samples/sample_analyze_invoices_from_bytes_source.py:174
- 1source
pkgs/python/[email protected]/samples/sample_analyze_invoices_from_bytes_source.py:43 - 2sink
pkgs/python/[email protected]/samples/sample_analyze_invoices_from_bytes_source.py:177
- 1source
pkgs/python/[email protected]/samples/sample_analyze_invoices_from_bytes_source.py:43 - 2sink
pkgs/python/[email protected]/samples/sample_analyze_invoices_from_bytes_source.py:180
- 1source
pkgs/python/[email protected]/samples/sample_analyze_invoices_from_bytes_source.py:43 - 2sink
pkgs/python/[email protected]/samples/sample_analyze_invoices_from_bytes_source.py:185
- 1source
pkgs/python/[email protected]/samples/sample_analyze_invoices_from_bytes_source.py:43 - 2sink
pkgs/python/[email protected]/samples/sample_analyze_invoices_from_bytes_source.py:188
- 1source
pkgs/python/[email protected]/samples/sample_analyze_invoices_from_bytes_source.py:43 - 2sink
pkgs/python/[email protected]/samples/sample_analyze_invoices_from_bytes_source.py:193
- 1source
pkgs/python/[email protected]/samples/sample_analyze_invoices_from_bytes_source.py:43 - 2sink
pkgs/python/[email protected]/samples/sample_analyze_invoices_from_bytes_source.py:198
- 1source
pkgs/python/[email protected]/samples/sample_analyze_invoices_from_bytes_source.py:43 - 2sink
pkgs/python/[email protected]/samples/sample_analyze_invoices_from_bytes_source.py:203
- 1source
pkgs/python/[email protected]/samples/sample_analyze_invoices_from_bytes_source.py:43 - 2sink
pkgs/python/[email protected]/samples/sample_analyze_invoices_from_bytes_source.py:208
- 1source
pkgs/python/[email protected]/samples/sample_analyze_invoices_from_bytes_source.py:43 - 2sink
pkgs/python/[email protected]/samples/sample_analyze_invoices_from_bytes_source.py:213
- 1source
pkgs/python/[email protected]/samples/sample_analyze_layout.py:57 - 2sink
pkgs/python/[email protected]/samples/sample_analyze_layout.py:70
- 1source
pkgs/python/[email protected]/samples/sample_analyze_layout.py:57 - 2sink
pkgs/python/[email protected]/samples/sample_analyze_layout.py:71
- 1source
pkgs/python/[email protected]/samples/sample_analyze_layout.py:57 - 2sink
pkgs/python/[email protected]/samples/sample_analyze_layout.py:78
- 1source
pkgs/python/[email protected]/samples/sample_analyze_layout.py:57 - 2sink
pkgs/python/[email protected]/samples/sample_analyze_layout.py:81
- 1source
pkgs/python/[email protected]/samples/sample_analyze_layout.py:57 - 2sink
pkgs/python/[email protected]/samples/sample_analyze_layout.py:88
- 1source
pkgs/python/[email protected]/samples/sample_analyze_layout.py:57 - 2sink
pkgs/python/[email protected]/samples/sample_analyze_layout.py:94
- 1source
pkgs/python/[email protected]/samples/sample_analyze_layout.py:57 - 2sink
pkgs/python/[email protected]/samples/sample_analyze_layout.py:100
- 1source
pkgs/python/[email protected]/samples/sample_analyze_layout.py:57 - 2sink
pkgs/python/[email protected]/samples/sample_analyze_layout.py:102
- 1source
pkgs/python/[email protected]/samples/sample_analyze_layout.py:57 - 2sink
pkgs/python/[email protected]/samples/sample_analyze_layout.py:103
- 1source
pkgs/python/[email protected]/samples/sample_analyze_layout.py:57 - 2sink
pkgs/python/[email protected]/samples/sample_analyze_layout.py:109
- 1source
pkgs/python/[email protected]/samples/sample_analyze_layout.py:57 - 2sink
pkgs/python/[email protected]/samples/sample_analyze_layout.py:110
- 1source
pkgs/python/[email protected]/samples/sample_analyze_layout.py:57 - 2sink
pkgs/python/[email protected]/samples/sample_analyze_layout.py:114
- 1source
pkgs/python/[email protected]/samples/sample_analyze_layout.py:57 - 2sink
pkgs/python/[email protected]/samples/sample_analyze_layout.py:117
- 1source
pkgs/python/[email protected]/samples/sample_analyze_layout.py:57 - 2sink
pkgs/python/[email protected]/samples/sample_analyze_layout.py:121
- 1source
pkgs/python/[email protected]/samples/sample_analyze_layout.py:57 - 2sink
pkgs/python/[email protected]/samples/sample_analyze_layout.py:124
- 1source
pkgs/python/[email protected]/samples/sample_analyze_read.py:68 - 2sink
pkgs/python/[email protected]/samples/sample_analyze_read.py:82
- 1source
pkgs/python/[email protected]/samples/sample_analyze_read.py:68 - 2sink
pkgs/python/[email protected]/samples/sample_analyze_read.py:91
- 1source
pkgs/python/[email protected]/samples/sample_analyze_read.py:68 - 2sink
pkgs/python/[email protected]/samples/sample_analyze_read.py:95
- 1source
pkgs/python/[email protected]/samples/sample_analyze_read.py:68 - 2sink
pkgs/python/[email protected]/samples/sample_analyze_read.py:96
- 1source
pkgs/python/[email protected]/samples/sample_analyze_read.py:68 - 2sink
pkgs/python/[email protected]/samples/sample_analyze_read.py:101
- 1source
pkgs/python/[email protected]/samples/sample_analyze_read.py:68 - 2sink
pkgs/python/[email protected]/samples/sample_analyze_read.py:108
- 1source
pkgs/python/[email protected]/samples/sample_analyze_read.py:68 - 2sink
pkgs/python/[email protected]/samples/sample_analyze_read.py:112
- 1source
pkgs/python/[email protected]/samples/sample_analyze_read.py:68 - 2sink
pkgs/python/[email protected]/samples/sample_analyze_read.py:118
- 1source
pkgs/python/[email protected]/samples/sample_analyze_read.py:68 - 2sink
pkgs/python/[email protected]/samples/sample_analyze_read.py:123
- 1source
pkgs/python/[email protected]/samples/sample_analyze_read.py:68 - 2sink
pkgs/python/[email protected]/samples/sample_analyze_read.py:127
- 1source
pkgs/python/[email protected]/samples/sample_analyze_read.py:68 - 2sink
pkgs/python/[email protected]/samples/sample_analyze_read.py:128
- 1source
pkgs/python/[email protected]/samples/sample_analyze_receipts.py:50 - 2sink
pkgs/python/[email protected]/samples/sample_analyze_receipts.py:59
- 1source
pkgs/python/[email protected]/samples/sample_analyze_receipts.py:50 - 2sink
pkgs/python/[email protected]/samples/sample_analyze_receipts.py:60
- 1source
pkgs/python/[email protected]/samples/sample_analyze_receipts.py:50 - 2sink
pkgs/python/[email protected]/samples/sample_analyze_receipts.py:64
- 1source
pkgs/python/[email protected]/samples/sample_analyze_receipts.py:50 - 2sink
pkgs/python/[email protected]/samples/sample_analyze_receipts.py:70
- 1source
pkgs/python/[email protected]/samples/sample_analyze_receipts.py:50 - 2sink
pkgs/python/[email protected]/samples/sample_analyze_receipts.py:78
- 1source
pkgs/python/[email protected]/samples/sample_analyze_receipts.py:50 - 2sink
pkgs/python/[email protected]/samples/sample_analyze_receipts.py:81
- 1source
pkgs/python/[email protected]/samples/sample_analyze_receipts.py:50 - 2sink
pkgs/python/[email protected]/samples/sample_analyze_receipts.py:87
- 1source
pkgs/python/[email protected]/samples/sample_analyze_receipts.py:50 - 2sink
pkgs/python/[email protected]/samples/sample_analyze_receipts.py:93
- 1source
pkgs/python/[email protected]/samples/sample_analyze_receipts.py:50 - 2sink
pkgs/python/[email protected]/samples/sample_analyze_receipts.py:99
- 1source
pkgs/python/[email protected]/samples/sample_analyze_receipts.py:50 - 2sink
pkgs/python/[email protected]/samples/sample_analyze_receipts.py:104
- 1source
pkgs/python/[email protected]/samples/sample_analyze_receipts.py:50 - 2sink
pkgs/python/[email protected]/samples/sample_analyze_receipts.py:107
- 1source
pkgs/python/[email protected]/samples/sample_analyze_receipts.py:50 - 2sink
pkgs/python/[email protected]/samples/sample_analyze_receipts.py:110
- 1source
pkgs/python/[email protected]/samples/sample_analyze_receipts_from_url.py:41 - 2sink
pkgs/python/[email protected]/samples/sample_analyze_receipts_from_url.py:53
- 1source
pkgs/python/[email protected]/samples/sample_analyze_receipts_from_url.py:41 - 2sink
pkgs/python/[email protected]/samples/sample_analyze_receipts_from_url.py:54
- 1source
pkgs/python/[email protected]/samples/sample_analyze_receipts_from_url.py:41 - 2sink
pkgs/python/[email protected]/samples/sample_analyze_receipts_from_url.py:58
- 1source
pkgs/python/[email protected]/samples/sample_analyze_receipts_from_url.py:41 - 2sink
pkgs/python/[email protected]/samples/sample_analyze_receipts_from_url.py:64
- 1source
pkgs/python/[email protected]/samples/sample_analyze_receipts_from_url.py:41 - 2sink
pkgs/python/[email protected]/samples/sample_analyze_receipts_from_url.py:72
- 1source
pkgs/python/[email protected]/samples/sample_analyze_receipts_from_url.py:41 - 2sink
pkgs/python/[email protected]/samples/sample_analyze_receipts_from_url.py:75
- 1source
pkgs/python/[email protected]/samples/sample_analyze_receipts_from_url.py:41 - 2sink
pkgs/python/[email protected]/samples/sample_analyze_receipts_from_url.py:81
- 1source
pkgs/python/[email protected]/samples/sample_analyze_receipts_from_url.py:41 - 2sink
pkgs/python/[email protected]/samples/sample_analyze_receipts_from_url.py:87
- 1source
pkgs/python/[email protected]/samples/sample_analyze_receipts_from_url.py:41 - 2sink
pkgs/python/[email protected]/samples/sample_analyze_receipts_from_url.py:93
- 1source
pkgs/python/[email protected]/samples/sample_analyze_receipts_from_url.py:41 - 2sink
pkgs/python/[email protected]/samples/sample_analyze_receipts_from_url.py:98
- 1source
pkgs/python/[email protected]/samples/sample_analyze_receipts_from_url.py:41 - 2sink
pkgs/python/[email protected]/samples/sample_analyze_receipts_from_url.py:101
- 1source
pkgs/python/[email protected]/samples/sample_analyze_receipts_from_url.py:41 - 2sink
pkgs/python/[email protected]/samples/sample_analyze_receipts_from_url.py:104
- 1source
pkgs/python/[email protected]/samples/sample_analyze_tax_us_w2.py:47 - 2sink
pkgs/python/[email protected]/samples/sample_analyze_tax_us_w2.py:56
- 1source
pkgs/python/[email protected]/samples/sample_analyze_tax_us_w2.py:47 - 2sink
pkgs/python/[email protected]/samples/sample_analyze_tax_us_w2.py:60
- 1source
pkgs/python/[email protected]/samples/sample_analyze_tax_us_w2.py:47 - 2sink
pkgs/python/[email protected]/samples/sample_analyze_tax_us_w2.py:65
- 1source
pkgs/python/[email protected]/samples/sample_analyze_tax_us_w2.py:47 - 2sink
pkgs/python/[email protected]/samples/sample_analyze_tax_us_w2.py:68
- 1source
pkgs/python/[email protected]/samples/sample_analyze_tax_us_w2.py:47 - 2sink
pkgs/python/[email protected]/samples/sample_analyze_tax_us_w2.py:74
- 1source
pkgs/python/[email protected]/samples/sample_analyze_tax_us_w2.py:47 - 2sink
pkgs/python/[email protected]/samples/sample_analyze_tax_us_w2.py:77
- 1source
pkgs/python/[email protected]/samples/sample_analyze_tax_us_w2.py:47 - 2sink
pkgs/python/[email protected]/samples/sample_analyze_tax_us_w2.py:80
- 1source
pkgs/python/[email protected]/samples/sample_analyze_tax_us_w2.py:47 - 2sink
pkgs/python/[email protected]/samples/sample_analyze_tax_us_w2.py:81
- 1source
pkgs/python/[email protected]/samples/sample_analyze_tax_us_w2.py:47 - 2sink
pkgs/python/[email protected]/samples/sample_analyze_tax_us_w2.py:84
- 1source
pkgs/python/[email protected]/samples/sample_analyze_tax_us_w2.py:47 - 2sink
pkgs/python/[email protected]/samples/sample_analyze_tax_us_w2.py:87
- 1source
pkgs/python/[email protected]/samples/sample_analyze_tax_us_w2.py:47 - 2sink
pkgs/python/[email protected]/samples/sample_analyze_tax_us_w2.py:96
- 1source
pkgs/python/[email protected]/samples/sample_analyze_tax_us_w2.py:47 - 2sink
pkgs/python/[email protected]/samples/sample_analyze_tax_us_w2.py:99
- 1source
pkgs/python/[email protected]/samples/sample_analyze_tax_us_w2.py:47 - 2sink
pkgs/python/[email protected]/samples/sample_analyze_tax_us_w2.py:104
- 1source
pkgs/python/[email protected]/samples/sample_analyze_tax_us_w2.py:47 - 2sink
pkgs/python/[email protected]/samples/sample_analyze_tax_us_w2.py:105
- 1source
pkgs/python/[email protected]/samples/sample_analyze_tax_us_w2.py:47 - 2sink
pkgs/python/[email protected]/samples/sample_analyze_tax_us_w2.py:108
- 1source
pkgs/python/[email protected]/samples/sample_analyze_tax_us_w2.py:47 - 2sink
pkgs/python/[email protected]/samples/sample_analyze_tax_us_w2.py:111
- 1source
pkgs/python/[email protected]/samples/sample_analyze_tax_us_w2.py:47 - 2sink
pkgs/python/[email protected]/samples/sample_analyze_tax_us_w2.py:117
- 1source
pkgs/python/[email protected]/samples/sample_analyze_tax_us_w2.py:47 - 2sink
pkgs/python/[email protected]/samples/sample_analyze_tax_us_w2.py:123
- 1source
pkgs/python/[email protected]/samples/sample_analyze_tax_us_w2.py:47 - 2sink
pkgs/python/[email protected]/samples/sample_analyze_tax_us_w2.py:129
- 1source
pkgs/python/[email protected]/samples/sample_analyze_tax_us_w2.py:47 - 2sink
pkgs/python/[email protected]/samples/sample_analyze_tax_us_w2.py:135
- 1source
pkgs/python/[email protected]/samples/sample_analyze_tax_us_w2.py:47 - 2sink
pkgs/python/[email protected]/samples/sample_analyze_tax_us_w2.py:141
- 1source
pkgs/python/[email protected]/samples/sample_analyze_tax_us_w2.py:47 - 2sink
pkgs/python/[email protected]/samples/sample_analyze_tax_us_w2.py:147
- 1source
pkgs/python/[email protected]/samples/sample_analyze_tax_us_w2.py:47 - 2sink
pkgs/python/[email protected]/samples/sample_analyze_tax_us_w2.py:153
- 1source
pkgs/python/[email protected]/samples/sample_analyze_tax_us_w2.py:47 - 2sink
pkgs/python/[email protected]/samples/sample_analyze_tax_us_w2.py:158
- 1source
pkgs/python/[email protected]/samples/sample_analyze_tax_us_w2.py:47 - 2sink
pkgs/python/[email protected]/samples/sample_analyze_tax_us_w2.py:163
- 1source
pkgs/python/[email protected]/samples/sample_analyze_tax_us_w2.py:47 - 2sink
pkgs/python/[email protected]/samples/sample_analyze_tax_us_w2.py:168
- 1source
pkgs/python/[email protected]/samples/sample_analyze_tax_us_w2.py:47 - 2sink
pkgs/python/[email protected]/samples/sample_analyze_tax_us_w2.py:177
- 1source
pkgs/python/[email protected]/samples/sample_analyze_tax_us_w2.py:47 - 2sink
pkgs/python/[email protected]/samples/sample_analyze_tax_us_w2.py:182
- 1source
pkgs/python/[email protected]/samples/sample_analyze_tax_us_w2.py:47 - 2sink
pkgs/python/[email protected]/samples/sample_analyze_tax_us_w2.py:185
- 1source
pkgs/python/[email protected]/samples/sample_analyze_tax_us_w2.py:47 - 2sink
pkgs/python/[email protected]/samples/sample_analyze_tax_us_w2.py:190
- 1source
pkgs/python/[email protected]/samples/sample_analyze_tax_us_w2.py:47 - 2sink
pkgs/python/[email protected]/samples/sample_analyze_tax_us_w2.py:195
- 1source
pkgs/python/[email protected]/samples/sample_analyze_tax_us_w2.py:47 - 2sink
pkgs/python/[email protected]/samples/sample_analyze_tax_us_w2.py:200
- 1source
pkgs/python/[email protected]/samples/sample_analyze_tax_us_w2.py:47 - 2sink
pkgs/python/[email protected]/samples/sample_analyze_tax_us_w2.py:207
- 1source
pkgs/python/[email protected]/samples/sample_analyze_tax_us_w2.py:47 - 2sink
pkgs/python/[email protected]/samples/sample_analyze_tax_us_w2.py:210
- 1source
pkgs/python/[email protected]/samples/sample_analyze_tax_us_w2.py:47 - 2sink
pkgs/python/[email protected]/samples/sample_analyze_tax_us_w2.py:216
- 1source
pkgs/python/[email protected]/samples/sample_analyze_tax_us_w2.py:47 - 2sink
pkgs/python/[email protected]/samples/sample_analyze_tax_us_w2.py:222
- 1source
pkgs/python/[email protected]/samples/sample_analyze_tax_us_w2.py:47 - 2sink
pkgs/python/[email protected]/samples/sample_analyze_tax_us_w2.py:232
- 1source
pkgs/python/[email protected]/samples/sample_analyze_tax_us_w2.py:47 - 2sink
pkgs/python/[email protected]/samples/sample_analyze_tax_us_w2.py:238
- 1source
pkgs/python/[email protected]/samples/sample_analyze_tax_us_w2.py:47 - 2sink
pkgs/python/[email protected]/samples/sample_analyze_tax_us_w2.py:244
- 1source
pkgs/python/[email protected]/samples/sample_classify_document.py:49 - 2sink
pkgs/python/[email protected]/samples/sample_classify_document.py:61
- 1source
pkgs/python/[email protected]/samples/sample_compose_model.py:56 - 2sink
pkgs/python/[email protected]/samples/sample_compose_model.py:116
- 1source
pkgs/python/[email protected]/samples/sample_compose_model.py:56 - 2sink
pkgs/python/[email protected]/samples/sample_compose_model.py:117
- 1source
pkgs/python/[email protected]/samples/sample_compose_model.py:56 - 2sink
pkgs/python/[email protected]/samples/sample_compose_model.py:118
- 1source
pkgs/python/[email protected]/samples/sample_compose_model.py:56 - 2sink
pkgs/python/[email protected]/samples/sample_compose_model.py:119
- 1source
pkgs/python/[email protected]/samples/sample_compose_model.py:56 - 2sink
pkgs/python/[email protected]/samples/sample_compose_model.py:123
- 1source
pkgs/python/[email protected]/samples/sample_compose_model.py:56 - 2sink
pkgs/python/[email protected]/samples/sample_compose_model.py:126
- 1source
pkgs/python/[email protected]/samples/sample_compose_model.py:56 - 2sink
pkgs/python/[email protected]/samples/sample_compose_model.py:133
- 1source
pkgs/python/[email protected]/samples/sample_convert_to_and_from_dict.py:44 - 2sink
pkgs/python/[email protected]/samples/sample_convert_to_and_from_dict.py:63
- 1source
pkgs/python/[email protected]/samples/sample_convert_to_and_from_dict.py:44 - 2sink
pkgs/python/[email protected]/samples/sample_convert_to_and_from_dict.py:64
- 1source
pkgs/python/[email protected]/samples/sample_convert_to_and_from_dict.py:44 - 2sink
pkgs/python/[email protected]/samples/sample_convert_to_and_from_dict.py:65
- 1source
pkgs/python/[email protected]/samples/sample_copy_model_to.py:41 - 2sink
pkgs/python/[email protected]/samples/sample_copy_model_to.py:65
- 1source
pkgs/python/[email protected]/samples/sample_copy_model_to.py:41 - 2sink
pkgs/python/[email protected]/samples/sample_copy_model_to.py:66
- 1source
pkgs/python/[email protected]/samples/sample_copy_model_to.py:41 - 2sink
pkgs/python/[email protected]/samples/sample_copy_model_to.py:67
- 1source
pkgs/python/[email protected]/samples/sample_copy_model_to.py:41 - 2sink
pkgs/python/[email protected]/samples/sample_copy_model_to.py:68
- 1source
pkgs/python/[email protected]/samples/sample_copy_model_to.py:41 - 2sink
pkgs/python/[email protected]/samples/sample_copy_model_to.py:72
- 1source
pkgs/python/[email protected]/samples/sample_copy_model_to.py:41 - 2sink
pkgs/python/[email protected]/samples/sample_copy_model_to.py:76
- 1source
pkgs/python/[email protected]/samples/sample_copy_model_to.py:41 - 2sink
pkgs/python/[email protected]/samples/sample_copy_model_to.py:83
- 1source
pkgs/python/[email protected]/samples/sample_manage_classifiers.py:41 - 2sink
pkgs/python/[email protected]/samples/sample_manage_classifiers.py:64
- 1source
pkgs/python/[email protected]/samples/sample_manage_classifiers.py:41 - 2sink
pkgs/python/[email protected]/samples/sample_manage_classifiers.py:65
- 1source
pkgs/python/[email protected]/samples/sample_manage_classifiers.py:41 - 2sink
pkgs/python/[email protected]/samples/sample_manage_classifiers.py:66
- 1source
pkgs/python/[email protected]/samples/sample_manage_classifiers.py:41 - 2sink
pkgs/python/[email protected]/samples/sample_manage_classifiers.py:69
- 1source
pkgs/python/[email protected]/samples/sample_manage_classifiers.py:41 - 2sink
pkgs/python/[email protected]/samples/sample_manage_classifiers.py:71
- 1source
pkgs/python/[email protected]/samples/sample_manage_classifiers.py:41 - 2sink
pkgs/python/[email protected]/samples/sample_manage_classifiers.py:80
- 1source
pkgs/python/[email protected]/samples/sample_manage_classifiers.py:41 - 2sink
pkgs/python/[email protected]/samples/sample_manage_classifiers.py:85
- 1source
pkgs/python/[email protected]/samples/sample_manage_classifiers.py:41 - 2sink
pkgs/python/[email protected]/samples/sample_manage_classifiers.py:86
- 1source
pkgs/python/[email protected]/samples/sample_manage_classifiers.py:41 - 2sink
pkgs/python/[email protected]/samples/sample_manage_classifiers.py:87
- 1source
pkgs/python/[email protected]/samples/sample_manage_classifiers.py:41 - 2sink
pkgs/python/[email protected]/samples/sample_manage_classifiers.py:88
- 1source
pkgs/python/[email protected]/samples/sample_manage_classifiers.py:41 - 2sink
pkgs/python/[email protected]/samples/sample_manage_classifiers.py:101
- 1source
pkgs/python/[email protected]/samples/sample_manage_models.py:42 - 2sink
pkgs/python/[email protected]/samples/sample_manage_models.py:56
- 1source
pkgs/python/[email protected]/samples/sample_manage_models.py:42 - 2sink
pkgs/python/[email protected]/samples/sample_manage_models.py:57
- 1source
pkgs/python/[email protected]/samples/sample_manage_models.py:42 - 2sink
pkgs/python/[email protected]/samples/sample_manage_models.py:58
- 1source
pkgs/python/[email protected]/samples/sample_manage_models.py:42 - 2sink
pkgs/python/[email protected]/samples/sample_manage_models.py:59
- 1source
pkgs/python/[email protected]/samples/sample_manage_models.py:42 - 2sink
pkgs/python/[email protected]/samples/sample_manage_models.py:63
- 1source
pkgs/python/[email protected]/samples/sample_manage_models.py:42 - 2sink
pkgs/python/[email protected]/samples/sample_manage_models.py:67
- 1source
pkgs/python/[email protected]/samples/sample_manage_models.py:42 - 2sink
pkgs/python/[email protected]/samples/sample_manage_models.py:75
- 1source
pkgs/python/[email protected]/samples/sample_manage_models.py:42 - 2sink
pkgs/python/[email protected]/samples/sample_manage_models.py:87
- 1source
pkgs/python/[email protected]/samples/sample_manage_models.py:42 - 2sink
pkgs/python/[email protected]/samples/sample_manage_models.py:92
- 1source
pkgs/python/[email protected]/samples/sample_manage_models.py:42 - 2sink
pkgs/python/[email protected]/samples/sample_manage_models.py:93
- 1source
pkgs/python/[email protected]/samples/sample_manage_models.py:42 - 2sink
pkgs/python/[email protected]/samples/sample_manage_models.py:94
- 1source
pkgs/python/[email protected]/samples/sample_manage_models.py:42 - 2sink
pkgs/python/[email protected]/samples/sample_manage_models.py:95
- 1source
pkgs/python/[email protected]/samples/sample_manage_models.py:42 - 2sink
pkgs/python/[email protected]/samples/sample_manage_models.py:99
- 1source
pkgs/python/[email protected]/samples/sample_manage_models.py:42 - 2sink
pkgs/python/[email protected]/samples/sample_manage_models.py:111
- 1source
pkgs/python/[email protected]/samples/sample_send_request.py:32 - 2sink
pkgs/python/[email protected]/samples/sample_send_request.py:43
</> First-Party Code
first-party (python): backend/open_webui/utils/telemetry
python first-partyfrom opentelemetry.semconv._incubating.attributes import (
db_attributes as _db,
A telemetry/analytics SDK is used; event data is sent to a third-party collector.
Fix: Ensure user consent and a lawful basis; strip PII from event payloads.
from opentelemetry.semconv._incubating.attributes import (
http_attributes as _http,
A telemetry/analytics SDK is used; event data is sent to a third-party collector.
Fix: Ensure user consent and a lawful basis; strip PII from event payloads.
from opentelemetry.instrumentation.aiohttp_client import AioHttpClientInstrumentor
A telemetry/analytics SDK is used; event data is sent to a third-party collector.
Fix: Ensure user consent and a lawful basis; strip PII from event payloads.
from opentelemetry.instrumentation.fastapi import FastAPIInstrumentor
A telemetry/analytics SDK is used; event data is sent to a third-party collector.
Fix: Ensure user consent and a lawful basis; strip PII from event payloads.
from opentelemetry.instrumentation.httpx import (
HTTPXClientInstrumentor,
RequestInfo,
ResponseInfo,
A telemetry/analytics SDK is used; event data is sent to a third-party collector.
Fix: Ensure user consent and a lawful basis; strip PII from event payloads.
from opentelemetry.instrumentation.instrumentor import BaseInstrumentor
A telemetry/analytics SDK is used; event data is sent to a third-party collector.
Fix: Ensure user consent and a lawful basis; strip PII from event payloads.
from opentelemetry.instrumentation.logging import LoggingInstrumentor
A telemetry/analytics SDK is used; event data is sent to a third-party collector.
Fix: Ensure user consent and a lawful basis; strip PII from event payloads.
from opentelemetry.instrumentation.redis import RedisInstrumentor
A telemetry/analytics SDK is used; event data is sent to a third-party collector.
Fix: Ensure user consent and a lawful basis; strip PII from event payloads.
from opentelemetry.instrumentation.requests import RequestsInstrumentor
A telemetry/analytics SDK is used; event data is sent to a third-party collector.
Fix: Ensure user consent and a lawful basis; strip PII from event payloads.
from opentelemetry.instrumentation.sqlalchemy import SQLAlchemyInstrumentor
A telemetry/analytics SDK is used; event data is sent to a third-party collector.
Fix: Ensure user consent and a lawful basis; strip PII from event payloads.
from opentelemetry.instrumentation.system_metrics import SystemMetricsInstrumentor
A telemetry/analytics SDK is used; event data is sent to a third-party collector.
Fix: Ensure user consent and a lawful basis; strip PII from event payloads.
from opentelemetry.trace import Span, StatusCode
A telemetry/analytics SDK is used; event data is sent to a third-party collector.
Fix: Ensure user consent and a lawful basis; strip PII from event payloads.
from opentelemetry._logs import set_logger_provider
A telemetry/analytics SDK is used; event data is sent to a third-party collector.
Fix: Ensure user consent and a lawful basis; strip PII from event payloads.
from opentelemetry.exporter.otlp.proto.grpc._log_exporter import OTLPLogExporter
A telemetry/analytics SDK is used; event data is sent to a third-party collector.
Fix: Ensure user consent and a lawful basis; strip PII from event payloads.
from opentelemetry.exporter.otlp.proto.http._log_exporter import (
OTLPLogExporter as HttpOTLPLogExporter,
A telemetry/analytics SDK is used; event data is sent to a third-party collector.
Fix: Ensure user consent and a lawful basis; strip PII from event payloads.
from opentelemetry.sdk._logs import (
LoggerProvider,
LoggingHandler,
A telemetry/analytics SDK is used; event data is sent to a third-party collector.
Fix: Ensure user consent and a lawful basis; strip PII from event payloads.
from opentelemetry.sdk._logs.export import BatchLogRecordProcessor
A telemetry/analytics SDK is used; event data is sent to a third-party collector.
Fix: Ensure user consent and a lawful basis; strip PII from event payloads.
from opentelemetry.sdk.resources import SERVICE_NAME, Resource
A telemetry/analytics SDK is used; event data is sent to a third-party collector.
Fix: Ensure user consent and a lawful basis; strip PII from event payloads.
from opentelemetry import metrics
A telemetry/analytics SDK is used; event data is sent to a third-party collector.
Fix: Ensure user consent and a lawful basis; strip PII from event payloads.
from opentelemetry.exporter.otlp.proto.grpc.metric_exporter import (
OTLPMetricExporter,
A telemetry/analytics SDK is used; event data is sent to a third-party collector.
Fix: Ensure user consent and a lawful basis; strip PII from event payloads.
from opentelemetry.exporter.otlp.proto.http.metric_exporter import (
OTLPMetricExporter as OTLPHttpMetricExporter,
A telemetry/analytics SDK is used; event data is sent to a third-party collector.
Fix: Ensure user consent and a lawful basis; strip PII from event payloads.
from opentelemetry.sdk.metrics import MeterProvider
A telemetry/analytics SDK is used; event data is sent to a third-party collector.
Fix: Ensure user consent and a lawful basis; strip PII from event payloads.
from opentelemetry.sdk.metrics.export import (
PeriodicExportingMetricReader,
A telemetry/analytics SDK is used; event data is sent to a third-party collector.
Fix: Ensure user consent and a lawful basis; strip PII from event payloads.
from opentelemetry.sdk.metrics.view import View
A telemetry/analytics SDK is used; event data is sent to a third-party collector.
Fix: Ensure user consent and a lawful basis; strip PII from event payloads.
from opentelemetry.sdk.resources import Resource
A telemetry/analytics SDK is used; event data is sent to a third-party collector.
Fix: Ensure user consent and a lawful basis; strip PII from event payloads.
from opentelemetry import trace
A telemetry/analytics SDK is used; event data is sent to a third-party collector.
Fix: Ensure user consent and a lawful basis; strip PII from event payloads.
from opentelemetry.exporter.otlp.proto.grpc.trace_exporter import OTLPSpanExporter
A telemetry/analytics SDK is used; event data is sent to a third-party collector.
Fix: Ensure user consent and a lawful basis; strip PII from event payloads.
from opentelemetry.exporter.otlp.proto.http.trace_exporter import (
OTLPSpanExporter as HttpOTLPSpanExporter,
A telemetry/analytics SDK is used; event data is sent to a third-party collector.
Fix: Ensure user consent and a lawful basis; strip PII from event payloads.
from opentelemetry.sdk.resources import SERVICE_NAME, Resource
A telemetry/analytics SDK is used; event data is sent to a third-party collector.
Fix: Ensure user consent and a lawful basis; strip PII from event payloads.
from opentelemetry.sdk.trace import TracerProvider
A telemetry/analytics SDK is used; event data is sent to a third-party collector.
Fix: Ensure user consent and a lawful basis; strip PII from event payloads.
from opentelemetry.sdk.trace.export import BatchSpanProcessor
A telemetry/analytics SDK is used; event data is sent to a third-party collector.
Fix: Ensure user consent and a lawful basis; strip PII from event payloads.
first-party (python)
python first-party response = requests.get(url, headers=headers)
A credential (read from the environment/filesystem, or parsed from the request URL) is applied as authorization on the same outbound request. This is intentional authentication to the service the credential belongs to, not unexpected data exfiltration.
Fix: Confirm the destination is the credential's own service; scope the credential and avoid logging it. No action if this is the intended authenticated API call.
headers=headers,
A credential (read from the environment/filesystem, or parsed from the request URL) is applied as authorization on the same outbound request. This is intentional authentication to the service the credential belongs to, not unexpected data exfiltration.
Fix: Confirm the destination is the credential's own service; scope the credential and avoid logging it. No action if this is the intended authenticated API call.
poll_response = requests.get(check_url, headers=headers)
A credential (read from the environment/filesystem, or parsed from the request URL) is applied as authorization on the same outbound request. This is intentional authentication to the service the credential belongs to, not unexpected data exfiltration.
Fix: Confirm the destination is the credential's own service; scope the credential and avoid logging it. No action if this is the intended authenticated API call.
response = requests.put(f'{url}/process', data=data, headers=headers)
A credential (read from the environment/filesystem, or parsed from the request URL) is applied as authorization on the same outbound request. This is intentional authentication to the service the credential belongs to, not unexpected data exfiltration.
Fix: Confirm the destination is the credential's own service; scope the credential and avoid logging it. No action if this is the intended authenticated API call.
headers=headers,
A credential (read from the environment/filesystem, or parsed from the request URL) is applied as authorization on the same outbound request. This is intentional authentication to the service the credential belongs to, not unexpected data exfiltration.
Fix: Confirm the destination is the credential's own service; scope the credential and avoid logging it. No action if this is the intended authenticated API call.
headers=headers,
A credential (read from the environment/filesystem, or parsed from the request URL) is applied as authorization on the same outbound request. This is intentional authentication to the service the credential belongs to, not unexpected data exfiltration.
Fix: Confirm the destination is the credential's own service; scope the credential and avoid logging it. No action if this is the intended authenticated API call.
headers=headers,
A credential (read from the environment/filesystem, or parsed from the request URL) is applied as authorization on the same outbound request. This is intentional authentication to the service the credential belongs to, not unexpected data exfiltration.
Fix: Confirm the destination is the credential's own service; scope the credential and avoid logging it. No action if this is the intended authenticated API call.
headers=headers,
A credential (read from the environment/filesystem, or parsed from the request URL) is applied as authorization on the same outbound request. This is intentional authentication to the service the credential belongs to, not unexpected data exfiltration.
Fix: Confirm the destination is the credential's own service; scope the credential and avoid logging it. No action if this is the intended authenticated API call.
response = requests.post(f'{self.api_url}/layout-parsing', json=payload, headers=headers)
A credential (read from the environment/filesystem, or parsed from the request URL) is applied as authorization on the same outbound request. This is intentional authentication to the service the credential belongs to, not unexpected data exfiltration.
Fix: Confirm the destination is the credential's own service; scope the credential and avoid logging it. No action if this is the intended authenticated API call.
response = requests.post(self.api_url, headers=headers, json=payload)
A credential (read from the environment/filesystem, or parsed from the request URL) is applied as authorization on the same outbound request. This is intentional authentication to the service the credential belongs to, not unexpected data exfiltration.
Fix: Confirm the destination is the credential's own service; scope the credential and avoid logging it. No action if this is the intended authenticated API call.
headers=headers,
A credential (read from the environment/filesystem, or parsed from the request URL) is applied as authorization on the same outbound request. This is intentional authentication to the service the credential belongs to, not unexpected data exfiltration.
Fix: Confirm the destination is the credential's own service; scope the credential and avoid logging it. No action if this is the intended authenticated API call.
from opentelemetry import trace
A telemetry/analytics SDK is used; event data is sent to a third-party collector.
Fix: Ensure user consent and a lawful basis; strip PII from event payloads.
from opentelemetry import trace
A telemetry/analytics SDK is used; event data is sent to a third-party collector.
Fix: Ensure user consent and a lawful basis; strip PII from event payloads.
from opentelemetry import trace
A telemetry/analytics SDK is used; event data is sent to a third-party collector.
Fix: Ensure user consent and a lawful basis; strip PII from event payloads.
from opentelemetry import trace
A telemetry/analytics SDK is used; event data is sent to a third-party collector.
Fix: Ensure user consent and a lawful basis; strip PII from event payloads.
expand_more 1054 low-confidence finding(s)
low env_fs — Environment-variable access. 853 locations
low env_fs — Filesystem access. 43 locations
low egress — Outbound request to a variable or assembled URL on a network client. Review what data is sent to this destination. 143 locations
low egress — Hardcoded external endpoint. Review what data is sent to this destination. 15 locations
</> Dependencies
azure-ai-documentintelligence
python dependency print(f"----Barcodes detected from page #{page.page_number}----")
PII-bearing data is written to a log/print sink — it stays in-process and does not leave the application, but logged PII is still a privacy concern.
Fix: Avoid logging user identifiers; redact or omit PII from log/print statements.
print(f"Detected {len(page.barcodes)} barcodes:")
PII-bearing data is written to a log/print sink — it stays in-process and does not leave the application, but logged PII is still a privacy concern.
Fix: Avoid logging user identifiers; redact or omit PII from log/print statements.
print(f"- Barcode #{barcode_idx}: {barcode.value}")
PII-bearing data is written to a log/print sink — it stays in-process and does not leave the application, but logged PII is still a privacy concern.
Fix: Avoid logging user identifiers; redact or omit PII from log/print statements.
print(f" Kind: {barcode.kind}")
PII-bearing data is written to a log/print sink — it stays in-process and does not leave the application, but logged PII is still a privacy concern.
Fix: Avoid logging user identifiers; redact or omit PII from log/print statements.
print(f" Confidence: {barcode.confidence}")
PII-bearing data is written to a log/print sink — it stays in-process and does not leave the application, but logged PII is still a privacy concern.
Fix: Avoid logging user identifiers; redact or omit PII from log/print statements.
print(f" Bounding regions: {format_polygon(barcode.polygon)}")
PII-bearing data is written to a log/print sink — it stays in-process and does not leave the application, but logged PII is still a privacy concern.
Fix: Avoid logging user identifiers; redact or omit PII from log/print statements.
print(f" Text: '{get_styled_text(styles, result.content)}'")
PII-bearing data is written to a log/print sink — it stays in-process and does not leave the application, but logged PII is still a privacy concern.
Fix: Avoid logging user identifiers; redact or omit PII from log/print statements.
print(f" Text: '{get_styled_text(styles, result.content)}'")
PII-bearing data is written to a log/print sink — it stays in-process and does not leave the application, but logged PII is still a privacy concern.
Fix: Avoid logging user identifiers; redact or omit PII from log/print statements.
print(f" Text: '{get_styled_text(styles, result.content)}'")
PII-bearing data is written to a log/print sink — it stays in-process and does not leave the application, but logged PII is still a privacy concern.
Fix: Avoid logging user identifiers; redact or omit PII from log/print statements.
print(f" Text: '{get_styled_text(styles, result.content)}'")
PII-bearing data is written to a log/print sink — it stays in-process and does not leave the application, but logged PII is still a privacy concern.
Fix: Avoid logging user identifiers; redact or omit PII from log/print statements.
print(f" Text: '{get_styled_text(styles, result.content)}'")
PII-bearing data is written to a log/print sink — it stays in-process and does not leave the application, but logged PII is still a privacy concern.
Fix: Avoid logging user identifiers; redact or omit PII from log/print statements.
print(f"----Formulas detected from page #{page.page_number}----")
PII-bearing data is written to a log/print sink — it stays in-process and does not leave the application, but logged PII is still a privacy concern.
Fix: Avoid logging user identifiers; redact or omit PII from log/print statements.
print(f"Detected {len(inline_formulas)} inline formulas.")
PII-bearing data is written to a log/print sink — it stays in-process and does not leave the application, but logged PII is still a privacy concern.
Fix: Avoid logging user identifiers; redact or omit PII from log/print statements.
print(f"- Inline #{formula_idx}: {formula.value}")
PII-bearing data is written to a log/print sink — it stays in-process and does not leave the application, but logged PII is still a privacy concern.
Fix: Avoid logging user identifiers; redact or omit PII from log/print statements.
print(f" Confidence: {formula.confidence}")
PII-bearing data is written to a log/print sink — it stays in-process and does not leave the application, but logged PII is still a privacy concern.
Fix: Avoid logging user identifiers; redact or omit PII from log/print statements.
print(f" Bounding regions: {format_polygon(formula.polygon)}")
PII-bearing data is written to a log/print sink — it stays in-process and does not leave the application, but logged PII is still a privacy concern.
Fix: Avoid logging user identifiers; redact or omit PII from log/print statements.
print(f"\nDetected {len(display_formulas)} display formulas.")
PII-bearing data is written to a log/print sink — it stays in-process and does not leave the application, but logged PII is still a privacy concern.
Fix: Avoid logging user identifiers; redact or omit PII from log/print statements.
print(f"- Display #{formula_idx}: {formula.value}")
PII-bearing data is written to a log/print sink — it stays in-process and does not leave the application, but logged PII is still a privacy concern.
Fix: Avoid logging user identifiers; redact or omit PII from log/print statements.
print(f" Confidence: {formula.confidence}")
PII-bearing data is written to a log/print sink — it stays in-process and does not leave the application, but logged PII is still a privacy concern.
Fix: Avoid logging user identifiers; redact or omit PII from log/print statements.
print(f" Bounding regions: {format_polygon(formula.polygon)}")
PII-bearing data is written to a log/print sink — it stays in-process and does not leave the application, but logged PII is still a privacy concern.
Fix: Avoid logging user identifiers; redact or omit PII from log/print statements.
print(f"----Analyzing layout from page #{page.page_number}----")
PII-bearing data is written to a log/print sink — it stays in-process and does not leave the application, but logged PII is still a privacy concern.
Fix: Avoid logging user identifiers; redact or omit PII from log/print statements.
print(f"Page has width: {page.width} and height: {page.height}, measured with unit: {page.unit}")
PII-bearing data is written to a log/print sink — it stays in-process and does not leave the application, but logged PII is still a privacy concern.
Fix: Avoid logging user identifiers; redact or omit PII from log/print statements.
print(
f"...Line # {line_idx} has word count {len(words)} and text '{line.content}' "
f"within bounding polygon '{format_polygon(line.polygon)}'"
)
PII-bearing data is written to a log/print sink — it stays in-process and does not leave the application, but logged PII is still a privacy concern.
Fix: Avoid logging user identifiers; redact or omit PII from log/print statements.
print(f"......Word '{word.content}' has a confidence of {word.confidence}")
PII-bearing data is written to a log/print sink — it stays in-process and does not leave the application, but logged PII is still a privacy concern.
Fix: Avoid logging user identifiers; redact or omit PII from log/print statements.
print(
f"Selection mark is '{selection_mark.state}' within bounding polygon "
f"'{format_polygon(selection_mark.polygon)}' and has a confidence of {selection_mark.confidence}"
)
PII-bearing data is written to a log/print sink — it stays in-process and does not leave the application, but logged PII is still a privacy concern.
Fix: Avoid logging user identifiers; redact or omit PII from log/print statements.
print(f"Table # {table_idx} has {table.row_count} rows and " f"{table.column_count} columns")
PII-bearing data is written to a log/print sink — it stays in-process and does not leave the application, but logged PII is still a privacy concern.
Fix: Avoid logging user identifiers; redact or omit PII from log/print statements.
print(
f"Table # {table_idx} location on page: {region.page_number} is {format_polygon(region.polygon)}"
)
PII-bearing data is written to a log/print sink — it stays in-process and does not leave the application, but logged PII is still a privacy concern.
Fix: Avoid logging user identifiers; redact or omit PII from log/print statements.
print(f"...Cell[{cell.row_index}][{cell.column_index}] has text '{cell.content}'")
PII-bearing data is written to a log/print sink — it stays in-process and does not leave the application, but logged PII is still a privacy concern.
Fix: Avoid logging user identifiers; redact or omit PII from log/print statements.
print(
f"...content on page {region.page_number} is within bounding polygon '{format_polygon(region.polygon)}'"
)
PII-bearing data is written to a log/print sink — it stays in-process and does not leave the application, but logged PII is still a privacy concern.
Fix: Avoid logging user identifiers; redact or omit PII from log/print statements.
print(f"Detected {len(result.languages)} languages:")
PII-bearing data is written to a log/print sink — it stays in-process and does not leave the application, but logged PII is still a privacy concern.
Fix: Avoid logging user identifiers; redact or omit PII from log/print statements.
print(f"- Language #{lang_idx}: locale '{lang.locale}'")
PII-bearing data is written to a log/print sink — it stays in-process and does not leave the application, but logged PII is still a privacy concern.
Fix: Avoid logging user identifiers; redact or omit PII from log/print statements.
print(f" Confidence: {lang.confidence}")
PII-bearing data is written to a log/print sink — it stays in-process and does not leave the application, but logged PII is still a privacy concern.
Fix: Avoid logging user identifiers; redact or omit PII from log/print statements.
print(f"Address: {doc.fields['Address'].value_string}")
PII-bearing data is written to a log/print sink — it stays in-process and does not leave the application, but logged PII is still a privacy concern.
Fix: Avoid logging user identifiers; redact or omit PII from log/print statements.
print(f"Invoice number: {doc.fields['InvoiceNumber'].value_string}")
PII-bearing data is written to a log/print sink — it stays in-process and does not leave the application, but logged PII is still a privacy concern.
Fix: Avoid logging user identifiers; redact or omit PII from log/print statements.
print(f"Succeeded count: {final_result.succeeded_count}")
PII-bearing data is written to a log/print sink — it stays in-process and does not leave the application, but logged PII is still a privacy concern.
Fix: Avoid logging user identifiers; redact or omit PII from log/print statements.
print(f"Failed count: {final_result.failed_count}")
PII-bearing data is written to a log/print sink — it stays in-process and does not leave the application, but logged PII is still a privacy concern.
Fix: Avoid logging user identifiers; redact or omit PII from log/print statements.
print(f"Skipped count: {final_result.skipped_count}")
PII-bearing data is written to a log/print sink — it stays in-process and does not leave the application, but logged PII is still a privacy concern.
Fix: Avoid logging user identifiers; redact or omit PII from log/print statements.
print(f"--------Analyzing document #{idx + 1}--------")
PII-bearing data is written to a log/print sink — it stays in-process and does not leave the application, but logged PII is still a privacy concern.
Fix: Avoid logging user identifiers; redact or omit PII from log/print statements.
print(f"Document has type {document.doc_type}")
PII-bearing data is written to a log/print sink — it stays in-process and does not leave the application, but logged PII is still a privacy concern.
Fix: Avoid logging user identifiers; redact or omit PII from log/print statements.
print(f"Document has document type confidence {document.confidence}")
PII-bearing data is written to a log/print sink — it stays in-process and does not leave the application, but logged PII is still a privacy concern.
Fix: Avoid logging user identifiers; redact or omit PII from log/print statements.
print(f"Document was analyzed with model with ID {result.model_id}")
PII-bearing data is written to a log/print sink — it stays in-process and does not leave the application, but logged PII is still a privacy concern.
Fix: Avoid logging user identifiers; redact or omit PII from log/print statements.
print(
f"......found field of type '{field.type}' with value '{field_value}' and with confidence {field.confidence}"
)
PII-bearing data is written to a log/print sink — it stays in-process and does not leave the application, but logged PII is still a privacy concern.
Fix: Avoid logging user identifiers; redact or omit PII from log/print statements.
print(f"Here's the full content in format {result.content_format}:\n")
PII-bearing data is written to a log/print sink — it stays in-process and does not leave the application, but logged PII is still a privacy concern.
Fix: Avoid logging user identifiers; redact or omit PII from log/print statements.
print(result.content)
PII-bearing data is written to a log/print sink — it stays in-process and does not leave the application, but logged PII is still a privacy concern.
Fix: Avoid logging user identifiers; redact or omit PII from log/print statements.
print(
f"Key '{kv_pair.key.content}' found within "
f"'{format_bounding_region(kv_pair.key.bounding_regions)}' bounding regions"
)
PII-bearing data is written to a log/print sink — it stays in-process and does not leave the application, but logged PII is still a privacy concern.
Fix: Avoid logging user identifiers; redact or omit PII from log/print statements.
print(
f"Value '{kv_pair.value.content}' found within "
f"'{format_bounding_region(kv_pair.value.bounding_regions)}' bounding regions\n"
)
PII-bearing data is written to a log/print sink — it stays in-process and does not leave the application, but logged PII is still a privacy concern.
Fix: Avoid logging user identifiers; redact or omit PII from log/print statements.
print(f"----Analyzing document from page #{page.page_number}----")
PII-bearing data is written to a log/print sink — it stays in-process and does not leave the application, but logged PII is still a privacy concern.
Fix: Avoid logging user identifiers; redact or omit PII from log/print statements.
print(f"Page has width: {page.width} and height: {page.height}, measured with unit: {page.unit}")
PII-bearing data is written to a log/print sink — it stays in-process and does not leave the application, but logged PII is still a privacy concern.
Fix: Avoid logging user identifiers; redact or omit PII from log/print statements.
print(
f"...Line #{line_idx} has {len(words)} words and text '{line.content}' within "
f"bounding polygon '{format_polygon(line.polygon)}'"
)
PII-bearing data is written to a log/print sink — it stays in-process and does not leave the application, but logged PII is still a privacy concern.
Fix: Avoid logging user identifiers; redact or omit PII from log/print statements.
print(f"......Word '{word.content}' has a confidence of {word.confidence}")
PII-bearing data is written to a log/print sink — it stays in-process and does not leave the application, but logged PII is still a privacy concern.
Fix: Avoid logging user identifiers; redact or omit PII from log/print statements.
print(
f"Selection mark is '{selection_mark.state}' within bounding polygon "
f"'{format_polygon(selection_mark.polygon)}' and has a confidence of "
f"{selection_mark.confidence}"
)
PII-bearing data is written to a log/print sink — it stays in-process and does not leave the application, but logged PII is still a privacy concern.
Fix: Avoid logging user identifiers; redact or omit PII from log/print statements.
print(f"Table # {table_idx} has {table.row_count} rows and {table.column_count} columns")
PII-bearing data is written to a log/print sink — it stays in-process and does not leave the application, but logged PII is still a privacy concern.
Fix: Avoid logging user identifiers; redact or omit PII from log/print statements.
print(
f"Table # {table_idx} location on page: {region.page_number} is {format_polygon(region.polygon)}"
)
PII-bearing data is written to a log/print sink — it stays in-process and does not leave the application, but logged PII is still a privacy concern.
Fix: Avoid logging user identifiers; redact or omit PII from log/print statements.
print(f"...Cell[{cell.row_index}][{cell.column_index}] has text '{cell.content}'")
PII-bearing data is written to a log/print sink — it stays in-process and does not leave the application, but logged PII is still a privacy concern.
Fix: Avoid logging user identifiers; redact or omit PII from log/print statements.
print(
f"...content on page {region.page_number} is within bounding polygon '{format_polygon(region.polygon)}'\n"
)
PII-bearing data is written to a log/print sink — it stays in-process and does not leave the application, but logged PII is still a privacy concern.
Fix: Avoid logging user identifiers; redact or omit PII from log/print statements.
print(f"--------Analyzing ID document #{idx + 1}--------")
PII-bearing data is written to a log/print sink — it stays in-process and does not leave the application, but logged PII is still a privacy concern.
Fix: Avoid logging user identifiers; redact or omit PII from log/print statements.
print(f"First Name: {first_name.get('valueString')} has confidence: {first_name.confidence}")
PII-bearing data is written to a log/print sink — it stays in-process and does not leave the application, but logged PII is still a privacy concern.
Fix: Avoid logging user identifiers; redact or omit PII from log/print statements.
print(f"Last Name: {last_name.get('valueString')} has confidence: {last_name.confidence}")
PII-bearing data is written to a log/print sink — it stays in-process and does not leave the application, but logged PII is still a privacy concern.
Fix: Avoid logging user identifiers; redact or omit PII from log/print statements.
print(
f"Document Number: {document_number.get('valueString')} has confidence: {document_number.confidence}"
)
PII-bearing data is written to a log/print sink — it stays in-process and does not leave the application, but logged PII is still a privacy concern.
Fix: Avoid logging user identifiers; redact or omit PII from log/print statements.
print(f"Date of Birth: {dob.get('valueDate')} has confidence: {dob.confidence}")
PII-bearing data is written to a log/print sink — it stays in-process and does not leave the application, but logged PII is still a privacy concern.
Fix: Avoid logging user identifiers; redact or omit PII from log/print statements.
print(f"Date of Expiration: {doe.get('valueDate')} has confidence: {doe.confidence}")
PII-bearing data is written to a log/print sink — it stays in-process and does not leave the application, but logged PII is still a privacy concern.
Fix: Avoid logging user identifiers; redact or omit PII from log/print statements.
print(f"Sex: {sex.get('valueString')} has confidence: {sex.confidence}")
PII-bearing data is written to a log/print sink — it stays in-process and does not leave the application, but logged PII is still a privacy concern.
Fix: Avoid logging user identifiers; redact or omit PII from log/print statements.
print(f"Address: {address.get('valueString')} has confidence: {address.confidence}")
PII-bearing data is written to a log/print sink — it stays in-process and does not leave the application, but logged PII is still a privacy concern.
Fix: Avoid logging user identifiers; redact or omit PII from log/print statements.
print(
f"Country/Region: {country_region.get('valueCountryRegion')} has confidence: {country_region.confidence}"
)
PII-bearing data is written to a log/print sink — it stays in-process and does not leave the application, but logged PII is still a privacy concern.
Fix: Avoid logging user identifiers; redact or omit PII from log/print statements.
print(f"Region: {region.get('valueString')} has confidence: {region.confidence}")
PII-bearing data is written to a log/print sink — it stays in-process and does not leave the application, but logged PII is still a privacy concern.
Fix: Avoid logging user identifiers; redact or omit PII from log/print statements.
print(f"--------Analyzing invoice #{idx + 1}--------")
PII-bearing data is written to a log/print sink — it stays in-process and does not leave the application, but logged PII is still a privacy concern.
Fix: Avoid logging user identifiers; redact or omit PII from log/print statements.
print(f"Vendor Name: {vendor_name.get('content')} has confidence: {vendor_name.get('confidence')}")
PII-bearing data is written to a log/print sink — it stays in-process and does not leave the application, but logged PII is still a privacy concern.
Fix: Avoid logging user identifiers; redact or omit PII from log/print statements.
print(
f"Vendor Address: {vendor_address.get('content')} has confidence: {vendor_address.get('confidence')}"
)
PII-bearing data is written to a log/print sink — it stays in-process and does not leave the application, but logged PII is still a privacy concern.
Fix: Avoid logging user identifiers; redact or omit PII from log/print statements.
print(
f"Vendor Address Recipient: {vendor_address_recipient.get('content')} has confidence: {vendor_address_recipient.get('confidence')}"
)
PII-bearing data is written to a log/print sink — it stays in-process and does not leave the application, but logged PII is still a privacy concern.
Fix: Avoid logging user identifiers; redact or omit PII from log/print statements.
print(
f"Customer Name: {customer_name.get('content')} has confidence: {customer_name.get('confidence')}"
)
PII-bearing data is written to a log/print sink — it stays in-process and does not leave the application, but logged PII is still a privacy concern.
Fix: Avoid logging user identifiers; redact or omit PII from log/print statements.
print(f"Customer Id: {customer_id.get('content')} has confidence: {customer_id.get('confidence')}")
PII-bearing data is written to a log/print sink — it stays in-process and does not leave the application, but logged PII is still a privacy concern.
Fix: Avoid logging user identifiers; redact or omit PII from log/print statements.
print(
f"Customer Address: {customer_address.get('content')} has confidence: {customer_address.get('confidence')}"
)
PII-bearing data is written to a log/print sink — it stays in-process and does not leave the application, but logged PII is still a privacy concern.
Fix: Avoid logging user identifiers; redact or omit PII from log/print statements.
print(
f"Customer Address Recipient: {customer_address_recipient.get('content')} has confidence: {customer_address_recipient.get('confidence')}"
)
PII-bearing data is written to a log/print sink — it stays in-process and does not leave the application, but logged PII is still a privacy concern.
Fix: Avoid logging user identifiers; redact or omit PII from log/print statements.
print(f"Invoice Id: {invoice_id.get('content')} has confidence: {invoice_id.get('confidence')}")
PII-bearing data is written to a log/print sink — it stays in-process and does not leave the application, but logged PII is still a privacy concern.
Fix: Avoid logging user identifiers; redact or omit PII from log/print statements.
print(
f"Invoice Date: {invoice_date.get('content')} has confidence: {invoice_date.get('confidence')}"
)
PII-bearing data is written to a log/print sink — it stays in-process and does not leave the application, but logged PII is still a privacy concern.
Fix: Avoid logging user identifiers; redact or omit PII from log/print statements.
print(
f"Invoice Total: {invoice_total.get('content')} has confidence: {invoice_total.get('confidence')}"
)
PII-bearing data is written to a log/print sink — it stays in-process and does not leave the application, but logged PII is still a privacy concern.
Fix: Avoid logging user identifiers; redact or omit PII from log/print statements.
print(f"Due Date: {due_date.get('content')} has confidence: {due_date.get('confidence')}")
PII-bearing data is written to a log/print sink — it stays in-process and does not leave the application, but logged PII is still a privacy concern.
Fix: Avoid logging user identifiers; redact or omit PII from log/print statements.
print(
f"Purchase Order: {purchase_order.get('content')} has confidence: {purchase_order.get('confidence')}"
)
PII-bearing data is written to a log/print sink — it stays in-process and does not leave the application, but logged PII is still a privacy concern.
Fix: Avoid logging user identifiers; redact or omit PII from log/print statements.
print(
f"Billing Address: {billing_address.get('content')} has confidence: {billing_address.get('confidence')}"
)
PII-bearing data is written to a log/print sink — it stays in-process and does not leave the application, but logged PII is still a privacy concern.
Fix: Avoid logging user identifiers; redact or omit PII from log/print statements.
print(
f"Billing Address Recipient: {billing_address_recipient.get('content')} has confidence: {billing_address_recipient.get('confidence')}"
)
PII-bearing data is written to a log/print sink — it stays in-process and does not leave the application, but logged PII is still a privacy concern.
Fix: Avoid logging user identifiers; redact or omit PII from log/print statements.
print(
f"Shipping Address: {shipping_address.get('content')} has confidence: {shipping_address.get('confidence')}"
)
PII-bearing data is written to a log/print sink — it stays in-process and does not leave the application, but logged PII is still a privacy concern.
Fix: Avoid logging user identifiers; redact or omit PII from log/print statements.
print(
f"Shipping Address Recipient: {shipping_address_recipient.get('content')} has confidence: {shipping_address_recipient.get('confidence')}"
)
PII-bearing data is written to a log/print sink — it stays in-process and does not leave the application, but logged PII is still a privacy concern.
Fix: Avoid logging user identifiers; redact or omit PII from log/print statements.
print(f"...Item #{idx + 1}")
PII-bearing data is written to a log/print sink — it stays in-process and does not leave the application, but logged PII is still a privacy concern.
Fix: Avoid logging user identifiers; redact or omit PII from log/print statements.
print(
f"......Description: {item_description.get('content')} has confidence: {item_description.get('confidence')}"
)
PII-bearing data is written to a log/print sink — it stays in-process and does not leave the application, but logged PII is still a privacy concern.
Fix: Avoid logging user identifiers; redact or omit PII from log/print statements.
print(
f"......Quantity: {item_quantity.get('content')} has confidence: {item_quantity.get('confidence')}"
)
PII-bearing data is written to a log/print sink — it stays in-process and does not leave the application, but logged PII is still a privacy concern.
Fix: Avoid logging user identifiers; redact or omit PII from log/print statements.
print(f"......Unit: {unit.get('content')} has confidence: {unit.get('confidence')}")
PII-bearing data is written to a log/print sink — it stays in-process and does not leave the application, but logged PII is still a privacy concern.
Fix: Avoid logging user identifiers; redact or omit PII from log/print statements.
print(
f"......Unit Price: {unit_price.get('content')}{unit_price_code} has confidence: {unit_price.get('confidence')}"
)
PII-bearing data is written to a log/print sink — it stays in-process and does not leave the application, but logged PII is still a privacy concern.
Fix: Avoid logging user identifiers; redact or omit PII from log/print statements.
print(
f"......Product Code: {product_code.get('content')} has confidence: {product_code.get('confidence')}"
)
PII-bearing data is written to a log/print sink — it stays in-process and does not leave the application, but logged PII is still a privacy concern.
Fix: Avoid logging user identifiers; redact or omit PII from log/print statements.
print(
f"......Date: {item_date.get('content')} has confidence: {item_date.get('confidence')}"
)
PII-bearing data is written to a log/print sink — it stays in-process and does not leave the application, but logged PII is still a privacy concern.
Fix: Avoid logging user identifiers; redact or omit PII from log/print statements.
print(f"......Tax: {tax.get('content')} has confidence: {tax.get('confidence')}")
PII-bearing data is written to a log/print sink — it stays in-process and does not leave the application, but logged PII is still a privacy concern.
Fix: Avoid logging user identifiers; redact or omit PII from log/print statements.
print(f"......Amount: {amount.get('content')} has confidence: {amount.get('confidence')}")
PII-bearing data is written to a log/print sink — it stays in-process and does not leave the application, but logged PII is still a privacy concern.
Fix: Avoid logging user identifiers; redact or omit PII from log/print statements.
print(f"Subtotal: {subtotal.get('content')} has confidence: {subtotal.get('confidence')}")
PII-bearing data is written to a log/print sink — it stays in-process and does not leave the application, but logged PII is still a privacy concern.
Fix: Avoid logging user identifiers; redact or omit PII from log/print statements.
print(f"Total Tax: {total_tax.get('content')} has confidence: {total_tax.get('confidence')}")
PII-bearing data is written to a log/print sink — it stays in-process and does not leave the application, but logged PII is still a privacy concern.
Fix: Avoid logging user identifiers; redact or omit PII from log/print statements.
print(
f"Previous Unpaid Balance: {previous_unpaid_balance.get('content')} has confidence: {previous_unpaid_balance.get('confidence')}"
)
PII-bearing data is written to a log/print sink — it stays in-process and does not leave the application, but logged PII is still a privacy concern.
Fix: Avoid logging user identifiers; redact or omit PII from log/print statements.
print(f"Amount Due: {amount_due.get('content')} has confidence: {amount_due.get('confidence')}")
PII-bearing data is written to a log/print sink — it stays in-process and does not leave the application, but logged PII is still a privacy concern.
Fix: Avoid logging user identifiers; redact or omit PII from log/print statements.
print(
f"Service Start Date: {service_start_date.get('content')} has confidence: {service_start_date.get('confidence')}"
)
PII-bearing data is written to a log/print sink — it stays in-process and does not leave the application, but logged PII is still a privacy concern.
Fix: Avoid logging user identifiers; redact or omit PII from log/print statements.
print(
f"Service End Date: {service_end_date.get('content')} has confidence: {service_end_date.get('confidence')}"
)
PII-bearing data is written to a log/print sink — it stays in-process and does not leave the application, but logged PII is still a privacy concern.
Fix: Avoid logging user identifiers; redact or omit PII from log/print statements.
print(
f"Service Address: {service_address.get('content')} has confidence: {service_address.get('confidence')}"
)
PII-bearing data is written to a log/print sink — it stays in-process and does not leave the application, but logged PII is still a privacy concern.
Fix: Avoid logging user identifiers; redact or omit PII from log/print statements.
print(
f"Service Address Recipient: {service_address_recipient.get('content')} has confidence: {service_address_recipient.get('confidence')}"
)
PII-bearing data is written to a log/print sink — it stays in-process and does not leave the application, but logged PII is still a privacy concern.
Fix: Avoid logging user identifiers; redact or omit PII from log/print statements.
print(
f"Remittance Address: {remittance_address.get('content')} has confidence: {remittance_address.get('confidence')}"
)
PII-bearing data is written to a log/print sink — it stays in-process and does not leave the application, but logged PII is still a privacy concern.
Fix: Avoid logging user identifiers; redact or omit PII from log/print statements.
print(
f"Remittance Address Recipient: {remittance_address_recipient.get('content')} has confidence: {remittance_address_recipient.get('confidence')}"
)
PII-bearing data is written to a log/print sink — it stays in-process and does not leave the application, but logged PII is still a privacy concern.
Fix: Avoid logging user identifiers; redact or omit PII from log/print statements.
print(f"--------Analyzing invoice #{idx + 1}--------")
PII-bearing data is written to a log/print sink — it stays in-process and does not leave the application, but logged PII is still a privacy concern.
Fix: Avoid logging user identifiers; redact or omit PII from log/print statements.
print(f"Vendor Name: {vendor_name.get('content')} has confidence: {vendor_name.get('confidence')}")
PII-bearing data is written to a log/print sink — it stays in-process and does not leave the application, but logged PII is still a privacy concern.
Fix: Avoid logging user identifiers; redact or omit PII from log/print statements.
print(
f"Vendor Address: {vendor_address.get('content')} has confidence: {vendor_address.get('confidence')}"
)
PII-bearing data is written to a log/print sink — it stays in-process and does not leave the application, but logged PII is still a privacy concern.
Fix: Avoid logging user identifiers; redact or omit PII from log/print statements.
print(
f"Vendor Address Recipient: {vendor_address_recipient.get('content')} has confidence: {vendor_address_recipient.get('confidence')}"
)
PII-bearing data is written to a log/print sink — it stays in-process and does not leave the application, but logged PII is still a privacy concern.
Fix: Avoid logging user identifiers; redact or omit PII from log/print statements.
print(
f"Customer Name: {customer_name.get('content')} has confidence: {customer_name.get('confidence')}"
)
PII-bearing data is written to a log/print sink — it stays in-process and does not leave the application, but logged PII is still a privacy concern.
Fix: Avoid logging user identifiers; redact or omit PII from log/print statements.
print(f"Customer Id: {customer_id.get('content')} has confidence: {customer_id.get('confidence')}")
PII-bearing data is written to a log/print sink — it stays in-process and does not leave the application, but logged PII is still a privacy concern.
Fix: Avoid logging user identifiers; redact or omit PII from log/print statements.
print(
f"Customer Address: {customer_address.get('content')} has confidence: {customer_address.get('confidence')}"
)
PII-bearing data is written to a log/print sink — it stays in-process and does not leave the application, but logged PII is still a privacy concern.
Fix: Avoid logging user identifiers; redact or omit PII from log/print statements.
print(
f"Customer Address Recipient: {customer_address_recipient.get('content')} has confidence: {customer_address_recipient.get('confidence')}"
)
PII-bearing data is written to a log/print sink — it stays in-process and does not leave the application, but logged PII is still a privacy concern.
Fix: Avoid logging user identifiers; redact or omit PII from log/print statements.
print(f"Invoice Id: {invoice_id.get('content')} has confidence: {invoice_id.get('confidence')}")
PII-bearing data is written to a log/print sink — it stays in-process and does not leave the application, but logged PII is still a privacy concern.
Fix: Avoid logging user identifiers; redact or omit PII from log/print statements.
print(
f"Invoice Date: {invoice_date.get('content')} has confidence: {invoice_date.get('confidence')}"
)
PII-bearing data is written to a log/print sink — it stays in-process and does not leave the application, but logged PII is still a privacy concern.
Fix: Avoid logging user identifiers; redact or omit PII from log/print statements.
print(
f"Invoice Total: {invoice_total.get('content')} has confidence: {invoice_total.get('confidence')}"
)
PII-bearing data is written to a log/print sink — it stays in-process and does not leave the application, but logged PII is still a privacy concern.
Fix: Avoid logging user identifiers; redact or omit PII from log/print statements.
print(f"Due Date: {due_date.get('content')} has confidence: {due_date.get('confidence')}")
PII-bearing data is written to a log/print sink — it stays in-process and does not leave the application, but logged PII is still a privacy concern.
Fix: Avoid logging user identifiers; redact or omit PII from log/print statements.
print(
f"Purchase Order: {purchase_order.get('content')} has confidence: {purchase_order.get('confidence')}"
)
PII-bearing data is written to a log/print sink — it stays in-process and does not leave the application, but logged PII is still a privacy concern.
Fix: Avoid logging user identifiers; redact or omit PII from log/print statements.
print(
f"Billing Address: {billing_address.get('content')} has confidence: {billing_address.get('confidence')}"
)
PII-bearing data is written to a log/print sink — it stays in-process and does not leave the application, but logged PII is still a privacy concern.
Fix: Avoid logging user identifiers; redact or omit PII from log/print statements.
print(
f"Billing Address Recipient: {billing_address_recipient.get('content')} has confidence: {billing_address_recipient.get('confidence')}"
)
PII-bearing data is written to a log/print sink — it stays in-process and does not leave the application, but logged PII is still a privacy concern.
Fix: Avoid logging user identifiers; redact or omit PII from log/print statements.
print(
f"Shipping Address: {shipping_address.get('content')} has confidence: {shipping_address.get('confidence')}"
)
PII-bearing data is written to a log/print sink — it stays in-process and does not leave the application, but logged PII is still a privacy concern.
Fix: Avoid logging user identifiers; redact or omit PII from log/print statements.
print(
f"Shipping Address Recipient: {shipping_address_recipient.get('content')} has confidence: {shipping_address_recipient.get('confidence')}"
)
PII-bearing data is written to a log/print sink — it stays in-process and does not leave the application, but logged PII is still a privacy concern.
Fix: Avoid logging user identifiers; redact or omit PII from log/print statements.
print(f"...Item #{idx + 1}")
PII-bearing data is written to a log/print sink — it stays in-process and does not leave the application, but logged PII is still a privacy concern.
Fix: Avoid logging user identifiers; redact or omit PII from log/print statements.
print(
f"......Description: {item_description.get('content')} has confidence: {item_description.get('confidence')}"
)
PII-bearing data is written to a log/print sink — it stays in-process and does not leave the application, but logged PII is still a privacy concern.
Fix: Avoid logging user identifiers; redact or omit PII from log/print statements.
print(
f"......Quantity: {item_quantity.get('content')} has confidence: {item_quantity.get('confidence')}"
)
PII-bearing data is written to a log/print sink — it stays in-process and does not leave the application, but logged PII is still a privacy concern.
Fix: Avoid logging user identifiers; redact or omit PII from log/print statements.
print(f"......Unit: {unit.get('content')} has confidence: {unit.get('confidence')}")
PII-bearing data is written to a log/print sink — it stays in-process and does not leave the application, but logged PII is still a privacy concern.
Fix: Avoid logging user identifiers; redact or omit PII from log/print statements.
print(
f"......Unit Price: {unit_price.get('content')}{unit_price_code} has confidence: {unit_price.get('confidence')}"
)
PII-bearing data is written to a log/print sink — it stays in-process and does not leave the application, but logged PII is still a privacy concern.
Fix: Avoid logging user identifiers; redact or omit PII from log/print statements.
print(
f"......Product Code: {product_code.get('content')} has confidence: {product_code.get('confidence')}"
)
PII-bearing data is written to a log/print sink — it stays in-process and does not leave the application, but logged PII is still a privacy concern.
Fix: Avoid logging user identifiers; redact or omit PII from log/print statements.
print(
f"......Date: {item_date.get('content')} has confidence: {item_date.get('confidence')}"
)
PII-bearing data is written to a log/print sink — it stays in-process and does not leave the application, but logged PII is still a privacy concern.
Fix: Avoid logging user identifiers; redact or omit PII from log/print statements.
print(f"......Tax: {tax.get('content')} has confidence: {tax.get('confidence')}")
PII-bearing data is written to a log/print sink — it stays in-process and does not leave the application, but logged PII is still a privacy concern.
Fix: Avoid logging user identifiers; redact or omit PII from log/print statements.
print(f"......Amount: {amount.get('content')} has confidence: {amount.get('confidence')}")
PII-bearing data is written to a log/print sink — it stays in-process and does not leave the application, but logged PII is still a privacy concern.
Fix: Avoid logging user identifiers; redact or omit PII from log/print statements.
print(f"Subtotal: {subtotal.get('content')} has confidence: {subtotal.get('confidence')}")
PII-bearing data is written to a log/print sink — it stays in-process and does not leave the application, but logged PII is still a privacy concern.
Fix: Avoid logging user identifiers; redact or omit PII from log/print statements.
print(f"Total Tax: {total_tax.get('content')} has confidence: {total_tax.get('confidence')}")
PII-bearing data is written to a log/print sink — it stays in-process and does not leave the application, but logged PII is still a privacy concern.
Fix: Avoid logging user identifiers; redact or omit PII from log/print statements.
print(
f"Previous Unpaid Balance: {previous_unpaid_balance.get('content')} has confidence: {previous_unpaid_balance.get('confidence')}"
)
PII-bearing data is written to a log/print sink — it stays in-process and does not leave the application, but logged PII is still a privacy concern.
Fix: Avoid logging user identifiers; redact or omit PII from log/print statements.
print(f"Amount Due: {amount_due.get('content')} has confidence: {amount_due.get('confidence')}")
PII-bearing data is written to a log/print sink — it stays in-process and does not leave the application, but logged PII is still a privacy concern.
Fix: Avoid logging user identifiers; redact or omit PII from log/print statements.
print(
f"Service Start Date: {service_start_date.get('content')} has confidence: {service_start_date.get('confidence')}"
)
PII-bearing data is written to a log/print sink — it stays in-process and does not leave the application, but logged PII is still a privacy concern.
Fix: Avoid logging user identifiers; redact or omit PII from log/print statements.
print(
f"Service End Date: {service_end_date.get('content')} has confidence: {service_end_date.get('confidence')}"
)
PII-bearing data is written to a log/print sink — it stays in-process and does not leave the application, but logged PII is still a privacy concern.
Fix: Avoid logging user identifiers; redact or omit PII from log/print statements.
print(
f"Service Address: {service_address.get('content')} has confidence: {service_address.get('confidence')}"
)
PII-bearing data is written to a log/print sink — it stays in-process and does not leave the application, but logged PII is still a privacy concern.
Fix: Avoid logging user identifiers; redact or omit PII from log/print statements.
print(
f"Service Address Recipient: {service_address_recipient.get('content')} has confidence: {service_address_recipient.get('confidence')}"
)
PII-bearing data is written to a log/print sink — it stays in-process and does not leave the application, but logged PII is still a privacy concern.
Fix: Avoid logging user identifiers; redact or omit PII from log/print statements.
print(
f"Remittance Address: {remittance_address.get('content')} has confidence: {remittance_address.get('confidence')}"
)
PII-bearing data is written to a log/print sink — it stays in-process and does not leave the application, but logged PII is still a privacy concern.
Fix: Avoid logging user identifiers; redact or omit PII from log/print statements.
print(
f"Remittance Address Recipient: {remittance_address_recipient.get('content')} has confidence: {remittance_address_recipient.get('confidence')}"
)
PII-bearing data is written to a log/print sink — it stays in-process and does not leave the application, but logged PII is still a privacy concern.
Fix: Avoid logging user identifiers; redact or omit PII from log/print statements.
print(f"----Analyzing layout from page #{page.page_number}----")
PII-bearing data is written to a log/print sink — it stays in-process and does not leave the application, but logged PII is still a privacy concern.
Fix: Avoid logging user identifiers; redact or omit PII from log/print statements.
print(f"Page has width: {page.width} and height: {page.height}, measured with unit: {page.unit}")
PII-bearing data is written to a log/print sink — it stays in-process and does not leave the application, but logged PII is still a privacy concern.
Fix: Avoid logging user identifiers; redact or omit PII from log/print statements.
print(
f"...Line # {line_idx} has word count {len(words)} and text '{line.content}' "
f"within bounding polygon '{format_polygon(line.polygon)}'"
)
PII-bearing data is written to a log/print sink — it stays in-process and does not leave the application, but logged PII is still a privacy concern.
Fix: Avoid logging user identifiers; redact or omit PII from log/print statements.
print(f"......Word '{word.content}' has a confidence of {word.confidence}")
PII-bearing data is written to a log/print sink — it stays in-process and does not leave the application, but logged PII is still a privacy concern.
Fix: Avoid logging user identifiers; redact or omit PII from log/print statements.
print(
f"Selection mark is '{selection_mark.state}' within bounding polygon "
f"'{format_polygon(selection_mark.polygon)}' and has a confidence of {selection_mark.confidence}"
)
PII-bearing data is written to a log/print sink — it stays in-process and does not leave the application, but logged PII is still a privacy concern.
Fix: Avoid logging user identifiers; redact or omit PII from log/print statements.
print(f"----Detected #{len(result.paragraphs)} paragraphs in the document----")
PII-bearing data is written to a log/print sink — it stays in-process and does not leave the application, but logged PII is still a privacy concern.
Fix: Avoid logging user identifiers; redact or omit PII from log/print statements.
print(
f"Found paragraph with role: '{paragraph.role}' within {format_bounding_region(paragraph.bounding_regions)} bounding region"
)
PII-bearing data is written to a log/print sink — it stays in-process and does not leave the application, but logged PII is still a privacy concern.
Fix: Avoid logging user identifiers; redact or omit PII from log/print statements.
print(f"...with content: '{paragraph.content}'")
PII-bearing data is written to a log/print sink — it stays in-process and does not leave the application, but logged PII is still a privacy concern.
Fix: Avoid logging user identifiers; redact or omit PII from log/print statements.
print(f"...with offset: {paragraph.spans[0].offset} and length: {paragraph.spans[0].length}")
PII-bearing data is written to a log/print sink — it stays in-process and does not leave the application, but logged PII is still a privacy concern.
Fix: Avoid logging user identifiers; redact or omit PII from log/print statements.
print(f"Table # {table_idx} has {table.row_count} rows and " f"{table.column_count} columns")
PII-bearing data is written to a log/print sink — it stays in-process and does not leave the application, but logged PII is still a privacy concern.
Fix: Avoid logging user identifiers; redact or omit PII from log/print statements.
print(
f"Table # {table_idx} location on page: {region.page_number} is {format_polygon(region.polygon)}"
)
PII-bearing data is written to a log/print sink — it stays in-process and does not leave the application, but logged PII is still a privacy concern.
Fix: Avoid logging user identifiers; redact or omit PII from log/print statements.
print(f"...Cell[{cell.row_index}][{cell.column_index}] has text '{cell.content}'")
PII-bearing data is written to a log/print sink — it stays in-process and does not leave the application, but logged PII is still a privacy concern.
Fix: Avoid logging user identifiers; redact or omit PII from log/print statements.
print(
f"...content on page {region.page_number} is within bounding polygon '{format_polygon(region.polygon)}'"
)
PII-bearing data is written to a log/print sink — it stays in-process and does not leave the application, but logged PII is still a privacy concern.
Fix: Avoid logging user identifiers; redact or omit PII from log/print statements.
print(f"Language code: '{language.locale}' with confidence {language.confidence}")
PII-bearing data is written to a log/print sink — it stays in-process and does not leave the application, but logged PII is still a privacy concern.
Fix: Avoid logging user identifiers; redact or omit PII from log/print statements.
print(f"The document contains '{style.font_style}' font style, applied to the following text: ")
PII-bearing data is written to a log/print sink — it stays in-process and does not leave the application, but logged PII is still a privacy concern.
Fix: Avoid logging user identifiers; redact or omit PII from log/print statements.
print(f"----Analyzing document from page #{page.page_number}----")
PII-bearing data is written to a log/print sink — it stays in-process and does not leave the application, but logged PII is still a privacy concern.
Fix: Avoid logging user identifiers; redact or omit PII from log/print statements.
print(f"Page has width: {page.width} and height: {page.height}, measured with unit: {page.unit}")
PII-bearing data is written to a log/print sink — it stays in-process and does not leave the application, but logged PII is still a privacy concern.
Fix: Avoid logging user identifiers; redact or omit PII from log/print statements.
print(
f"...Line # {line_idx} has {len(words)} words and text '{line.content}' within bounding polygon '{format_polygon(line.polygon)}'"
)
PII-bearing data is written to a log/print sink — it stays in-process and does not leave the application, but logged PII is still a privacy concern.
Fix: Avoid logging user identifiers; redact or omit PII from log/print statements.
print(f"......Word '{word.content}' has a confidence of {word.confidence}")
PII-bearing data is written to a log/print sink — it stays in-process and does not leave the application, but logged PII is still a privacy concern.
Fix: Avoid logging user identifiers; redact or omit PII from log/print statements.
print(
f"...Selection mark is '{selection_mark.state}' within bounding polygon "
f"'{format_polygon(selection_mark.polygon)}' and has a confidence of {selection_mark.confidence}"
)
PII-bearing data is written to a log/print sink — it stays in-process and does not leave the application, but logged PII is still a privacy concern.
Fix: Avoid logging user identifiers; redact or omit PII from log/print statements.
print(f"----Detected #{len(result.paragraphs)} paragraphs in the document----")
PII-bearing data is written to a log/print sink — it stays in-process and does not leave the application, but logged PII is still a privacy concern.
Fix: Avoid logging user identifiers; redact or omit PII from log/print statements.
print(
f"Found paragraph with role: '{paragraph.role}' within {format_bounding_region(paragraph.bounding_regions)} bounding region"
)
PII-bearing data is written to a log/print sink — it stays in-process and does not leave the application, but logged PII is still a privacy concern.
Fix: Avoid logging user identifiers; redact or omit PII from log/print statements.
print(f"...with content: '{paragraph.content}'")
PII-bearing data is written to a log/print sink — it stays in-process and does not leave the application, but logged PII is still a privacy concern.
Fix: Avoid logging user identifiers; redact or omit PII from log/print statements.
print(f"...with offset: {paragraph.spans[0].offset} and length: {paragraph.spans[0].length}")
PII-bearing data is written to a log/print sink — it stays in-process and does not leave the application, but logged PII is still a privacy concern.
Fix: Avoid logging user identifiers; redact or omit PII from log/print statements.
print(f"--------Analysis of receipt #{idx + 1}--------")
PII-bearing data is written to a log/print sink — it stays in-process and does not leave the application, but logged PII is still a privacy concern.
Fix: Avoid logging user identifiers; redact or omit PII from log/print statements.
print(f"Receipt type: {receipt.doc_type if receipt.doc_type else 'N/A'}")
PII-bearing data is written to a log/print sink — it stays in-process and does not leave the application, but logged PII is still a privacy concern.
Fix: Avoid logging user identifiers; redact or omit PII from log/print statements.
print(
f"Merchant Name: {merchant_name.get('valueString')} has confidence: "
f"{merchant_name.confidence}"
)
PII-bearing data is written to a log/print sink — it stays in-process and does not leave the application, but logged PII is still a privacy concern.
Fix: Avoid logging user identifiers; redact or omit PII from log/print statements.
print(
f"Transaction Date: {transaction_date.get('valueDate')} has confidence: "
f"{transaction_date.confidence}"
)
PII-bearing data is written to a log/print sink — it stays in-process and does not leave the application, but logged PII is still a privacy concern.
Fix: Avoid logging user identifiers; redact or omit PII from log/print statements.
print(f"...Item #{idx + 1}")
PII-bearing data is written to a log/print sink — it stays in-process and does not leave the application, but logged PII is still a privacy concern.
Fix: Avoid logging user identifiers; redact or omit PII from log/print statements.
print(
f"......Item Description: {item_description.get('valueString')} has confidence: "
f"{item_description.confidence}"
)
PII-bearing data is written to a log/print sink — it stays in-process and does not leave the application, but logged PII is still a privacy concern.
Fix: Avoid logging user identifiers; redact or omit PII from log/print statements.
print(
f"......Item Quantity: {item_quantity.get('valueString')} has confidence: "
f"{item_quantity.confidence}"
)
PII-bearing data is written to a log/print sink — it stays in-process and does not leave the application, but logged PII is still a privacy concern.
Fix: Avoid logging user identifiers; redact or omit PII from log/print statements.
print(
f"......Total Item Price: {format_price(item_total_price.get('valueCurrency'))} has confidence: "
f"{item_total_price.confidence}"
)
PII-bearing data is written to a log/print sink — it stays in-process and does not leave the application, but logged PII is still a privacy concern.
Fix: Avoid logging user identifiers; redact or omit PII from log/print statements.
print(
f"Subtotal: {format_price(subtotal.get('valueCurrency'))} has confidence: {subtotal.confidence}"
)
PII-bearing data is written to a log/print sink — it stays in-process and does not leave the application, but logged PII is still a privacy concern.
Fix: Avoid logging user identifiers; redact or omit PII from log/print statements.
print(f"Total tax: {format_price(tax.get('valueCurrency'))} has confidence: {tax.confidence}")
PII-bearing data is written to a log/print sink — it stays in-process and does not leave the application, but logged PII is still a privacy concern.
Fix: Avoid logging user identifiers; redact or omit PII from log/print statements.
print(f"Tip: {format_price(tip.get('valueCurrency'))} has confidence: {tip.confidence}")
PII-bearing data is written to a log/print sink — it stays in-process and does not leave the application, but logged PII is still a privacy concern.
Fix: Avoid logging user identifiers; redact or omit PII from log/print statements.
print(f"Total: {format_price(total.get('valueCurrency'))} has confidence: {total.confidence}")
PII-bearing data is written to a log/print sink — it stays in-process and does not leave the application, but logged PII is still a privacy concern.
Fix: Avoid logging user identifiers; redact or omit PII from log/print statements.
print(f"--------Analysis of receipt #{idx + 1}--------")
PII-bearing data is written to a log/print sink — it stays in-process and does not leave the application, but logged PII is still a privacy concern.
Fix: Avoid logging user identifiers; redact or omit PII from log/print statements.
print(f"Receipt type: {receipt.doc_type if receipt.doc_type else 'N/A'}")
PII-bearing data is written to a log/print sink — it stays in-process and does not leave the application, but logged PII is still a privacy concern.
Fix: Avoid logging user identifiers; redact or omit PII from log/print statements.
print(
f"Merchant Name: {merchant_name.get('valueString')} has confidence: "
f"{merchant_name.confidence}"
)
PII-bearing data is written to a log/print sink — it stays in-process and does not leave the application, but logged PII is still a privacy concern.
Fix: Avoid logging user identifiers; redact or omit PII from log/print statements.
print(
f"Transaction Date: {transaction_date.get('valueDate')} has confidence: "
f"{transaction_date.confidence}"
)
PII-bearing data is written to a log/print sink — it stays in-process and does not leave the application, but logged PII is still a privacy concern.
Fix: Avoid logging user identifiers; redact or omit PII from log/print statements.
print(f"...Item #{idx + 1}")
PII-bearing data is written to a log/print sink — it stays in-process and does not leave the application, but logged PII is still a privacy concern.
Fix: Avoid logging user identifiers; redact or omit PII from log/print statements.
print(
f"......Item Description: {item_description.get('valueString')} has confidence: "
f"{item_description.confidence}"
)
PII-bearing data is written to a log/print sink — it stays in-process and does not leave the application, but logged PII is still a privacy concern.
Fix: Avoid logging user identifiers; redact or omit PII from log/print statements.
print(
f"......Item Quantity: {item_quantity.get('valueString')} has confidence: "
f"{item_quantity.confidence}"
)
PII-bearing data is written to a log/print sink — it stays in-process and does not leave the application, but logged PII is still a privacy concern.
Fix: Avoid logging user identifiers; redact or omit PII from log/print statements.
print(
f"......Total Item Price: {format_price(item_total_price.get('valueCurrency'))} has confidence: "
f"{item_total_price.confidence}"
)
PII-bearing data is written to a log/print sink — it stays in-process and does not leave the application, but logged PII is still a privacy concern.
Fix: Avoid logging user identifiers; redact or omit PII from log/print statements.
print(
f"Subtotal: {format_price(subtotal.get('valueCurrency'))} has confidence: {subtotal.confidence}"
)
PII-bearing data is written to a log/print sink — it stays in-process and does not leave the application, but logged PII is still a privacy concern.
Fix: Avoid logging user identifiers; redact or omit PII from log/print statements.
print(f"Total tax: {format_price(tax.get('valueCurrency'))} has confidence: {tax.confidence}")
PII-bearing data is written to a log/print sink — it stays in-process and does not leave the application, but logged PII is still a privacy concern.
Fix: Avoid logging user identifiers; redact or omit PII from log/print statements.
print(f"Tip: {format_price(tip.get('valueCurrency'))} has confidence: {tip.confidence}")
PII-bearing data is written to a log/print sink — it stays in-process and does not leave the application, but logged PII is still a privacy concern.
Fix: Avoid logging user identifiers; redact or omit PII from log/print statements.
print(f"Total: {format_price(total.get('valueCurrency'))} has confidence: {total.confidence}")
PII-bearing data is written to a log/print sink — it stays in-process and does not leave the application, but logged PII is still a privacy concern.
Fix: Avoid logging user identifiers; redact or omit PII from log/print statements.
print(f"--------Analyzing US Tax W-2 Form #{idx + 1}--------")
PII-bearing data is written to a log/print sink — it stays in-process and does not leave the application, but logged PII is still a privacy concern.
Fix: Avoid logging user identifiers; redact or omit PII from log/print statements.
print(
f"Form variant: {form_variant.get('valueString')} has confidence: " f"{form_variant.confidence}"
)
PII-bearing data is written to a log/print sink — it stays in-process and does not leave the application, but logged PII is still a privacy concern.
Fix: Avoid logging user identifiers; redact or omit PII from log/print statements.
print(f"Tax year: {tax_year.get('valueString')} has confidence: {tax_year.confidence}")
PII-bearing data is written to a log/print sink — it stays in-process and does not leave the application, but logged PII is still a privacy concern.
Fix: Avoid logging user identifiers; redact or omit PII from log/print statements.
print(f"W-2 Copy: {w2_copy.get('valueString')} has confidence: {w2_copy.confidence}")
PII-bearing data is written to a log/print sink — it stays in-process and does not leave the application, but logged PII is still a privacy concern.
Fix: Avoid logging user identifiers; redact or omit PII from log/print statements.
print(f"...Name: {employee_name.get('valueString')} has confidence: {employee_name.confidence}")
PII-bearing data is written to a log/print sink — it stays in-process and does not leave the application, but logged PII is still a privacy concern.
Fix: Avoid logging user identifiers; redact or omit PII from log/print statements.
print(f"...SSN: {employee_ssn.get('valueString')} has confidence: {employee_ssn.confidence}")
PII-bearing data is written to a log/print sink — it stays in-process and does not leave the application, but logged PII is still a privacy concern.
Fix: Avoid logging user identifiers; redact or omit PII from log/print statements.
print(f"...Address: {format_address_value(employee_address.get('valueAddress'))}")
PII-bearing data is written to a log/print sink — it stays in-process and does not leave the application, but logged PII is still a privacy concern.
Fix: Avoid logging user identifiers; redact or omit PII from log/print statements.
print(f"......has confidence: {employee_address.confidence}")
PII-bearing data is written to a log/print sink — it stays in-process and does not leave the application, but logged PII is still a privacy concern.
Fix: Avoid logging user identifiers; redact or omit PII from log/print statements.
print(f"...Zipcode: {employee_zipcode} has confidence: " f"{employee_address.confidence}")
PII-bearing data is written to a log/print sink — it stays in-process and does not leave the application, but logged PII is still a privacy concern.
Fix: Avoid logging user identifiers; redact or omit PII from log/print statements.
print(
f"Control Number: {control_number.get('valueString')} has confidence: "
f"{control_number.confidence}"
)
PII-bearing data is written to a log/print sink — it stays in-process and does not leave the application, but logged PII is still a privacy concern.
Fix: Avoid logging user identifiers; redact or omit PII from log/print statements.
print(f"...Name: {employer_name.get('valueString')} has confidence: {employer_name.confidence}")
PII-bearing data is written to a log/print sink — it stays in-process and does not leave the application, but logged PII is still a privacy concern.
Fix: Avoid logging user identifiers; redact or omit PII from log/print statements.
print(
f"...ID Number: {employer_id.get('valueString')} has confidence: {employer_id.confidence}"
)
PII-bearing data is written to a log/print sink — it stays in-process and does not leave the application, but logged PII is still a privacy concern.
Fix: Avoid logging user identifiers; redact or omit PII from log/print statements.
print(f"...Address: {format_address_value(employer_address.get('valueAddress'))}")
PII-bearing data is written to a log/print sink — it stays in-process and does not leave the application, but logged PII is still a privacy concern.
Fix: Avoid logging user identifiers; redact or omit PII from log/print statements.
print(f"\n......has confidence: {employer_address.confidence}")
PII-bearing data is written to a log/print sink — it stays in-process and does not leave the application, but logged PII is still a privacy concern.
Fix: Avoid logging user identifiers; redact or omit PII from log/print statements.
print(f"...Zipcode: {employer_zipcode} has confidence: {employer_address.confidence}")
PII-bearing data is written to a log/print sink — it stays in-process and does not leave the application, but logged PII is still a privacy concern.
Fix: Avoid logging user identifiers; redact or omit PII from log/print statements.
print(
f"Wages, tips, and other compensation: {wages_tips.get('valueNumber')} "
f"has confidence: {wages_tips.confidence}"
)
PII-bearing data is written to a log/print sink — it stays in-process and does not leave the application, but logged PII is still a privacy concern.
Fix: Avoid logging user identifiers; redact or omit PII from log/print statements.
print(
f"Federal income tax withheld: {fed_income_tax_withheld.get('valueNumber')} has "
f"confidence: {fed_income_tax_withheld.confidence}"
)
PII-bearing data is written to a log/print sink — it stays in-process and does not leave the application, but logged PII is still a privacy concern.
Fix: Avoid logging user identifiers; redact or omit PII from log/print statements.
print(
f"Social Security wages: {social_security_wages.get('valueNumber')} has confidence: "
f"{social_security_wages.confidence}"
)
PII-bearing data is written to a log/print sink — it stays in-process and does not leave the application, but logged PII is still a privacy concern.
Fix: Avoid logging user identifiers; redact or omit PII from log/print statements.
print(
f"Social Security tax withheld: {social_security_tax_withheld.get('valueNumber')} "
f"has confidence: {social_security_tax_withheld.confidence}"
)
PII-bearing data is written to a log/print sink — it stays in-process and does not leave the application, but logged PII is still a privacy concern.
Fix: Avoid logging user identifiers; redact or omit PII from log/print statements.
print(
f"Medicare wages and tips: {medicare_wages_tips.get('valueNumber')} has confidence: "
f"{medicare_wages_tips.confidence}"
)
PII-bearing data is written to a log/print sink — it stays in-process and does not leave the application, but logged PII is still a privacy concern.
Fix: Avoid logging user identifiers; redact or omit PII from log/print statements.
print(
f"Medicare tax withheld: {medicare_tax_withheld.get('valueNumber')} has confidence: "
f"{medicare_tax_withheld.confidence}"
)
PII-bearing data is written to a log/print sink — it stays in-process and does not leave the application, but logged PII is still a privacy concern.
Fix: Avoid logging user identifiers; redact or omit PII from log/print statements.
print(
f"Social Security tips: {social_security_tips.get('valueNumber')} has confidence: "
f"{social_security_tips.confidence}"
)
PII-bearing data is written to a log/print sink — it stays in-process and does not leave the application, but logged PII is still a privacy concern.
Fix: Avoid logging user identifiers; redact or omit PII from log/print statements.
print(
f"Allocated tips: {allocated_tips.get('valueNumber')} has confidence: {allocated_tips.confidence}"
)
PII-bearing data is written to a log/print sink — it stays in-process and does not leave the application, but logged PII is still a privacy concern.
Fix: Avoid logging user identifiers; redact or omit PII from log/print statements.
print(
f"Verification code: {verification_code.get('valueNumber')} has confidence: {verification_code.confidence}"
)
PII-bearing data is written to a log/print sink — it stays in-process and does not leave the application, but logged PII is still a privacy concern.
Fix: Avoid logging user identifiers; redact or omit PII from log/print statements.
print(
f"Dependent care benefits: {dependent_care_benefits.get('valueNumber')} has confidence: {dependent_care_benefits.confidence}"
)
PII-bearing data is written to a log/print sink — it stays in-process and does not leave the application, but logged PII is still a privacy concern.
Fix: Avoid logging user identifiers; redact or omit PII from log/print statements.
print(
f"Non-qualified plans: {non_qualified_plans.get('valueNumber')} has confidence: {non_qualified_plans.confidence}"
)
PII-bearing data is written to a log/print sink — it stays in-process and does not leave the application, but logged PII is still a privacy concern.
Fix: Avoid logging user identifiers; redact or omit PII from log/print statements.
print(
f"...Letter code: {letter_code.get('valueString')} has confidence: {letter_code.confidence}"
)
PII-bearing data is written to a log/print sink — it stays in-process and does not leave the application, but logged PII is still a privacy concern.
Fix: Avoid logging user identifiers; redact or omit PII from log/print statements.
print(f"...Amount: {amount.get('valueNumber')} has confidence: {amount.confidence}")
PII-bearing data is written to a log/print sink — it stays in-process and does not leave the application, but logged PII is still a privacy concern.
Fix: Avoid logging user identifiers; redact or omit PII from log/print statements.
print(
f"Is statutory employee: {is_statutory_employee.get('valueString')} has confidence: {is_statutory_employee.confidence}"
)
PII-bearing data is written to a log/print sink — it stays in-process and does not leave the application, but logged PII is still a privacy concern.
Fix: Avoid logging user identifiers; redact or omit PII from log/print statements.
print(
f"Is retirement plan: {is_retirement_plan.get('valueString')} has confidence: {is_retirement_plan.confidence}"
)
PII-bearing data is written to a log/print sink — it stays in-process and does not leave the application, but logged PII is still a privacy concern.
Fix: Avoid logging user identifiers; redact or omit PII from log/print statements.
print(
f"Is third party sick pay: {third_party_sick_pay.get('valueString')} has confidence: {third_party_sick_pay.confidence}"
)
PII-bearing data is written to a log/print sink — it stays in-process and does not leave the application, but logged PII is still a privacy concern.
Fix: Avoid logging user identifiers; redact or omit PII from log/print statements.
print(f"Other information: {other_info.get('valueString')} has confidence: {other_info.confidence}")
PII-bearing data is written to a log/print sink — it stays in-process and does not leave the application, but logged PII is still a privacy concern.
Fix: Avoid logging user identifiers; redact or omit PII from log/print statements.
print(f"...State: {state.get('valueString')} has confidence: {state.confidence}")
PII-bearing data is written to a log/print sink — it stays in-process and does not leave the application, but logged PII is still a privacy concern.
Fix: Avoid logging user identifiers; redact or omit PII from log/print statements.
print(
f"...Employer state ID number: {employer_state_id_number.get('valueString')} has "
f"confidence: {employer_state_id_number.confidence}"
)
PII-bearing data is written to a log/print sink — it stays in-process and does not leave the application, but logged PII is still a privacy concern.
Fix: Avoid logging user identifiers; redact or omit PII from log/print statements.
print(
f"...State wages, tips, etc: {state_wages_tips.get('valueNumber')} has confidence: "
f"{state_wages_tips.confidence}"
)
PII-bearing data is written to a log/print sink — it stays in-process and does not leave the application, but logged PII is still a privacy concern.
Fix: Avoid logging user identifiers; redact or omit PII from log/print statements.
print(
f"...State income tax: {state_income_tax.get('valueNumber')} has confidence: "
f"{state_income_tax.confidence}"
)
PII-bearing data is written to a log/print sink — it stays in-process and does not leave the application, but logged PII is still a privacy concern.
Fix: Avoid logging user identifiers; redact or omit PII from log/print statements.
print(
f"...Local wages, tips, etc: {local_wages_tips.get('valueNumber')} has confidence: "
f"{local_wages_tips.confidence}"
)
PII-bearing data is written to a log/print sink — it stays in-process and does not leave the application, but logged PII is still a privacy concern.
Fix: Avoid logging user identifiers; redact or omit PII from log/print statements.
print(
f"...Local income tax: {local_income_tax.get('valueNumber')} has confidence: "
f"{local_income_tax.confidence}"
)
PII-bearing data is written to a log/print sink — it stays in-process and does not leave the application, but logged PII is still a privacy concern.
Fix: Avoid logging user identifiers; redact or omit PII from log/print statements.
print(
f"...Locality name: {locality_name.get('valueString')} has confidence: "
f"{locality_name.confidence}"
)
PII-bearing data is written to a log/print sink — it stays in-process and does not leave the application, but logged PII is still a privacy concern.
Fix: Avoid logging user identifiers; redact or omit PII from log/print statements.
print(
f"Found document of type '{doc.doc_type or 'N/A'}' with a confidence of {doc.confidence} contained on "
f"the following pages: {[region.page_number for region in doc.bounding_regions]}"
)
PII-bearing data is written to a log/print sink — it stays in-process and does not leave the application, but logged PII is still a privacy concern.
Fix: Avoid logging user identifiers; redact or omit PII from log/print statements.
print(f"Model ID: {model.model_id}")
PII-bearing data is written to a log/print sink — it stays in-process and does not leave the application, but logged PII is still a privacy concern.
Fix: Avoid logging user identifiers; redact or omit PII from log/print statements.
print(f"Description: {model.description}")
PII-bearing data is written to a log/print sink — it stays in-process and does not leave the application, but logged PII is still a privacy concern.
Fix: Avoid logging user identifiers; redact or omit PII from log/print statements.
print(f"Model created on: {model.created_date_time}")
PII-bearing data is written to a log/print sink — it stays in-process and does not leave the application, but logged PII is still a privacy concern.
Fix: Avoid logging user identifiers; redact or omit PII from log/print statements.
print(f"Model expires on: {model.expiration_date_time}")
PII-bearing data is written to a log/print sink — it stays in-process and does not leave the application, but logged PII is still a privacy concern.
Fix: Avoid logging user identifiers; redact or omit PII from log/print statements.
print(f"Doc Type: '{name}' which has the following fields:")
PII-bearing data is written to a log/print sink — it stays in-process and does not leave the application, but logged PII is still a privacy concern.
Fix: Avoid logging user identifiers; redact or omit PII from log/print statements.
print(
f"Field: '{field_name}' has type '{field['type']}' and confidence score "
f"{doc_type.field_confidence[field_name]}"
)
PII-bearing data is written to a log/print sink — it stays in-process and does not leave the application, but logged PII is still a privacy concern.
Fix: Avoid logging user identifiers; redact or omit PII from log/print statements.
print(f"warning code: {warning.code}, message: {warning.message}, target of the error: {warning.target}")
PII-bearing data is written to a log/print sink — it stays in-process and does not leave the application, but logged PII is still a privacy concern.
Fix: Avoid logging user identifiers; redact or omit PII from log/print statements.
print(f"Model ID: '{model.model_id}'")
PII-bearing data is written to a log/print sink — it stays in-process and does not leave the application, but logged PII is still a privacy concern.
Fix: Avoid logging user identifiers; redact or omit PII from log/print statements.
print(f"Number of pages analyzed {len(model.pages)}")
PII-bearing data is written to a log/print sink — it stays in-process and does not leave the application, but logged PII is still a privacy concern.
Fix: Avoid logging user identifiers; redact or omit PII from log/print statements.
print(f"API version used: {model.api_version}")
PII-bearing data is written to a log/print sink — it stays in-process and does not leave the application, but logged PII is still a privacy concern.
Fix: Avoid logging user identifiers; redact or omit PII from log/print statements.
print(f"Model ID: {copied_over_model.model_id}")
PII-bearing data is written to a log/print sink — it stays in-process and does not leave the application, but logged PII is still a privacy concern.
Fix: Avoid logging user identifiers; redact or omit PII from log/print statements.
print(f"Description: {copied_over_model.description}")
PII-bearing data is written to a log/print sink — it stays in-process and does not leave the application, but logged PII is still a privacy concern.
Fix: Avoid logging user identifiers; redact or omit PII from log/print statements.
print(f"Model created on: {copied_over_model.created_date_time}")
PII-bearing data is written to a log/print sink — it stays in-process and does not leave the application, but logged PII is still a privacy concern.
Fix: Avoid logging user identifiers; redact or omit PII from log/print statements.
print(f"Model expires on: {copied_over_model.expiration_date_time}")
PII-bearing data is written to a log/print sink — it stays in-process and does not leave the application, but logged PII is still a privacy concern.
Fix: Avoid logging user identifiers; redact or omit PII from log/print statements.
print(f"Doc Type: '{name}' which has the following fields:")
PII-bearing data is written to a log/print sink — it stays in-process and does not leave the application, but logged PII is still a privacy concern.
Fix: Avoid logging user identifiers; redact or omit PII from log/print statements.
print(
f"Field: '{field_name}' has type '{field['type']}' and confidence score "
f"{doc_type.field_confidence[field_name]}"
)
PII-bearing data is written to a log/print sink — it stays in-process and does not leave the application, but logged PII is still a privacy concern.
Fix: Avoid logging user identifiers; redact or omit PII from log/print statements.
print(f"warning code: {warning.code}, message: {warning.message}, target of the error: {warning.target}")
PII-bearing data is written to a log/print sink — it stays in-process and does not leave the application, but logged PII is still a privacy concern.
Fix: Avoid logging user identifiers; redact or omit PII from log/print statements.
print(f"Built classifier with ID: {classifier.classifier_id}")
PII-bearing data is written to a log/print sink — it stays in-process and does not leave the application, but logged PII is still a privacy concern.
Fix: Avoid logging user identifiers; redact or omit PII from log/print statements.
print(f"API version used to build the classifier model: {classifier.api_version}")
PII-bearing data is written to a log/print sink — it stays in-process and does not leave the application, but logged PII is still a privacy concern.
Fix: Avoid logging user identifiers; redact or omit PII from log/print statements.
print(f"Classifier description: {classifier.description}")
PII-bearing data is written to a log/print sink — it stays in-process and does not leave the application, but logged PII is still a privacy concern.
Fix: Avoid logging user identifiers; redact or omit PII from log/print statements.
print(f"Document type: {doc_type}")
PII-bearing data is written to a log/print sink — it stays in-process and does not leave the application, but logged PII is still a privacy concern.
Fix: Avoid logging user identifiers; redact or omit PII from log/print statements.
print(f"Container source: {details.azure_blob_source.container_url}\n")
PII-bearing data is written to a log/print sink — it stays in-process and does not leave the application, but logged PII is still a privacy concern.
Fix: Avoid logging user identifiers; redact or omit PII from log/print statements.
print(f"{classifier.classifier_id} | {classifier.description}")
PII-bearing data is written to a log/print sink — it stays in-process and does not leave the application, but logged PII is still a privacy concern.
Fix: Avoid logging user identifiers; redact or omit PII from log/print statements.
print(f"\nClassifier ID: {my_classifier.classifier_id}")
PII-bearing data is written to a log/print sink — it stays in-process and does not leave the application, but logged PII is still a privacy concern.
Fix: Avoid logging user identifiers; redact or omit PII from log/print statements.
print(f"Description: {my_classifier.description}")
PII-bearing data is written to a log/print sink — it stays in-process and does not leave the application, but logged PII is still a privacy concern.
Fix: Avoid logging user identifiers; redact or omit PII from log/print statements.
print(f"Classifier created on: {my_classifier.created_date_time}")
PII-bearing data is written to a log/print sink — it stays in-process and does not leave the application, but logged PII is still a privacy concern.
Fix: Avoid logging user identifiers; redact or omit PII from log/print statements.
print(f"Classifier expires on: {my_classifier.expiration_date_time}")
PII-bearing data is written to a log/print sink — it stays in-process and does not leave the application, but logged PII is still a privacy concern.
Fix: Avoid logging user identifiers; redact or omit PII from log/print statements.
print(f"Successfully deleted classifier with ID {my_classifier.classifier_id}")
PII-bearing data is written to a log/print sink — it stays in-process and does not leave the application, but logged PII is still a privacy concern.
Fix: Avoid logging user identifiers; redact or omit PII from log/print statements.
print(f"Model ID: {model.model_id}")
PII-bearing data is written to a log/print sink — it stays in-process and does not leave the application, but logged PII is still a privacy concern.
Fix: Avoid logging user identifiers; redact or omit PII from log/print statements.
print(f"Description: {model.description}")
PII-bearing data is written to a log/print sink — it stays in-process and does not leave the application, but logged PII is still a privacy concern.
Fix: Avoid logging user identifiers; redact or omit PII from log/print statements.
print(f"Model created on: {model.created_date_time}")
PII-bearing data is written to a log/print sink — it stays in-process and does not leave the application, but logged PII is still a privacy concern.
Fix: Avoid logging user identifiers; redact or omit PII from log/print statements.
print(f"Model expires on: {model.expiration_date_time}")
PII-bearing data is written to a log/print sink — it stays in-process and does not leave the application, but logged PII is still a privacy concern.
Fix: Avoid logging user identifiers; redact or omit PII from log/print statements.
print(f"Doc Type: '{name}' built with '{doc_type.build_mode}' mode which has the following fields:")
PII-bearing data is written to a log/print sink — it stays in-process and does not leave the application, but logged PII is still a privacy concern.
Fix: Avoid logging user identifiers; redact or omit PII from log/print statements.
print(
f"Field: '{field_name}' has type '{field['type']}' and confidence score "
f"{doc_type.field_confidence[field_name]}"
)
PII-bearing data is written to a log/print sink — it stays in-process and does not leave the application, but logged PII is still a privacy concern.
Fix: Avoid logging user identifiers; redact or omit PII from log/print statements.
print(
f"warning code: {warning.code}, message: {warning.message}, target of the error: {warning.target}"
)
PII-bearing data is written to a log/print sink — it stays in-process and does not leave the application, but logged PII is still a privacy concern.
Fix: Avoid logging user identifiers; redact or omit PII from log/print statements.
print(
f"Our resource has {account_details.custom_document_models.count} custom models, "
f"and we can have at most {account_details.custom_document_models.limit} custom models"
)
PII-bearing data is written to a log/print sink — it stays in-process and does not leave the application, but logged PII is still a privacy concern.
Fix: Avoid logging user identifiers; redact or omit PII from log/print statements.
print(f"{model.model_id} | {model.description}")
PII-bearing data is written to a log/print sink — it stays in-process and does not leave the application, but logged PII is still a privacy concern.
Fix: Avoid logging user identifiers; redact or omit PII from log/print statements.
print(f"\nModel ID: {my_model.model_id}")
PII-bearing data is written to a log/print sink — it stays in-process and does not leave the application, but logged PII is still a privacy concern.
Fix: Avoid logging user identifiers; redact or omit PII from log/print statements.
print(f"Description: {my_model.description}")
PII-bearing data is written to a log/print sink — it stays in-process and does not leave the application, but logged PII is still a privacy concern.
Fix: Avoid logging user identifiers; redact or omit PII from log/print statements.
print(f"Model created on: {my_model.created_date_time}")
PII-bearing data is written to a log/print sink — it stays in-process and does not leave the application, but logged PII is still a privacy concern.
Fix: Avoid logging user identifiers; redact or omit PII from log/print statements.
print(f"Model expires on: {my_model.expiration_date_time}")
PII-bearing data is written to a log/print sink — it stays in-process and does not leave the application, but logged PII is still a privacy concern.
Fix: Avoid logging user identifiers; redact or omit PII from log/print statements.
print(f"Successfully deleted model with ID {my_model.model_id}")
PII-bearing data is written to a log/print sink — it stays in-process and does not leave the application, but logged PII is still a privacy concern.
Fix: Avoid logging user identifiers; redact or omit PII from log/print statements.
print(
f"Our resource has {response_body['customDocumentModels']['count']} custom models, "
f"and we can have at most {response_body['customDocumentModels']['limit']} custom models."
f"The quota limit for custom neural document models is {response_body['customNeuralDocumentModelBuilds']['quota']} and the resource has"
f"used {response_body['customNeuralDocumentModelBuilds']['used']}. The resource quota will reset on {response_body['customNeuralDocumentModelBuilds']['quotaResetDateTime']}"
)
PII-bearing data is written to a log/print sink — it stays in-process and does not leave the application, but logged PII is still a privacy concern.
Fix: Avoid logging user identifiers; redact or omit PII from log/print statements.
print(f"----Barcodes detected from page #{page.page_number}----")
PII-bearing data is written to a log/print sink — it stays in-process and does not leave the application, but logged PII is still a privacy concern.
Fix: Avoid logging user identifiers; redact or omit PII from log/print statements.
print(f"Detected {len(page.barcodes)} barcodes:")
PII-bearing data is written to a log/print sink — it stays in-process and does not leave the application, but logged PII is still a privacy concern.
Fix: Avoid logging user identifiers; redact or omit PII from log/print statements.
print(f"- Barcode #{barcode_idx}: {barcode.value}")
PII-bearing data is written to a log/print sink — it stays in-process and does not leave the application, but logged PII is still a privacy concern.
Fix: Avoid logging user identifiers; redact or omit PII from log/print statements.
print(f" Kind: {barcode.kind}")
PII-bearing data is written to a log/print sink — it stays in-process and does not leave the application, but logged PII is still a privacy concern.
Fix: Avoid logging user identifiers; redact or omit PII from log/print statements.
print(f" Confidence: {barcode.confidence}")
PII-bearing data is written to a log/print sink — it stays in-process and does not leave the application, but logged PII is still a privacy concern.
Fix: Avoid logging user identifiers; redact or omit PII from log/print statements.
print(
", ".join(
[
f"[{barcode.polygon[i]}, {barcode.polygon[i + 1]}]"
for i in range(0, len(barcode.polygon), 2)
]
)
)
PII-bearing data is written to a log/print sink — it stays in-process and does not leave the application, but logged PII is still a privacy concern.
Fix: Avoid logging user identifiers; redact or omit PII from log/print statements.
print(f" Text: '{_get_styled_text(styles, result.content)}'")
PII-bearing data is written to a log/print sink — it stays in-process and does not leave the application, but logged PII is still a privacy concern.
Fix: Avoid logging user identifiers; redact or omit PII from log/print statements.
print(f" Text: '{_get_styled_text(styles, result.content)}'")
PII-bearing data is written to a log/print sink — it stays in-process and does not leave the application, but logged PII is still a privacy concern.
Fix: Avoid logging user identifiers; redact or omit PII from log/print statements.
print(f" Text: '{_get_styled_text(styles, result.content)}'")
PII-bearing data is written to a log/print sink — it stays in-process and does not leave the application, but logged PII is still a privacy concern.
Fix: Avoid logging user identifiers; redact or omit PII from log/print statements.
print(f" Text: '{_get_styled_text(styles, result.content)}'")
PII-bearing data is written to a log/print sink — it stays in-process and does not leave the application, but logged PII is still a privacy concern.
Fix: Avoid logging user identifiers; redact or omit PII from log/print statements.
print(f" Text: '{_get_styled_text(styles, result.content)}'")
PII-bearing data is written to a log/print sink — it stays in-process and does not leave the application, but logged PII is still a privacy concern.
Fix: Avoid logging user identifiers; redact or omit PII from log/print statements.
print(f"----Formulas detected from page #{page.page_number}----")
PII-bearing data is written to a log/print sink — it stays in-process and does not leave the application, but logged PII is still a privacy concern.
Fix: Avoid logging user identifiers; redact or omit PII from log/print statements.
print(f"Detected {len(inline_formulas)} inline formulas.")
PII-bearing data is written to a log/print sink — it stays in-process and does not leave the application, but logged PII is still a privacy concern.
Fix: Avoid logging user identifiers; redact or omit PII from log/print statements.
print(f"- Inline #{formula_idx}: {formula.value}")
PII-bearing data is written to a log/print sink — it stays in-process and does not leave the application, but logged PII is still a privacy concern.
Fix: Avoid logging user identifiers; redact or omit PII from log/print statements.
print(f" Confidence: {formula.confidence}")
PII-bearing data is written to a log/print sink — it stays in-process and does not leave the application, but logged PII is still a privacy concern.
Fix: Avoid logging user identifiers; redact or omit PII from log/print statements.
print(f" Bounding regions: {_format_polygon(formula.polygon)}")
PII-bearing data is written to a log/print sink — it stays in-process and does not leave the application, but logged PII is still a privacy concern.
Fix: Avoid logging user identifiers; redact or omit PII from log/print statements.
print(f"\nDetected {len(display_formulas)} display formulas.")
PII-bearing data is written to a log/print sink — it stays in-process and does not leave the application, but logged PII is still a privacy concern.
Fix: Avoid logging user identifiers; redact or omit PII from log/print statements.
print(f"- Display #{formula_idx}: {formula.value}")
PII-bearing data is written to a log/print sink — it stays in-process and does not leave the application, but logged PII is still a privacy concern.
Fix: Avoid logging user identifiers; redact or omit PII from log/print statements.
print(f" Confidence: {formula.confidence}")
PII-bearing data is written to a log/print sink — it stays in-process and does not leave the application, but logged PII is still a privacy concern.
Fix: Avoid logging user identifiers; redact or omit PII from log/print statements.
print(f" Bounding regions: {_format_polygon(formula.polygon)}")
PII-bearing data is written to a log/print sink — it stays in-process and does not leave the application, but logged PII is still a privacy concern.
Fix: Avoid logging user identifiers; redact or omit PII from log/print statements.
print(f"----Analyzing layout from page #{page.page_number}----")
PII-bearing data is written to a log/print sink — it stays in-process and does not leave the application, but logged PII is still a privacy concern.
Fix: Avoid logging user identifiers; redact or omit PII from log/print statements.
print(f"Page has width: {page.width} and height: {page.height}, measured with unit: {page.unit}")
PII-bearing data is written to a log/print sink — it stays in-process and does not leave the application, but logged PII is still a privacy concern.
Fix: Avoid logging user identifiers; redact or omit PII from log/print statements.
print(f"......Word '{word.content}' has a confidence of {word.confidence}")
PII-bearing data is written to a log/print sink — it stays in-process and does not leave the application, but logged PII is still a privacy concern.
Fix: Avoid logging user identifiers; redact or omit PII from log/print statements.
print(
f"...Line # {line_idx} has word count {len(words)} and text '{line.content}' "
f"within bounding polygon '{_format_polygon(line.polygon)}'"
)
PII-bearing data is written to a log/print sink — it stays in-process and does not leave the application, but logged PII is still a privacy concern.
Fix: Avoid logging user identifiers; redact or omit PII from log/print statements.
print(
f"Selection mark is '{selection_mark.state}' within bounding polygon "
f"'{_format_polygon(selection_mark.polygon)}' and has a confidence of {selection_mark.confidence}"
)
PII-bearing data is written to a log/print sink — it stays in-process and does not leave the application, but logged PII is still a privacy concern.
Fix: Avoid logging user identifiers; redact or omit PII from log/print statements.
print(f"Table # {table_idx} has {table.row_count} rows and " f"{table.column_count} columns")
PII-bearing data is written to a log/print sink — it stays in-process and does not leave the application, but logged PII is still a privacy concern.
Fix: Avoid logging user identifiers; redact or omit PII from log/print statements.
print(
f"Table # {table_idx} location on page: {region.page_number} is {_format_polygon(region.polygon)}"
)
PII-bearing data is written to a log/print sink — it stays in-process and does not leave the application, but logged PII is still a privacy concern.
Fix: Avoid logging user identifiers; redact or omit PII from log/print statements.
print(f"...Cell[{cell.row_index}][{cell.column_index}] has text '{cell.content}'")
PII-bearing data is written to a log/print sink — it stays in-process and does not leave the application, but logged PII is still a privacy concern.
Fix: Avoid logging user identifiers; redact or omit PII from log/print statements.
print(
f"...content on page {region.page_number} is within bounding polygon '{_format_polygon(region.polygon)}'"
)
PII-bearing data is written to a log/print sink — it stays in-process and does not leave the application, but logged PII is still a privacy concern.
Fix: Avoid logging user identifiers; redact or omit PII from log/print statements.
print(f"Detected {len(result.languages)} languages:")
PII-bearing data is written to a log/print sink — it stays in-process and does not leave the application, but logged PII is still a privacy concern.
Fix: Avoid logging user identifiers; redact or omit PII from log/print statements.
print(f"- Language #{lang_idx}: locale '{lang.locale}'")
PII-bearing data is written to a log/print sink — it stays in-process and does not leave the application, but logged PII is still a privacy concern.
Fix: Avoid logging user identifiers; redact or omit PII from log/print statements.
print(f" Confidence: {lang.confidence}")
PII-bearing data is written to a log/print sink — it stays in-process and does not leave the application, but logged PII is still a privacy concern.
Fix: Avoid logging user identifiers; redact or omit PII from log/print statements.
print(f"Address: {doc.fields['Address'].value_string}")
PII-bearing data is written to a log/print sink — it stays in-process and does not leave the application, but logged PII is still a privacy concern.
Fix: Avoid logging user identifiers; redact or omit PII from log/print statements.
print(f"Invoice number: {doc.fields['InvoiceNumber'].value_string}")
PII-bearing data is written to a log/print sink — it stays in-process and does not leave the application, but logged PII is still a privacy concern.
Fix: Avoid logging user identifiers; redact or omit PII from log/print statements.
print(f"Succeeded count: {final_result.succeeded_count}")
PII-bearing data is written to a log/print sink — it stays in-process and does not leave the application, but logged PII is still a privacy concern.
Fix: Avoid logging user identifiers; redact or omit PII from log/print statements.
print(f"Failed count: {final_result.failed_count}")
PII-bearing data is written to a log/print sink — it stays in-process and does not leave the application, but logged PII is still a privacy concern.
Fix: Avoid logging user identifiers; redact or omit PII from log/print statements.
print(f"Skipped count: {final_result.skipped_count}")
PII-bearing data is written to a log/print sink — it stays in-process and does not leave the application, but logged PII is still a privacy concern.
Fix: Avoid logging user identifiers; redact or omit PII from log/print statements.
print(f"--------Analyzing document #{idx + 1}--------")
PII-bearing data is written to a log/print sink — it stays in-process and does not leave the application, but logged PII is still a privacy concern.
Fix: Avoid logging user identifiers; redact or omit PII from log/print statements.
print(f"Document has type {document.doc_type}")
PII-bearing data is written to a log/print sink — it stays in-process and does not leave the application, but logged PII is still a privacy concern.
Fix: Avoid logging user identifiers; redact or omit PII from log/print statements.
print(f"Document has document type confidence {document.confidence}")
PII-bearing data is written to a log/print sink — it stays in-process and does not leave the application, but logged PII is still a privacy concern.
Fix: Avoid logging user identifiers; redact or omit PII from log/print statements.
print(f"Document was analyzed with model with ID {result.model_id}")
PII-bearing data is written to a log/print sink — it stays in-process and does not leave the application, but logged PII is still a privacy concern.
Fix: Avoid logging user identifiers; redact or omit PII from log/print statements.
print(
f"......found field of type '{field.type}' with value '{field_value}' and with confidence {field.confidence}"
)
PII-bearing data is written to a log/print sink — it stays in-process and does not leave the application, but logged PII is still a privacy concern.
Fix: Avoid logging user identifiers; redact or omit PII from log/print statements.
print(f"Here's the full content in format {result.content_format}:\n")
PII-bearing data is written to a log/print sink — it stays in-process and does not leave the application, but logged PII is still a privacy concern.
Fix: Avoid logging user identifiers; redact or omit PII from log/print statements.
print(result.content)
PII-bearing data is written to a log/print sink — it stays in-process and does not leave the application, but logged PII is still a privacy concern.
Fix: Avoid logging user identifiers; redact or omit PII from log/print statements.
print(
f"Key '{kv_pair.key.content}' found within "
f"'{_format_bounding_region(kv_pair.key.bounding_regions)}' bounding regions"
)
PII-bearing data is written to a log/print sink — it stays in-process and does not leave the application, but logged PII is still a privacy concern.
Fix: Avoid logging user identifiers; redact or omit PII from log/print statements.
print(
f"Value '{kv_pair.value.content}' found within "
f"'{_format_bounding_region(kv_pair.value.bounding_regions)}' bounding regions\n"
)
PII-bearing data is written to a log/print sink — it stays in-process and does not leave the application, but logged PII is still a privacy concern.
Fix: Avoid logging user identifiers; redact or omit PII from log/print statements.
print(f"----Analyzing document from page #{page.page_number}----")
PII-bearing data is written to a log/print sink — it stays in-process and does not leave the application, but logged PII is still a privacy concern.
Fix: Avoid logging user identifiers; redact or omit PII from log/print statements.
print(f"Page has width: {page.width} and height: {page.height}, measured with unit: {page.unit}")
PII-bearing data is written to a log/print sink — it stays in-process and does not leave the application, but logged PII is still a privacy concern.
Fix: Avoid logging user identifiers; redact or omit PII from log/print statements.
print(f"......Word '{word.content}' has a confidence of {word.confidence}")
PII-bearing data is written to a log/print sink — it stays in-process and does not leave the application, but logged PII is still a privacy concern.
Fix: Avoid logging user identifiers; redact or omit PII from log/print statements.
print(
f"...Line #{line_idx} has {len(words)} words and text '{line.content}' within "
f"bounding polygon '{_format_polygon(line.polygon)}'"
)
PII-bearing data is written to a log/print sink — it stays in-process and does not leave the application, but logged PII is still a privacy concern.
Fix: Avoid logging user identifiers; redact or omit PII from log/print statements.
print(
f"Selection mark is '{selection_mark.state}' within bounding polygon "
f"'{_format_polygon(selection_mark.polygon)}' and has a confidence of "
f"{selection_mark.confidence}"
)
PII-bearing data is written to a log/print sink — it stays in-process and does not leave the application, but logged PII is still a privacy concern.
Fix: Avoid logging user identifiers; redact or omit PII from log/print statements.
print(f"Table # {table_idx} has {table.row_count} rows and {table.column_count} columns")
PII-bearing data is written to a log/print sink — it stays in-process and does not leave the application, but logged PII is still a privacy concern.
Fix: Avoid logging user identifiers; redact or omit PII from log/print statements.
print(
f"Table # {table_idx} location on page: {region.page_number} is {_format_polygon(region.polygon)}"
)
PII-bearing data is written to a log/print sink — it stays in-process and does not leave the application, but logged PII is still a privacy concern.
Fix: Avoid logging user identifiers; redact or omit PII from log/print statements.
print(f"...Cell[{cell.row_index}][{cell.column_index}] has text '{cell.content}'")
PII-bearing data is written to a log/print sink — it stays in-process and does not leave the application, but logged PII is still a privacy concern.
Fix: Avoid logging user identifiers; redact or omit PII from log/print statements.
print(
f"...content on page {region.page_number} is within bounding polygon '{_format_polygon(region.polygon)}'\n"
)
PII-bearing data is written to a log/print sink — it stays in-process and does not leave the application, but logged PII is still a privacy concern.
Fix: Avoid logging user identifiers; redact or omit PII from log/print statements.
print(f"--------Analyzing ID document #{idx + 1}--------")
PII-bearing data is written to a log/print sink — it stays in-process and does not leave the application, but logged PII is still a privacy concern.
Fix: Avoid logging user identifiers; redact or omit PII from log/print statements.
print(f"First Name: {first_name.get('valueString')} has confidence: {first_name.confidence}")
PII-bearing data is written to a log/print sink — it stays in-process and does not leave the application, but logged PII is still a privacy concern.
Fix: Avoid logging user identifiers; redact or omit PII from log/print statements.
print(f"Last Name: {last_name.get('valueString')} has confidence: {last_name.confidence}")
PII-bearing data is written to a log/print sink — it stays in-process and does not leave the application, but logged PII is still a privacy concern.
Fix: Avoid logging user identifiers; redact or omit PII from log/print statements.
print(
f"Document Number: {document_number.get('valueString')} has confidence: {document_number.confidence}"
)
PII-bearing data is written to a log/print sink — it stays in-process and does not leave the application, but logged PII is still a privacy concern.
Fix: Avoid logging user identifiers; redact or omit PII from log/print statements.
print(f"Date of Birth: {dob.get('valueDate')} has confidence: {dob.confidence}")
PII-bearing data is written to a log/print sink — it stays in-process and does not leave the application, but logged PII is still a privacy concern.
Fix: Avoid logging user identifiers; redact or omit PII from log/print statements.
print(f"Date of Expiration: {doe.get('valueDate')} has confidence: {doe.confidence}")
PII-bearing data is written to a log/print sink — it stays in-process and does not leave the application, but logged PII is still a privacy concern.
Fix: Avoid logging user identifiers; redact or omit PII from log/print statements.
print(f"Sex: {sex.get('valueString')} has confidence: {sex.confidence}")
PII-bearing data is written to a log/print sink — it stays in-process and does not leave the application, but logged PII is still a privacy concern.
Fix: Avoid logging user identifiers; redact or omit PII from log/print statements.
print(f"Address: {address.get('valueString')} has confidence: {address.confidence}")
PII-bearing data is written to a log/print sink — it stays in-process and does not leave the application, but logged PII is still a privacy concern.
Fix: Avoid logging user identifiers; redact or omit PII from log/print statements.
print(
f"Country/Region: {country_region.get('valueCountryRegion')} has confidence: {country_region.confidence}"
)
PII-bearing data is written to a log/print sink — it stays in-process and does not leave the application, but logged PII is still a privacy concern.
Fix: Avoid logging user identifiers; redact or omit PII from log/print statements.
print(f"Region: {region.get('valueString')} has confidence: {region.confidence}")
PII-bearing data is written to a log/print sink — it stays in-process and does not leave the application, but logged PII is still a privacy concern.
Fix: Avoid logging user identifiers; redact or omit PII from log/print statements.
print(f"--------Analyzing invoice #{idx + 1}--------")
PII-bearing data is written to a log/print sink — it stays in-process and does not leave the application, but logged PII is still a privacy concern.
Fix: Avoid logging user identifiers; redact or omit PII from log/print statements.
print(f"Vendor Name: {vendor_name.get('content')} has confidence: {vendor_name.get('confidence')}")
PII-bearing data is written to a log/print sink — it stays in-process and does not leave the application, but logged PII is still a privacy concern.
Fix: Avoid logging user identifiers; redact or omit PII from log/print statements.
print(
f"Vendor Address: {vendor_address.get('content')} has confidence: {vendor_address.get('confidence')}"
)
PII-bearing data is written to a log/print sink — it stays in-process and does not leave the application, but logged PII is still a privacy concern.
Fix: Avoid logging user identifiers; redact or omit PII from log/print statements.
print(
f"Vendor Address Recipient: {vendor_address_recipient.get('content')} has confidence: {vendor_address_recipient.get('confidence')}"
)
PII-bearing data is written to a log/print sink — it stays in-process and does not leave the application, but logged PII is still a privacy concern.
Fix: Avoid logging user identifiers; redact or omit PII from log/print statements.
print(
f"Customer Name: {customer_name.get('content')} has confidence: {customer_name.get('confidence')}"
)
PII-bearing data is written to a log/print sink — it stays in-process and does not leave the application, but logged PII is still a privacy concern.
Fix: Avoid logging user identifiers; redact or omit PII from log/print statements.
print(f"Customer Id: {customer_id.get('content')} has confidence: {customer_id.get('confidence')}")
PII-bearing data is written to a log/print sink — it stays in-process and does not leave the application, but logged PII is still a privacy concern.
Fix: Avoid logging user identifiers; redact or omit PII from log/print statements.
print(
f"Customer Address: {customer_address.get('content')} has confidence: {customer_address.get('confidence')}"
)
PII-bearing data is written to a log/print sink — it stays in-process and does not leave the application, but logged PII is still a privacy concern.
Fix: Avoid logging user identifiers; redact or omit PII from log/print statements.
print(
f"Customer Address Recipient: {customer_address_recipient.get('content')} has confidence: {customer_address_recipient.get('confidence')}"
)
PII-bearing data is written to a log/print sink — it stays in-process and does not leave the application, but logged PII is still a privacy concern.
Fix: Avoid logging user identifiers; redact or omit PII from log/print statements.
print(f"Invoice Id: {invoice_id.get('content')} has confidence: {invoice_id.get('confidence')}")
PII-bearing data is written to a log/print sink — it stays in-process and does not leave the application, but logged PII is still a privacy concern.
Fix: Avoid logging user identifiers; redact or omit PII from log/print statements.
print(
f"Invoice Date: {invoice_date.get('content')} has confidence: {invoice_date.get('confidence')}"
)
PII-bearing data is written to a log/print sink — it stays in-process and does not leave the application, but logged PII is still a privacy concern.
Fix: Avoid logging user identifiers; redact or omit PII from log/print statements.
print(
f"Invoice Total: {invoice_total.get('content')} has confidence: {invoice_total.get('confidence')}"
)
PII-bearing data is written to a log/print sink — it stays in-process and does not leave the application, but logged PII is still a privacy concern.
Fix: Avoid logging user identifiers; redact or omit PII from log/print statements.
print(f"Due Date: {due_date.get('content')} has confidence: {due_date.get('confidence')}")
PII-bearing data is written to a log/print sink — it stays in-process and does not leave the application, but logged PII is still a privacy concern.
Fix: Avoid logging user identifiers; redact or omit PII from log/print statements.
print(
f"Purchase Order: {purchase_order.get('content')} has confidence: {purchase_order.get('confidence')}"
)
PII-bearing data is written to a log/print sink — it stays in-process and does not leave the application, but logged PII is still a privacy concern.
Fix: Avoid logging user identifiers; redact or omit PII from log/print statements.
print(
f"Billing Address: {billing_address.get('content')} has confidence: {billing_address.get('confidence')}"
)
PII-bearing data is written to a log/print sink — it stays in-process and does not leave the application, but logged PII is still a privacy concern.
Fix: Avoid logging user identifiers; redact or omit PII from log/print statements.
print(
f"Billing Address Recipient: {billing_address_recipient.get('content')} has confidence: {billing_address_recipient.get('confidence')}"
)
PII-bearing data is written to a log/print sink — it stays in-process and does not leave the application, but logged PII is still a privacy concern.
Fix: Avoid logging user identifiers; redact or omit PII from log/print statements.
print(
f"Shipping Address: {shipping_address.get('content')} has confidence: {shipping_address.get('confidence')}"
)
PII-bearing data is written to a log/print sink — it stays in-process and does not leave the application, but logged PII is still a privacy concern.
Fix: Avoid logging user identifiers; redact or omit PII from log/print statements.
print(
f"Shipping Address Recipient: {shipping_address_recipient.get('content')} has confidence: {shipping_address_recipient.get('confidence')}"
)
PII-bearing data is written to a log/print sink — it stays in-process and does not leave the application, but logged PII is still a privacy concern.
Fix: Avoid logging user identifiers; redact or omit PII from log/print statements.
print(f"...Item #{idx + 1}")
PII-bearing data is written to a log/print sink — it stays in-process and does not leave the application, but logged PII is still a privacy concern.
Fix: Avoid logging user identifiers; redact or omit PII from log/print statements.
print(
f"......Description: {item_description.get('content')} has confidence: {item_description.get('confidence')}"
)
PII-bearing data is written to a log/print sink — it stays in-process and does not leave the application, but logged PII is still a privacy concern.
Fix: Avoid logging user identifiers; redact or omit PII from log/print statements.
print(
f"......Quantity: {item_quantity.get('content')} has confidence: {item_quantity.get('confidence')}"
)
PII-bearing data is written to a log/print sink — it stays in-process and does not leave the application, but logged PII is still a privacy concern.
Fix: Avoid logging user identifiers; redact or omit PII from log/print statements.
print(f"......Unit: {unit.get('content')} has confidence: {unit.get('confidence')}")
PII-bearing data is written to a log/print sink — it stays in-process and does not leave the application, but logged PII is still a privacy concern.
Fix: Avoid logging user identifiers; redact or omit PII from log/print statements.
print(
f"......Unit Price: {unit_price.get('content')}{unit_price_code} has confidence: {unit_price.get('confidence')}"
)
PII-bearing data is written to a log/print sink — it stays in-process and does not leave the application, but logged PII is still a privacy concern.
Fix: Avoid logging user identifiers; redact or omit PII from log/print statements.
print(
f"......Product Code: {product_code.get('content')} has confidence: {product_code.get('confidence')}"
)
PII-bearing data is written to a log/print sink — it stays in-process and does not leave the application, but logged PII is still a privacy concern.
Fix: Avoid logging user identifiers; redact or omit PII from log/print statements.
print(
f"......Date: {item_date.get('content')} has confidence: {item_date.get('confidence')}"
)
PII-bearing data is written to a log/print sink — it stays in-process and does not leave the application, but logged PII is still a privacy concern.
Fix: Avoid logging user identifiers; redact or omit PII from log/print statements.
print(f"......Tax: {tax.get('content')} has confidence: {tax.get('confidence')}")
PII-bearing data is written to a log/print sink — it stays in-process and does not leave the application, but logged PII is still a privacy concern.
Fix: Avoid logging user identifiers; redact or omit PII from log/print statements.
print(f"......Amount: {amount.get('content')} has confidence: {amount.get('confidence')}")
PII-bearing data is written to a log/print sink — it stays in-process and does not leave the application, but logged PII is still a privacy concern.
Fix: Avoid logging user identifiers; redact or omit PII from log/print statements.
print(f"Subtotal: {subtotal.get('content')} has confidence: {subtotal.get('confidence')}")
PII-bearing data is written to a log/print sink — it stays in-process and does not leave the application, but logged PII is still a privacy concern.
Fix: Avoid logging user identifiers; redact or omit PII from log/print statements.
print(f"Total Tax: {total_tax.get('content')} has confidence: {total_tax.get('confidence')}")
PII-bearing data is written to a log/print sink — it stays in-process and does not leave the application, but logged PII is still a privacy concern.
Fix: Avoid logging user identifiers; redact or omit PII from log/print statements.
print(
f"Previous Unpaid Balance: {previous_unpaid_balance.get('content')} has confidence: {previous_unpaid_balance.get('confidence')}"
)
PII-bearing data is written to a log/print sink — it stays in-process and does not leave the application, but logged PII is still a privacy concern.
Fix: Avoid logging user identifiers; redact or omit PII from log/print statements.
print(f"Amount Due: {amount_due.get('content')} has confidence: {amount_due.get('confidence')}")
PII-bearing data is written to a log/print sink — it stays in-process and does not leave the application, but logged PII is still a privacy concern.
Fix: Avoid logging user identifiers; redact or omit PII from log/print statements.
print(
f"Service Start Date: {service_start_date.get('content')} has confidence: {service_start_date.get('confidence')}"
)
PII-bearing data is written to a log/print sink — it stays in-process and does not leave the application, but logged PII is still a privacy concern.
Fix: Avoid logging user identifiers; redact or omit PII from log/print statements.
print(
f"Service End Date: {service_end_date.get('content')} has confidence: {service_end_date.get('confidence')}"
)
PII-bearing data is written to a log/print sink — it stays in-process and does not leave the application, but logged PII is still a privacy concern.
Fix: Avoid logging user identifiers; redact or omit PII from log/print statements.
print(
f"Service Address: {service_address.get('content')} has confidence: {service_address.get('confidence')}"
)
PII-bearing data is written to a log/print sink — it stays in-process and does not leave the application, but logged PII is still a privacy concern.
Fix: Avoid logging user identifiers; redact or omit PII from log/print statements.
print(
f"Service Address Recipient: {service_address_recipient.get('content')} has confidence: {service_address_recipient.get('confidence')}"
)
PII-bearing data is written to a log/print sink — it stays in-process and does not leave the application, but logged PII is still a privacy concern.
Fix: Avoid logging user identifiers; redact or omit PII from log/print statements.
print(
f"Remittance Address: {remittance_address.get('content')} has confidence: {remittance_address.get('confidence')}"
)
PII-bearing data is written to a log/print sink — it stays in-process and does not leave the application, but logged PII is still a privacy concern.
Fix: Avoid logging user identifiers; redact or omit PII from log/print statements.
print(
f"Remittance Address Recipient: {remittance_address_recipient.get('content')} has confidence: {remittance_address_recipient.get('confidence')}"
)
PII-bearing data is written to a log/print sink — it stays in-process and does not leave the application, but logged PII is still a privacy concern.
Fix: Avoid logging user identifiers; redact or omit PII from log/print statements.
print(f"--------Analyzing invoice #{idx + 1}--------")
PII-bearing data is written to a log/print sink — it stays in-process and does not leave the application, but logged PII is still a privacy concern.
Fix: Avoid logging user identifiers; redact or omit PII from log/print statements.
print(f"Vendor Name: {vendor_name.get('content')} has confidence: {vendor_name.get('confidence')}")
PII-bearing data is written to a log/print sink — it stays in-process and does not leave the application, but logged PII is still a privacy concern.
Fix: Avoid logging user identifiers; redact or omit PII from log/print statements.
print(
f"Vendor Address: {vendor_address.get('content')} has confidence: {vendor_address.get('confidence')}"
)
PII-bearing data is written to a log/print sink — it stays in-process and does not leave the application, but logged PII is still a privacy concern.
Fix: Avoid logging user identifiers; redact or omit PII from log/print statements.
print(
f"Vendor Address Recipient: {vendor_address_recipient.get('content')} has confidence: {vendor_address_recipient.get('confidence')}"
)
PII-bearing data is written to a log/print sink — it stays in-process and does not leave the application, but logged PII is still a privacy concern.
Fix: Avoid logging user identifiers; redact or omit PII from log/print statements.
print(
f"Customer Name: {customer_name.get('content')} has confidence: {customer_name.get('confidence')}"
)
PII-bearing data is written to a log/print sink — it stays in-process and does not leave the application, but logged PII is still a privacy concern.
Fix: Avoid logging user identifiers; redact or omit PII from log/print statements.
print(f"Customer Id: {customer_id.get('content')} has confidence: {customer_id.get('confidence')}")
PII-bearing data is written to a log/print sink — it stays in-process and does not leave the application, but logged PII is still a privacy concern.
Fix: Avoid logging user identifiers; redact or omit PII from log/print statements.
print(
f"Customer Address: {customer_address.get('content')} has confidence: {customer_address.get('confidence')}"
)
PII-bearing data is written to a log/print sink — it stays in-process and does not leave the application, but logged PII is still a privacy concern.
Fix: Avoid logging user identifiers; redact or omit PII from log/print statements.
print(
f"Customer Address Recipient: {customer_address_recipient.get('content')} has confidence: {customer_address_recipient.get('confidence')}"
)
PII-bearing data is written to a log/print sink — it stays in-process and does not leave the application, but logged PII is still a privacy concern.
Fix: Avoid logging user identifiers; redact or omit PII from log/print statements.
print(f"Invoice Id: {invoice_id.get('content')} has confidence: {invoice_id.get('confidence')}")
PII-bearing data is written to a log/print sink — it stays in-process and does not leave the application, but logged PII is still a privacy concern.
Fix: Avoid logging user identifiers; redact or omit PII from log/print statements.
print(
f"Invoice Date: {invoice_date.get('content')} has confidence: {invoice_date.get('confidence')}"
)
PII-bearing data is written to a log/print sink — it stays in-process and does not leave the application, but logged PII is still a privacy concern.
Fix: Avoid logging user identifiers; redact or omit PII from log/print statements.
print(
f"Invoice Total: {invoice_total.get('content')} has confidence: {invoice_total.get('confidence')}"
)
PII-bearing data is written to a log/print sink — it stays in-process and does not leave the application, but logged PII is still a privacy concern.
Fix: Avoid logging user identifiers; redact or omit PII from log/print statements.
print(f"Due Date: {due_date.get('content')} has confidence: {due_date.get('confidence')}")
PII-bearing data is written to a log/print sink — it stays in-process and does not leave the application, but logged PII is still a privacy concern.
Fix: Avoid logging user identifiers; redact or omit PII from log/print statements.
print(
f"Purchase Order: {purchase_order.get('content')} has confidence: {purchase_order.get('confidence')}"
)
PII-bearing data is written to a log/print sink — it stays in-process and does not leave the application, but logged PII is still a privacy concern.
Fix: Avoid logging user identifiers; redact or omit PII from log/print statements.
print(
f"Billing Address: {billing_address.get('content')} has confidence: {billing_address.get('confidence')}"
)
PII-bearing data is written to a log/print sink — it stays in-process and does not leave the application, but logged PII is still a privacy concern.
Fix: Avoid logging user identifiers; redact or omit PII from log/print statements.
print(
f"Billing Address Recipient: {billing_address_recipient.get('content')} has confidence: {billing_address_recipient.get('confidence')}"
)
PII-bearing data is written to a log/print sink — it stays in-process and does not leave the application, but logged PII is still a privacy concern.
Fix: Avoid logging user identifiers; redact or omit PII from log/print statements.
print(
f"Shipping Address: {shipping_address.get('content')} has confidence: {shipping_address.get('confidence')}"
)
PII-bearing data is written to a log/print sink — it stays in-process and does not leave the application, but logged PII is still a privacy concern.
Fix: Avoid logging user identifiers; redact or omit PII from log/print statements.
print(
f"Shipping Address Recipient: {shipping_address_recipient.get('content')} has confidence: {shipping_address_recipient.get('confidence')}"
)
PII-bearing data is written to a log/print sink — it stays in-process and does not leave the application, but logged PII is still a privacy concern.
Fix: Avoid logging user identifiers; redact or omit PII from log/print statements.
print(f"...Item #{idx + 1}")
PII-bearing data is written to a log/print sink — it stays in-process and does not leave the application, but logged PII is still a privacy concern.
Fix: Avoid logging user identifiers; redact or omit PII from log/print statements.
print(
f"......Description: {item_description.get('content')} has confidence: {item_description.get('confidence')}"
)
PII-bearing data is written to a log/print sink — it stays in-process and does not leave the application, but logged PII is still a privacy concern.
Fix: Avoid logging user identifiers; redact or omit PII from log/print statements.
print(
f"......Quantity: {item_quantity.get('content')} has confidence: {item_quantity.get('confidence')}"
)
PII-bearing data is written to a log/print sink — it stays in-process and does not leave the application, but logged PII is still a privacy concern.
Fix: Avoid logging user identifiers; redact or omit PII from log/print statements.
print(f"......Unit: {unit.get('content')} has confidence: {unit.get('confidence')}")
PII-bearing data is written to a log/print sink — it stays in-process and does not leave the application, but logged PII is still a privacy concern.
Fix: Avoid logging user identifiers; redact or omit PII from log/print statements.
print(
f"......Unit Price: {unit_price.get('content')}{unit_price_code} has confidence: {unit_price.get('confidence')}"
)
PII-bearing data is written to a log/print sink — it stays in-process and does not leave the application, but logged PII is still a privacy concern.
Fix: Avoid logging user identifiers; redact or omit PII from log/print statements.
print(
f"......Product Code: {product_code.get('content')} has confidence: {product_code.get('confidence')}"
)
PII-bearing data is written to a log/print sink — it stays in-process and does not leave the application, but logged PII is still a privacy concern.
Fix: Avoid logging user identifiers; redact or omit PII from log/print statements.
print(
f"......Date: {item_date.get('content')} has confidence: {item_date.get('confidence')}"
)
PII-bearing data is written to a log/print sink — it stays in-process and does not leave the application, but logged PII is still a privacy concern.
Fix: Avoid logging user identifiers; redact or omit PII from log/print statements.
print(f"......Tax: {tax.get('content')} has confidence: {tax.get('confidence')}")
PII-bearing data is written to a log/print sink — it stays in-process and does not leave the application, but logged PII is still a privacy concern.
Fix: Avoid logging user identifiers; redact or omit PII from log/print statements.
print(f"......Amount: {amount.get('content')} has confidence: {amount.get('confidence')}")
PII-bearing data is written to a log/print sink — it stays in-process and does not leave the application, but logged PII is still a privacy concern.
Fix: Avoid logging user identifiers; redact or omit PII from log/print statements.
print(f"Subtotal: {subtotal.get('content')} has confidence: {subtotal.get('confidence')}")
PII-bearing data is written to a log/print sink — it stays in-process and does not leave the application, but logged PII is still a privacy concern.
Fix: Avoid logging user identifiers; redact or omit PII from log/print statements.
print(f"Total Tax: {total_tax.get('content')} has confidence: {total_tax.get('confidence')}")
PII-bearing data is written to a log/print sink — it stays in-process and does not leave the application, but logged PII is still a privacy concern.
Fix: Avoid logging user identifiers; redact or omit PII from log/print statements.
print(
f"Previous Unpaid Balance: {previous_unpaid_balance.get('content')} has confidence: {previous_unpaid_balance.get('confidence')}"
)
PII-bearing data is written to a log/print sink — it stays in-process and does not leave the application, but logged PII is still a privacy concern.
Fix: Avoid logging user identifiers; redact or omit PII from log/print statements.
print(f"Amount Due: {amount_due.get('content')} has confidence: {amount_due.get('confidence')}")
PII-bearing data is written to a log/print sink — it stays in-process and does not leave the application, but logged PII is still a privacy concern.
Fix: Avoid logging user identifiers; redact or omit PII from log/print statements.
print(
f"Service Start Date: {service_start_date.get('content')} has confidence: {service_start_date.get('confidence')}"
)
PII-bearing data is written to a log/print sink — it stays in-process and does not leave the application, but logged PII is still a privacy concern.
Fix: Avoid logging user identifiers; redact or omit PII from log/print statements.
print(
f"Service End Date: {service_end_date.get('content')} has confidence: {service_end_date.get('confidence')}"
)
PII-bearing data is written to a log/print sink — it stays in-process and does not leave the application, but logged PII is still a privacy concern.
Fix: Avoid logging user identifiers; redact or omit PII from log/print statements.
print(
f"Service Address: {service_address.get('content')} has confidence: {service_address.get('confidence')}"
)
PII-bearing data is written to a log/print sink — it stays in-process and does not leave the application, but logged PII is still a privacy concern.
Fix: Avoid logging user identifiers; redact or omit PII from log/print statements.
print(
f"Service Address Recipient: {service_address_recipient.get('content')} has confidence: {service_address_recipient.get('confidence')}"
)
PII-bearing data is written to a log/print sink — it stays in-process and does not leave the application, but logged PII is still a privacy concern.
Fix: Avoid logging user identifiers; redact or omit PII from log/print statements.
print(
f"Remittance Address: {remittance_address.get('content')} has confidence: {remittance_address.get('confidence')}"
)
PII-bearing data is written to a log/print sink — it stays in-process and does not leave the application, but logged PII is still a privacy concern.
Fix: Avoid logging user identifiers; redact or omit PII from log/print statements.
print(
f"Remittance Address Recipient: {remittance_address_recipient.get('content')} has confidence: {remittance_address_recipient.get('confidence')}"
)
PII-bearing data is written to a log/print sink — it stays in-process and does not leave the application, but logged PII is still a privacy concern.
Fix: Avoid logging user identifiers; redact or omit PII from log/print statements.
print(f"----Analyzing layout from page #{page.page_number}----")
PII-bearing data is written to a log/print sink — it stays in-process and does not leave the application, but logged PII is still a privacy concern.
Fix: Avoid logging user identifiers; redact or omit PII from log/print statements.
print(f"Page has width: {page.width} and height: {page.height}, measured with unit: {page.unit}")
PII-bearing data is written to a log/print sink — it stays in-process and does not leave the application, but logged PII is still a privacy concern.
Fix: Avoid logging user identifiers; redact or omit PII from log/print statements.
print(f"......Word '{word.content}' has a confidence of {word.confidence}")
PII-bearing data is written to a log/print sink — it stays in-process and does not leave the application, but logged PII is still a privacy concern.
Fix: Avoid logging user identifiers; redact or omit PII from log/print statements.
print(
f"...Line # {line_idx} has word count {len(words)} and text '{line.content}' "
f"within bounding polygon '{_format_polygon(line.polygon)}'"
)
PII-bearing data is written to a log/print sink — it stays in-process and does not leave the application, but logged PII is still a privacy concern.
Fix: Avoid logging user identifiers; redact or omit PII from log/print statements.
print(
f"Selection mark is '{selection_mark.state}' within bounding polygon "
f"'{_format_polygon(selection_mark.polygon)}' and has a confidence of {selection_mark.confidence}"
)
PII-bearing data is written to a log/print sink — it stays in-process and does not leave the application, but logged PII is still a privacy concern.
Fix: Avoid logging user identifiers; redact or omit PII from log/print statements.
print(f"----Detected #{len(result.paragraphs)} paragraphs in the document----")
PII-bearing data is written to a log/print sink — it stays in-process and does not leave the application, but logged PII is still a privacy concern.
Fix: Avoid logging user identifiers; redact or omit PII from log/print statements.
print(f"Found paragraph with role: '{paragraph.role}' within N/A bounding region")
PII-bearing data is written to a log/print sink — it stays in-process and does not leave the application, but logged PII is still a privacy concern.
Fix: Avoid logging user identifiers; redact or omit PII from log/print statements.
print(f"Found paragraph with role: '{paragraph.role}' within")
PII-bearing data is written to a log/print sink — it stays in-process and does not leave the application, but logged PII is still a privacy concern.
Fix: Avoid logging user identifiers; redact or omit PII from log/print statements.
print(
", ".join(
f" Page #{region.page_number}: {_format_polygon(region.polygon)} bounding region"
for region in paragraph.bounding_regions
)
)
PII-bearing data is written to a log/print sink — it stays in-process and does not leave the application, but logged PII is still a privacy concern.
Fix: Avoid logging user identifiers; redact or omit PII from log/print statements.
print(f"...with content: '{paragraph.content}'")
PII-bearing data is written to a log/print sink — it stays in-process and does not leave the application, but logged PII is still a privacy concern.
Fix: Avoid logging user identifiers; redact or omit PII from log/print statements.
print(f"...with offset: {paragraph.spans[0].offset} and length: {paragraph.spans[0].length}")
PII-bearing data is written to a log/print sink — it stays in-process and does not leave the application, but logged PII is still a privacy concern.
Fix: Avoid logging user identifiers; redact or omit PII from log/print statements.
print(f"Table # {table_idx} has {table.row_count} rows and " f"{table.column_count} columns")
PII-bearing data is written to a log/print sink — it stays in-process and does not leave the application, but logged PII is still a privacy concern.
Fix: Avoid logging user identifiers; redact or omit PII from log/print statements.
print(
f"Table # {table_idx} location on page: {region.page_number} is {_format_polygon(region.polygon)}"
)
PII-bearing data is written to a log/print sink — it stays in-process and does not leave the application, but logged PII is still a privacy concern.
Fix: Avoid logging user identifiers; redact or omit PII from log/print statements.
print(f"...Cell[{cell.row_index}][{cell.column_index}] has text '{cell.content}'")
PII-bearing data is written to a log/print sink — it stays in-process and does not leave the application, but logged PII is still a privacy concern.
Fix: Avoid logging user identifiers; redact or omit PII from log/print statements.
print(
f"...content on page {region.page_number} is within bounding polygon '{_format_polygon(region.polygon)}'"
)
PII-bearing data is written to a log/print sink — it stays in-process and does not leave the application, but logged PII is still a privacy concern.
Fix: Avoid logging user identifiers; redact or omit PII from log/print statements.
print(f"Language code: '{language.locale}' with confidence {language.confidence}")
PII-bearing data is written to a log/print sink — it stays in-process and does not leave the application, but logged PII is still a privacy concern.
Fix: Avoid logging user identifiers; redact or omit PII from log/print statements.
print(f"The document contains '{style.font_style}' font style, applied to the following text: ")
PII-bearing data is written to a log/print sink — it stays in-process and does not leave the application, but logged PII is still a privacy concern.
Fix: Avoid logging user identifiers; redact or omit PII from log/print statements.
print(f"----Analyzing document from page #{page.page_number}----")
PII-bearing data is written to a log/print sink — it stays in-process and does not leave the application, but logged PII is still a privacy concern.
Fix: Avoid logging user identifiers; redact or omit PII from log/print statements.
print(f"Page has width: {page.width} and height: {page.height}, measured with unit: {page.unit}")
PII-bearing data is written to a log/print sink — it stays in-process and does not leave the application, but logged PII is still a privacy concern.
Fix: Avoid logging user identifiers; redact or omit PII from log/print statements.
print(
f"...Line # {line_idx} has {len(words)} words and text '{line.content}' within "
f"bounding polygon '{format_polygon(line.polygon)}'"
)
PII-bearing data is written to a log/print sink — it stays in-process and does not leave the application, but logged PII is still a privacy concern.
Fix: Avoid logging user identifiers; redact or omit PII from log/print statements.
print(f"......Word '{word.content}' has a confidence of {word.confidence}")
PII-bearing data is written to a log/print sink — it stays in-process and does not leave the application, but logged PII is still a privacy concern.
Fix: Avoid logging user identifiers; redact or omit PII from log/print statements.
print(
f"...Selection mark is '{selection_mark.state}' within bounding polygon "
f"'{format_polygon(selection_mark.polygon)}' and has a confidence of {selection_mark.confidence}"
)
PII-bearing data is written to a log/print sink — it stays in-process and does not leave the application, but logged PII is still a privacy concern.
Fix: Avoid logging user identifiers; redact or omit PII from log/print statements.
print(f"----Detected #{len(result.paragraphs)} paragraphs in the document----")
PII-bearing data is written to a log/print sink — it stays in-process and does not leave the application, but logged PII is still a privacy concern.
Fix: Avoid logging user identifiers; redact or omit PII from log/print statements.
print(
f"Found paragraph with role: '{paragraph.role}' within "
f"{format_bounding_region(paragraph.bounding_regions)} bounding regions"
)
PII-bearing data is written to a log/print sink — it stays in-process and does not leave the application, but logged PII is still a privacy concern.
Fix: Avoid logging user identifiers; redact or omit PII from log/print statements.
print(f"...with content: '{paragraph.content}'")
PII-bearing data is written to a log/print sink — it stays in-process and does not leave the application, but logged PII is still a privacy concern.
Fix: Avoid logging user identifiers; redact or omit PII from log/print statements.
print(f"...with offset: {paragraph.spans[0].offset} and length: {paragraph.spans[0].length}")
PII-bearing data is written to a log/print sink — it stays in-process and does not leave the application, but logged PII is still a privacy concern.
Fix: Avoid logging user identifiers; redact or omit PII from log/print statements.
print(f"--------Analysis of receipt #{idx + 1}--------")
PII-bearing data is written to a log/print sink — it stays in-process and does not leave the application, but logged PII is still a privacy concern.
Fix: Avoid logging user identifiers; redact or omit PII from log/print statements.
print(f"Receipt type: {receipt.doc_type if receipt.doc_type else 'N/A'}")
PII-bearing data is written to a log/print sink — it stays in-process and does not leave the application, but logged PII is still a privacy concern.
Fix: Avoid logging user identifiers; redact or omit PII from log/print statements.
print(
f"Merchant Name: {merchant_name.get('valueString')} has confidence: "
f"{merchant_name.confidence}"
)
PII-bearing data is written to a log/print sink — it stays in-process and does not leave the application, but logged PII is still a privacy concern.
Fix: Avoid logging user identifiers; redact or omit PII from log/print statements.
print(
f"Transaction Date: {transaction_date.get('valueDate')} has confidence: "
f"{transaction_date.confidence}"
)
PII-bearing data is written to a log/print sink — it stays in-process and does not leave the application, but logged PII is still a privacy concern.
Fix: Avoid logging user identifiers; redact or omit PII from log/print statements.
print(f"...Item #{idx + 1}")
PII-bearing data is written to a log/print sink — it stays in-process and does not leave the application, but logged PII is still a privacy concern.
Fix: Avoid logging user identifiers; redact or omit PII from log/print statements.
print(
f"......Item Description: {item_description.get('valueString')} has confidence: "
f"{item_description.confidence}"
)
PII-bearing data is written to a log/print sink — it stays in-process and does not leave the application, but logged PII is still a privacy concern.
Fix: Avoid logging user identifiers; redact or omit PII from log/print statements.
print(
f"......Item Quantity: {item_quantity.get('valueString')} has confidence: "
f"{item_quantity.confidence}"
)
PII-bearing data is written to a log/print sink — it stays in-process and does not leave the application, but logged PII is still a privacy concern.
Fix: Avoid logging user identifiers; redact or omit PII from log/print statements.
print(
f"......Total Item Price: {_format_price(item_total_price.get('valueCurrency'))} has confidence: "
f"{item_total_price.confidence}"
)
PII-bearing data is written to a log/print sink — it stays in-process and does not leave the application, but logged PII is still a privacy concern.
Fix: Avoid logging user identifiers; redact or omit PII from log/print statements.
print(
f"Subtotal: {_format_price(subtotal.get('valueCurrency'))} has confidence: {subtotal.confidence}"
)
PII-bearing data is written to a log/print sink — it stays in-process and does not leave the application, but logged PII is still a privacy concern.
Fix: Avoid logging user identifiers; redact or omit PII from log/print statements.
print(f"Total tax: {_format_price(tax.get('valueCurrency'))} has confidence: {tax.confidence}")
PII-bearing data is written to a log/print sink — it stays in-process and does not leave the application, but logged PII is still a privacy concern.
Fix: Avoid logging user identifiers; redact or omit PII from log/print statements.
print(f"Tip: {_format_price(tip.get('valueCurrency'))} has confidence: {tip.confidence}")
PII-bearing data is written to a log/print sink — it stays in-process and does not leave the application, but logged PII is still a privacy concern.
Fix: Avoid logging user identifiers; redact or omit PII from log/print statements.
print(f"Total: {_format_price(total.get('valueCurrency'))} has confidence: {total.confidence}")
PII-bearing data is written to a log/print sink — it stays in-process and does not leave the application, but logged PII is still a privacy concern.
Fix: Avoid logging user identifiers; redact or omit PII from log/print statements.
print(f"--------Analysis of receipt #{idx + 1}--------")
PII-bearing data is written to a log/print sink — it stays in-process and does not leave the application, but logged PII is still a privacy concern.
Fix: Avoid logging user identifiers; redact or omit PII from log/print statements.
print(f"Receipt type: {receipt.doc_type if receipt.doc_type else 'N/A'}")
PII-bearing data is written to a log/print sink — it stays in-process and does not leave the application, but logged PII is still a privacy concern.
Fix: Avoid logging user identifiers; redact or omit PII from log/print statements.
print(
f"Merchant Name: {merchant_name.get('valueString')} has confidence: "
f"{merchant_name.confidence}"
)
PII-bearing data is written to a log/print sink — it stays in-process and does not leave the application, but logged PII is still a privacy concern.
Fix: Avoid logging user identifiers; redact or omit PII from log/print statements.
print(
f"Transaction Date: {transaction_date.get('valueDate')} has confidence: "
f"{transaction_date.confidence}"
)
PII-bearing data is written to a log/print sink — it stays in-process and does not leave the application, but logged PII is still a privacy concern.
Fix: Avoid logging user identifiers; redact or omit PII from log/print statements.
print(f"...Item #{idx + 1}")
PII-bearing data is written to a log/print sink — it stays in-process and does not leave the application, but logged PII is still a privacy concern.
Fix: Avoid logging user identifiers; redact or omit PII from log/print statements.
print(
f"......Item Description: {item_description.get('valueString')} has confidence: "
f"{item_description.confidence}"
)
PII-bearing data is written to a log/print sink — it stays in-process and does not leave the application, but logged PII is still a privacy concern.
Fix: Avoid logging user identifiers; redact or omit PII from log/print statements.
print(
f"......Item Quantity: {item_quantity.get('valueString')} has confidence: "
f"{item_quantity.confidence}"
)
PII-bearing data is written to a log/print sink — it stays in-process and does not leave the application, but logged PII is still a privacy concern.
Fix: Avoid logging user identifiers; redact or omit PII from log/print statements.
print(
f"......Total Item Price: {format_price(item_total_price.get('valueCurrency'))} has confidence: "
f"{item_total_price.confidence}"
)
PII-bearing data is written to a log/print sink — it stays in-process and does not leave the application, but logged PII is still a privacy concern.
Fix: Avoid logging user identifiers; redact or omit PII from log/print statements.
print(
f"Subtotal: {format_price(subtotal.get('valueCurrency'))} has confidence: {subtotal.confidence}"
)
PII-bearing data is written to a log/print sink — it stays in-process and does not leave the application, but logged PII is still a privacy concern.
Fix: Avoid logging user identifiers; redact or omit PII from log/print statements.
print(f"Total tax: {format_price(tax.get('valueCurrency'))} has confidence: {tax.confidence}")
PII-bearing data is written to a log/print sink — it stays in-process and does not leave the application, but logged PII is still a privacy concern.
Fix: Avoid logging user identifiers; redact or omit PII from log/print statements.
print(f"Tip: {format_price(tip.get('valueCurrency'))} has confidence: {tip.confidence}")
PII-bearing data is written to a log/print sink — it stays in-process and does not leave the application, but logged PII is still a privacy concern.
Fix: Avoid logging user identifiers; redact or omit PII from log/print statements.
print(f"Total: {format_price(total.get('valueCurrency'))} has confidence: {total.confidence}")
PII-bearing data is written to a log/print sink — it stays in-process and does not leave the application, but logged PII is still a privacy concern.
Fix: Avoid logging user identifiers; redact or omit PII from log/print statements.
print(f"--------Analyzing US Tax W-2 Form #{idx + 1}--------")
PII-bearing data is written to a log/print sink — it stays in-process and does not leave the application, but logged PII is still a privacy concern.
Fix: Avoid logging user identifiers; redact or omit PII from log/print statements.
print(
f"Form variant: {form_variant.get('valueString')} has confidence: " f"{form_variant.confidence}"
)
PII-bearing data is written to a log/print sink — it stays in-process and does not leave the application, but logged PII is still a privacy concern.
Fix: Avoid logging user identifiers; redact or omit PII from log/print statements.
print(f"Tax year: {tax_year.get('valueString')} has confidence: {tax_year.confidence}")
PII-bearing data is written to a log/print sink — it stays in-process and does not leave the application, but logged PII is still a privacy concern.
Fix: Avoid logging user identifiers; redact or omit PII from log/print statements.
print(f"W-2 Copy: {w2_copy.get('valueString')} has confidence: {w2_copy.confidence}")
PII-bearing data is written to a log/print sink — it stays in-process and does not leave the application, but logged PII is still a privacy concern.
Fix: Avoid logging user identifiers; redact or omit PII from log/print statements.
print(f"...Name: {employee_name.get('valueString')} has confidence: {employee_name.confidence}")
PII-bearing data is written to a log/print sink — it stays in-process and does not leave the application, but logged PII is still a privacy concern.
Fix: Avoid logging user identifiers; redact or omit PII from log/print statements.
print(f"...SSN: {employee_ssn.get('valueString')} has confidence: {employee_ssn.confidence}")
PII-bearing data is written to a log/print sink — it stays in-process and does not leave the application, but logged PII is still a privacy concern.
Fix: Avoid logging user identifiers; redact or omit PII from log/print statements.
print(f"...Address: {format_address_value(employee_address.get('valueAddress'))}")
PII-bearing data is written to a log/print sink — it stays in-process and does not leave the application, but logged PII is still a privacy concern.
Fix: Avoid logging user identifiers; redact or omit PII from log/print statements.
print(f"......has confidence: {employee_address.confidence}")
PII-bearing data is written to a log/print sink — it stays in-process and does not leave the application, but logged PII is still a privacy concern.
Fix: Avoid logging user identifiers; redact or omit PII from log/print statements.
print(f"...Zipcode: {employee_zipcode} has confidence: " f"{employee_address.confidence}")
PII-bearing data is written to a log/print sink — it stays in-process and does not leave the application, but logged PII is still a privacy concern.
Fix: Avoid logging user identifiers; redact or omit PII from log/print statements.
print(
f"Control Number: {control_number.get('valueString')} has confidence: "
f"{control_number.confidence}"
)
PII-bearing data is written to a log/print sink — it stays in-process and does not leave the application, but logged PII is still a privacy concern.
Fix: Avoid logging user identifiers; redact or omit PII from log/print statements.
print(f"...Name: {employer_name.get('valueString')} has confidence: {employer_name.confidence}")
PII-bearing data is written to a log/print sink — it stays in-process and does not leave the application, but logged PII is still a privacy concern.
Fix: Avoid logging user identifiers; redact or omit PII from log/print statements.
print(
f"...ID Number: {employer_id.get('valueString')} has confidence: {employer_id.confidence}"
)
PII-bearing data is written to a log/print sink — it stays in-process and does not leave the application, but logged PII is still a privacy concern.
Fix: Avoid logging user identifiers; redact or omit PII from log/print statements.
print(f"...Address: {format_address_value(employer_address.get('valueAddress'))}")
PII-bearing data is written to a log/print sink — it stays in-process and does not leave the application, but logged PII is still a privacy concern.
Fix: Avoid logging user identifiers; redact or omit PII from log/print statements.
print(f"\n......has confidence: {employer_address.confidence}")
PII-bearing data is written to a log/print sink — it stays in-process and does not leave the application, but logged PII is still a privacy concern.
Fix: Avoid logging user identifiers; redact or omit PII from log/print statements.
print(f"...Zipcode: {employer_zipcode} has confidence: {employer_address.confidence}")
PII-bearing data is written to a log/print sink — it stays in-process and does not leave the application, but logged PII is still a privacy concern.
Fix: Avoid logging user identifiers; redact or omit PII from log/print statements.
print(
f"Wages, tips, and other compensation: {wages_tips.get('valueNumber')} "
f"has confidence: {wages_tips.confidence}"
)
PII-bearing data is written to a log/print sink — it stays in-process and does not leave the application, but logged PII is still a privacy concern.
Fix: Avoid logging user identifiers; redact or omit PII from log/print statements.
print(
f"Federal income tax withheld: {fed_income_tax_withheld.get('valueNumber')} has "
f"confidence: {fed_income_tax_withheld.confidence}"
)
PII-bearing data is written to a log/print sink — it stays in-process and does not leave the application, but logged PII is still a privacy concern.
Fix: Avoid logging user identifiers; redact or omit PII from log/print statements.
print(
f"Social Security wages: {social_security_wages.get('valueNumber')} has confidence: "
f"{social_security_wages.confidence}"
)
PII-bearing data is written to a log/print sink — it stays in-process and does not leave the application, but logged PII is still a privacy concern.
Fix: Avoid logging user identifiers; redact or omit PII from log/print statements.
print(
f"Social Security tax withheld: {social_security_tax_withheld.get('valueNumber')} "
f"has confidence: {social_security_tax_withheld.confidence}"
)
PII-bearing data is written to a log/print sink — it stays in-process and does not leave the application, but logged PII is still a privacy concern.
Fix: Avoid logging user identifiers; redact or omit PII from log/print statements.
print(
f"Medicare wages and tips: {medicare_wages_tips.get('valueNumber')} has confidence: "
f"{medicare_wages_tips.confidence}"
)
PII-bearing data is written to a log/print sink — it stays in-process and does not leave the application, but logged PII is still a privacy concern.
Fix: Avoid logging user identifiers; redact or omit PII from log/print statements.
print(
f"Medicare tax withheld: {medicare_tax_withheld.get('valueNumber')} has confidence: "
f"{medicare_tax_withheld.confidence}"
)
PII-bearing data is written to a log/print sink — it stays in-process and does not leave the application, but logged PII is still a privacy concern.
Fix: Avoid logging user identifiers; redact or omit PII from log/print statements.
print(
f"Social Security tips: {social_security_tips.get('valueNumber')} has confidence: "
f"{social_security_tips.confidence}"
)
PII-bearing data is written to a log/print sink — it stays in-process and does not leave the application, but logged PII is still a privacy concern.
Fix: Avoid logging user identifiers; redact or omit PII from log/print statements.
print(
f"Allocated tips: {allocated_tips.get('valueNumber')} has confidence: {allocated_tips.confidence}"
)
PII-bearing data is written to a log/print sink — it stays in-process and does not leave the application, but logged PII is still a privacy concern.
Fix: Avoid logging user identifiers; redact or omit PII from log/print statements.
print(
f"Verification code: {verification_code.get('valueNumber')} has confidence: {verification_code.confidence}"
)
PII-bearing data is written to a log/print sink — it stays in-process and does not leave the application, but logged PII is still a privacy concern.
Fix: Avoid logging user identifiers; redact or omit PII from log/print statements.
print(
f"Dependent care benefits: {dependent_care_benefits.get('valueNumber')} has confidence: {dependent_care_benefits.confidence}"
)
PII-bearing data is written to a log/print sink — it stays in-process and does not leave the application, but logged PII is still a privacy concern.
Fix: Avoid logging user identifiers; redact or omit PII from log/print statements.
print(
f"Non-qualified plans: {non_qualified_plans.get('valueNumber')} has confidence: {non_qualified_plans.confidence}"
)
PII-bearing data is written to a log/print sink — it stays in-process and does not leave the application, but logged PII is still a privacy concern.
Fix: Avoid logging user identifiers; redact or omit PII from log/print statements.
print(
f"...Letter code: {letter_code.get('valueString')} has confidence: {letter_code.confidence}"
)
PII-bearing data is written to a log/print sink — it stays in-process and does not leave the application, but logged PII is still a privacy concern.
Fix: Avoid logging user identifiers; redact or omit PII from log/print statements.
print(f"...Amount: {amount.get('valueNumber')} has confidence: {amount.confidence}")
PII-bearing data is written to a log/print sink — it stays in-process and does not leave the application, but logged PII is still a privacy concern.
Fix: Avoid logging user identifiers; redact or omit PII from log/print statements.
print(
f"Is statutory employee: {is_statutory_employee.get('valueString')} has confidence: {is_statutory_employee.confidence}"
)
PII-bearing data is written to a log/print sink — it stays in-process and does not leave the application, but logged PII is still a privacy concern.
Fix: Avoid logging user identifiers; redact or omit PII from log/print statements.
print(
f"Is retirement plan: {is_retirement_plan.get('valueString')} has confidence: {is_retirement_plan.confidence}"
)
PII-bearing data is written to a log/print sink — it stays in-process and does not leave the application, but logged PII is still a privacy concern.
Fix: Avoid logging user identifiers; redact or omit PII from log/print statements.
print(
f"Is third party sick pay: {third_party_sick_pay.get('valueString')} has confidence: {third_party_sick_pay.confidence}"
)
PII-bearing data is written to a log/print sink — it stays in-process and does not leave the application, but logged PII is still a privacy concern.
Fix: Avoid logging user identifiers; redact or omit PII from log/print statements.
print(f"Other information: {other_info.get('valueString')} has confidence: {other_info.confidence}")
PII-bearing data is written to a log/print sink — it stays in-process and does not leave the application, but logged PII is still a privacy concern.
Fix: Avoid logging user identifiers; redact or omit PII from log/print statements.
print(f"...State: {state.get('valueString')} has confidence: {state.confidence}")
PII-bearing data is written to a log/print sink — it stays in-process and does not leave the application, but logged PII is still a privacy concern.
Fix: Avoid logging user identifiers; redact or omit PII from log/print statements.
print(
f"...Employer state ID number: {employer_state_id_number.get('valueString')} has "
f"confidence: {employer_state_id_number.confidence}"
)
PII-bearing data is written to a log/print sink — it stays in-process and does not leave the application, but logged PII is still a privacy concern.
Fix: Avoid logging user identifiers; redact or omit PII from log/print statements.
print(
f"...State wages, tips, etc: {state_wages_tips.get('valueNumber')} has confidence: "
f"{state_wages_tips.confidence}"
)
PII-bearing data is written to a log/print sink — it stays in-process and does not leave the application, but logged PII is still a privacy concern.
Fix: Avoid logging user identifiers; redact or omit PII from log/print statements.
print(
f"...State income tax: {state_income_tax.get('valueNumber')} has confidence: "
f"{state_income_tax.confidence}"
)
PII-bearing data is written to a log/print sink — it stays in-process and does not leave the application, but logged PII is still a privacy concern.
Fix: Avoid logging user identifiers; redact or omit PII from log/print statements.
print(
f"...Local wages, tips, etc: {local_wages_tips.get('valueNumber')} has confidence: "
f"{local_wages_tips.confidence}"
)
PII-bearing data is written to a log/print sink — it stays in-process and does not leave the application, but logged PII is still a privacy concern.
Fix: Avoid logging user identifiers; redact or omit PII from log/print statements.
print(
f"...Local income tax: {local_income_tax.get('valueNumber')} has confidence: "
f"{local_income_tax.confidence}"
)
PII-bearing data is written to a log/print sink — it stays in-process and does not leave the application, but logged PII is still a privacy concern.
Fix: Avoid logging user identifiers; redact or omit PII from log/print statements.
print(
f"...Locality name: {locality_name.get('valueString')} has confidence: "
f"{locality_name.confidence}"
)
PII-bearing data is written to a log/print sink — it stays in-process and does not leave the application, but logged PII is still a privacy concern.
Fix: Avoid logging user identifiers; redact or omit PII from log/print statements.
print(
f"Found document of type '{doc.doc_type or 'N/A'}' with a confidence of {doc.confidence} contained on "
f"the following pages: {[region.page_number for region in doc.bounding_regions]}"
)
PII-bearing data is written to a log/print sink — it stays in-process and does not leave the application, but logged PII is still a privacy concern.
Fix: Avoid logging user identifiers; redact or omit PII from log/print statements.
print(f"Model ID: {model.model_id}")
PII-bearing data is written to a log/print sink — it stays in-process and does not leave the application, but logged PII is still a privacy concern.
Fix: Avoid logging user identifiers; redact or omit PII from log/print statements.
print(f"Description: {model.description}")
PII-bearing data is written to a log/print sink — it stays in-process and does not leave the application, but logged PII is still a privacy concern.
Fix: Avoid logging user identifiers; redact or omit PII from log/print statements.
print(f"Model created on: {model.created_date_time}")
PII-bearing data is written to a log/print sink — it stays in-process and does not leave the application, but logged PII is still a privacy concern.
Fix: Avoid logging user identifiers; redact or omit PII from log/print statements.
print(f"Model expires on: {model.expiration_date_time}")
PII-bearing data is written to a log/print sink — it stays in-process and does not leave the application, but logged PII is still a privacy concern.
Fix: Avoid logging user identifiers; redact or omit PII from log/print statements.
print(f"Doc Type: '{name}' which has the following fields:")
PII-bearing data is written to a log/print sink — it stays in-process and does not leave the application, but logged PII is still a privacy concern.
Fix: Avoid logging user identifiers; redact or omit PII from log/print statements.
print(
f"Field: '{field_name}' has type '{field['type']}' and confidence score "
f"{doc_type.field_confidence[field_name]}"
)
PII-bearing data is written to a log/print sink — it stays in-process and does not leave the application, but logged PII is still a privacy concern.
Fix: Avoid logging user identifiers; redact or omit PII from log/print statements.
print(f"warning code: {warning.code}, message: {warning.message}, target of the error: {warning.target}")
PII-bearing data is written to a log/print sink — it stays in-process and does not leave the application, but logged PII is still a privacy concern.
Fix: Avoid logging user identifiers; redact or omit PII from log/print statements.
print(f"Model ID: '{model.model_id}'")
PII-bearing data is written to a log/print sink — it stays in-process and does not leave the application, but logged PII is still a privacy concern.
Fix: Avoid logging user identifiers; redact or omit PII from log/print statements.
print(f"Number of pages analyzed {len(model.pages)}")
PII-bearing data is written to a log/print sink — it stays in-process and does not leave the application, but logged PII is still a privacy concern.
Fix: Avoid logging user identifiers; redact or omit PII from log/print statements.
print(f"API version used: {model.api_version}")
PII-bearing data is written to a log/print sink — it stays in-process and does not leave the application, but logged PII is still a privacy concern.
Fix: Avoid logging user identifiers; redact or omit PII from log/print statements.
print(f"Model ID: {copied_over_model.model_id}")
PII-bearing data is written to a log/print sink — it stays in-process and does not leave the application, but logged PII is still a privacy concern.
Fix: Avoid logging user identifiers; redact or omit PII from log/print statements.
print(f"Description: {copied_over_model.description}")
PII-bearing data is written to a log/print sink — it stays in-process and does not leave the application, but logged PII is still a privacy concern.
Fix: Avoid logging user identifiers; redact or omit PII from log/print statements.
print(f"Model created on: {copied_over_model.created_date_time}")
PII-bearing data is written to a log/print sink — it stays in-process and does not leave the application, but logged PII is still a privacy concern.
Fix: Avoid logging user identifiers; redact or omit PII from log/print statements.
print(f"Model expires on: {copied_over_model.expiration_date_time}")
PII-bearing data is written to a log/print sink — it stays in-process and does not leave the application, but logged PII is still a privacy concern.
Fix: Avoid logging user identifiers; redact or omit PII from log/print statements.
print(f"Doc Type: '{name}' which has the following fields:")
PII-bearing data is written to a log/print sink — it stays in-process and does not leave the application, but logged PII is still a privacy concern.
Fix: Avoid logging user identifiers; redact or omit PII from log/print statements.
print(
f"Field: '{field_name}' has type '{field['type']}' and confidence score "
f"{doc_type.field_confidence[field_name]}"
)
PII-bearing data is written to a log/print sink — it stays in-process and does not leave the application, but logged PII is still a privacy concern.
Fix: Avoid logging user identifiers; redact or omit PII from log/print statements.
print(f"warning code: {warning.code}, message: {warning.message}, target of the error: {warning.target}")
PII-bearing data is written to a log/print sink — it stays in-process and does not leave the application, but logged PII is still a privacy concern.
Fix: Avoid logging user identifiers; redact or omit PII from log/print statements.
print(f"Built classifier with ID: {classifier.classifier_id}")
PII-bearing data is written to a log/print sink — it stays in-process and does not leave the application, but logged PII is still a privacy concern.
Fix: Avoid logging user identifiers; redact or omit PII from log/print statements.
print(f"API version used to build the classifier model: {classifier.api_version}")
PII-bearing data is written to a log/print sink — it stays in-process and does not leave the application, but logged PII is still a privacy concern.
Fix: Avoid logging user identifiers; redact or omit PII from log/print statements.
print(f"Classifier description: {classifier.description}")
PII-bearing data is written to a log/print sink — it stays in-process and does not leave the application, but logged PII is still a privacy concern.
Fix: Avoid logging user identifiers; redact or omit PII from log/print statements.
print(f"Document type: {doc_type}")
PII-bearing data is written to a log/print sink — it stays in-process and does not leave the application, but logged PII is still a privacy concern.
Fix: Avoid logging user identifiers; redact or omit PII from log/print statements.
print(f"Container source: {details.azure_blob_source.container_url}\n")
PII-bearing data is written to a log/print sink — it stays in-process and does not leave the application, but logged PII is still a privacy concern.
Fix: Avoid logging user identifiers; redact or omit PII from log/print statements.
print(f"{classifier.classifier_id} | {classifier.description}")
PII-bearing data is written to a log/print sink — it stays in-process and does not leave the application, but logged PII is still a privacy concern.
Fix: Avoid logging user identifiers; redact or omit PII from log/print statements.
print(f"\nClassifier ID: {my_classifier.classifier_id}")
PII-bearing data is written to a log/print sink — it stays in-process and does not leave the application, but logged PII is still a privacy concern.
Fix: Avoid logging user identifiers; redact or omit PII from log/print statements.
print(f"Description: {my_classifier.description}")
PII-bearing data is written to a log/print sink — it stays in-process and does not leave the application, but logged PII is still a privacy concern.
Fix: Avoid logging user identifiers; redact or omit PII from log/print statements.
print(f"Classifier created on: {my_classifier.created_date_time}")
PII-bearing data is written to a log/print sink — it stays in-process and does not leave the application, but logged PII is still a privacy concern.
Fix: Avoid logging user identifiers; redact or omit PII from log/print statements.
print(f"Classifier expires on: {my_classifier.expiration_date_time}")
PII-bearing data is written to a log/print sink — it stays in-process and does not leave the application, but logged PII is still a privacy concern.
Fix: Avoid logging user identifiers; redact or omit PII from log/print statements.
print(f"Successfully deleted classifier with ID {my_classifier.classifier_id}")
PII-bearing data is written to a log/print sink — it stays in-process and does not leave the application, but logged PII is still a privacy concern.
Fix: Avoid logging user identifiers; redact or omit PII from log/print statements.
print(f"Model ID: {model.model_id}")
PII-bearing data is written to a log/print sink — it stays in-process and does not leave the application, but logged PII is still a privacy concern.
Fix: Avoid logging user identifiers; redact or omit PII from log/print statements.
print(f"Description: {model.description}")
PII-bearing data is written to a log/print sink — it stays in-process and does not leave the application, but logged PII is still a privacy concern.
Fix: Avoid logging user identifiers; redact or omit PII from log/print statements.
print(f"Model created on: {model.created_date_time}")
PII-bearing data is written to a log/print sink — it stays in-process and does not leave the application, but logged PII is still a privacy concern.
Fix: Avoid logging user identifiers; redact or omit PII from log/print statements.
print(f"Model expires on: {model.expiration_date_time}")
PII-bearing data is written to a log/print sink — it stays in-process and does not leave the application, but logged PII is still a privacy concern.
Fix: Avoid logging user identifiers; redact or omit PII from log/print statements.
print(f"Doc Type: '{name}' built with '{doc_type.build_mode}' mode which has the following fields:")
PII-bearing data is written to a log/print sink — it stays in-process and does not leave the application, but logged PII is still a privacy concern.
Fix: Avoid logging user identifiers; redact or omit PII from log/print statements.
print(
f"Field: '{field_name}' has type '{field['type']}' and confidence score "
f"{doc_type.field_confidence[field_name]}"
)
PII-bearing data is written to a log/print sink — it stays in-process and does not leave the application, but logged PII is still a privacy concern.
Fix: Avoid logging user identifiers; redact or omit PII from log/print statements.
print(
f"Our resource has {account_details.custom_document_models.count} custom models, "
f"and we can have at most {account_details.custom_document_models.limit} custom models"
)
PII-bearing data is written to a log/print sink — it stays in-process and does not leave the application, but logged PII is still a privacy concern.
Fix: Avoid logging user identifiers; redact or omit PII from log/print statements.
print(f"{model.model_id} | {model.description}")
PII-bearing data is written to a log/print sink — it stays in-process and does not leave the application, but logged PII is still a privacy concern.
Fix: Avoid logging user identifiers; redact or omit PII from log/print statements.
print(f"\nModel ID: {my_model.model_id}")
PII-bearing data is written to a log/print sink — it stays in-process and does not leave the application, but logged PII is still a privacy concern.
Fix: Avoid logging user identifiers; redact or omit PII from log/print statements.
print(f"Description: {my_model.description}")
PII-bearing data is written to a log/print sink — it stays in-process and does not leave the application, but logged PII is still a privacy concern.
Fix: Avoid logging user identifiers; redact or omit PII from log/print statements.
print(f"Model created on: {my_model.created_date_time}")
PII-bearing data is written to a log/print sink — it stays in-process and does not leave the application, but logged PII is still a privacy concern.
Fix: Avoid logging user identifiers; redact or omit PII from log/print statements.
print(f"Model expires on: {my_model.expiration_date_time}")
PII-bearing data is written to a log/print sink — it stays in-process and does not leave the application, but logged PII is still a privacy concern.
Fix: Avoid logging user identifiers; redact or omit PII from log/print statements.
print(f"warning code: {warning.code}, message: {warning.message}, target of the error: {warning.target}")
PII-bearing data is written to a log/print sink — it stays in-process and does not leave the application, but logged PII is still a privacy concern.
Fix: Avoid logging user identifiers; redact or omit PII from log/print statements.
print(f"Successfully deleted model with ID {my_model.model_id}")
PII-bearing data is written to a log/print sink — it stays in-process and does not leave the application, but logged PII is still a privacy concern.
Fix: Avoid logging user identifiers; redact or omit PII from log/print statements.
print(
f"Our resource has {response_body['customDocumentModels']['count']} custom models, "
f"and we can have at most {response_body['customDocumentModels']['limit']} custom models."
f"The quota limit for custom neural document models is {response_body['customNeuralDocumentModelBuilds']['quota']} and the resource has"
f"used {response_body['customNeuralDocumentModelBuilds']['used']}. The resource quota will reset on {response_body['customNeuralDocumentModelBuilds']['quotaResetDateTime']}"
)
PII-bearing data is written to a log/print sink — it stays in-process and does not leave the application, but logged PII is still a privacy concern.
Fix: Avoid logging user identifiers; redact or omit PII from log/print statements.
expand_more 212 low-confidence finding(s)
low env_fs — Environment-variable access. 168 locations
low env_fs — Filesystem access. 44 locations
azure-search-documents
python dependency print(f"Retrieved: knowledge source '{knowledge_source.name}'")
PII-bearing data is written to a log/print sink — it stays in-process and does not leave the application, but logged PII is still a privacy concern.
Fix: Avoid logging user identifiers; redact or omit PII from log/print statements.
print(f"Retrieved: knowledge base '{knowledge_base.name}'")
PII-bearing data is written to a log/print sink — it stays in-process and does not leave the application, but logged PII is still a privacy concern.
Fix: Avoid logging user identifiers; redact or omit PII from log/print statements.
print(f"Retrieved: knowledge source '{knowledge_source.name}'")
PII-bearing data is written to a log/print sink — it stays in-process and does not leave the application, but logged PII is still a privacy concern.
Fix: Avoid logging user identifiers; redact or omit PII from log/print statements.
print(f"Retrieved: knowledge base '{knowledge_base.name}'")
PII-bearing data is written to a log/print sink — it stays in-process and does not leave the application, but logged PII is still a privacy concern.
Fix: Avoid logging user identifiers; redact or omit PII from log/print statements.
print(f"Document count: {document_count} (index '{index_name}')")
PII-bearing data is written to a log/print sink — it stays in-process and does not leave the application, but logged PII is still a privacy concern.
Fix: Avoid logging user identifiers; redact or omit PII from log/print statements.
print(f"Indexes ({len(names)}): {', '.join(names)}")
PII-bearing data is written to a log/print sink — it stays in-process and does not leave the application, but logged PII is still a privacy concern.
Fix: Avoid logging user identifiers; redact or omit PII from log/print statements.
print(f"Document count: {document_count} (index '{index_name}')")
PII-bearing data is written to a log/print sink — it stays in-process and does not leave the application, but logged PII is still a privacy concern.
Fix: Avoid logging user identifiers; redact or omit PII from log/print statements.
print(f"Indexes ({len(names)}): {', '.join(names)}")
PII-bearing data is written to a log/print sink — it stays in-process and does not leave the application, but logged PII is still a privacy concern.
Fix: Avoid logging user identifiers; redact or omit PII from log/print statements.
print(f"Uploaded: document 100 (succeeded={result[0].succeeded})")
PII-bearing data is written to a log/print sink — it stays in-process and does not leave the application, but logged PII is still a privacy concern.
Fix: Avoid logging user identifiers; redact or omit PII from log/print statements.
print(f"Merged: document 100 (succeeded={result[0].succeeded})")
PII-bearing data is written to a log/print sink — it stays in-process and does not leave the application, but logged PII is still a privacy concern.
Fix: Avoid logging user identifiers; redact or omit PII from log/print statements.
print(f" HotelName: {result['HotelName']}")
PII-bearing data is written to a log/print sink — it stays in-process and does not leave the application, but logged PII is still a privacy concern.
Fix: Avoid logging user identifiers; redact or omit PII from log/print statements.
print(f"Deleted: document 100 (succeeded={result[0].succeeded})")
PII-bearing data is written to a log/print sink — it stays in-process and does not leave the application, but logged PII is still a privacy concern.
Fix: Avoid logging user identifiers; redact or omit PII from log/print statements.
print(f"Merge or upload: document 100 (succeeded={result[0].succeeded})")
PII-bearing data is written to a log/print sink — it stays in-process and does not leave the application, but logged PII is still a privacy concern.
Fix: Avoid logging user identifiers; redact or omit PII from log/print statements.
print(f"Uploaded: document 100 (succeeded={result[0].succeeded})")
PII-bearing data is written to a log/print sink — it stays in-process and does not leave the application, but logged PII is still a privacy concern.
Fix: Avoid logging user identifiers; redact or omit PII from log/print statements.
print(f"Merged: document 100 (succeeded={result[0].succeeded})")
PII-bearing data is written to a log/print sink — it stays in-process and does not leave the application, but logged PII is still a privacy concern.
Fix: Avoid logging user identifiers; redact or omit PII from log/print statements.
print(f" HotelName: {result['HotelName']}")
PII-bearing data is written to a log/print sink — it stays in-process and does not leave the application, but logged PII is still a privacy concern.
Fix: Avoid logging user identifiers; redact or omit PII from log/print statements.
print(f"Deleted: document 100 (succeeded={result[0].succeeded})")
PII-bearing data is written to a log/print sink — it stays in-process and does not leave the application, but logged PII is still a privacy concern.
Fix: Avoid logging user identifiers; redact or omit PII from log/print statements.
print(f"Merge or upload: document 100 (succeeded={result[0].succeeded})")
PII-bearing data is written to a log/print sink — it stays in-process and does not leave the application, but logged PII is still a privacy concern.
Fix: Avoid logging user identifiers; redact or omit PII from log/print statements.
print(f"Created: alias '{result.name}' -> index '{index_name}'")
PII-bearing data is written to a log/print sink — it stays in-process and does not leave the application, but logged PII is still a privacy concern.
Fix: Avoid logging user identifiers; redact or omit PII from log/print statements.
print(f"Retrieved: alias '{result.name}'")
PII-bearing data is written to a log/print sink — it stays in-process and does not leave the application, but logged PII is still a privacy concern.
Fix: Avoid logging user identifiers; redact or omit PII from log/print statements.
print(f"Updated: alias '{result.name}' -> index '{new_index_name}'")
PII-bearing data is written to a log/print sink — it stays in-process and does not leave the application, but logged PII is still a privacy concern.
Fix: Avoid logging user identifiers; redact or omit PII from log/print statements.
print(f"Created: alias '{result.name}' -> index '{index_name}'")
PII-bearing data is written to a log/print sink — it stays in-process and does not leave the application, but logged PII is still a privacy concern.
Fix: Avoid logging user identifiers; redact or omit PII from log/print statements.
print(f"Retrieved: alias '{result.name}'")
PII-bearing data is written to a log/print sink — it stays in-process and does not leave the application, but logged PII is still a privacy concern.
Fix: Avoid logging user identifiers; redact or omit PII from log/print statements.
print(f"Updated: alias '{result.name}' -> index '{new_index_name}'")
PII-bearing data is written to a log/print sink — it stays in-process and does not leave the application, but logged PII is still a privacy concern.
Fix: Avoid logging user identifiers; redact or omit PII from log/print statements.
print(f" Token: {token.token}, Start: {token.start_offset}, End: {token.end_offset}")
PII-bearing data is written to a log/print sink — it stays in-process and does not leave the application, but logged PII is still a privacy concern.
Fix: Avoid logging user identifiers; redact or omit PII from log/print statements.
print(f" Token: {token.token}, Start: {token.start_offset}, End: {token.end_offset}")
PII-bearing data is written to a log/print sink — it stays in-process and does not leave the application, but logged PII is still a privacy concern.
Fix: Avoid logging user identifiers; redact or omit PII from log/print statements.
print(f"Response: {response_body}")
PII-bearing data is written to a log/print sink — it stays in-process and does not leave the application, but logged PII is still a privacy concern.
Fix: Avoid logging user identifiers; redact or omit PII from log/print statements.
print(f"Response: {response_body}")
PII-bearing data is written to a log/print sink — it stays in-process and does not leave the application, but logged PII is still a privacy concern.
Fix: Avoid logging user identifiers; redact or omit PII from log/print statements.
print(f"Created: index '{result.name}'")
PII-bearing data is written to a log/print sink — it stays in-process and does not leave the application, but logged PII is still a privacy concern.
Fix: Avoid logging user identifiers; redact or omit PII from log/print statements.
print(f"Retrieved: index '{result.name}'")
PII-bearing data is written to a log/print sink — it stays in-process and does not leave the application, but logged PII is still a privacy concern.
Fix: Avoid logging user identifiers; redact or omit PII from log/print statements.
print(f"Updated: index '{result.name}'")
PII-bearing data is written to a log/print sink — it stays in-process and does not leave the application, but logged PII is still a privacy concern.
Fix: Avoid logging user identifiers; redact or omit PII from log/print statements.
print(f" - {name}")
PII-bearing data is written to a log/print sink — it stays in-process and does not leave the application, but logged PII is still a privacy concern.
Fix: Avoid logging user identifiers; redact or omit PII from log/print statements.
print(f"Created: index '{result.name}'")
PII-bearing data is written to a log/print sink — it stays in-process and does not leave the application, but logged PII is still a privacy concern.
Fix: Avoid logging user identifiers; redact or omit PII from log/print statements.
print(f"Retrieved: index '{result.name}'")
PII-bearing data is written to a log/print sink — it stays in-process and does not leave the application, but logged PII is still a privacy concern.
Fix: Avoid logging user identifiers; redact or omit PII from log/print statements.
print(f"Updated: index '{result.name}'")
PII-bearing data is written to a log/print sink — it stays in-process and does not leave the application, but logged PII is still a privacy concern.
Fix: Avoid logging user identifiers; redact or omit PII from log/print statements.
print(f"Created: synonym map '{result.name}'")
PII-bearing data is written to a log/print sink — it stays in-process and does not leave the application, but logged PII is still a privacy concern.
Fix: Avoid logging user identifiers; redact or omit PII from log/print statements.
print(f"Created: synonym map '{result.name}'")
PII-bearing data is written to a log/print sink — it stays in-process and does not leave the application, but logged PII is still a privacy concern.
Fix: Avoid logging user identifiers; redact or omit PII from log/print statements.
print(f"Synonym maps ({len(result)}): {', '.join(names)}")
PII-bearing data is written to a log/print sink — it stays in-process and does not leave the application, but logged PII is still a privacy concern.
Fix: Avoid logging user identifiers; redact or omit PII from log/print statements.
print(f" {syn}")
PII-bearing data is written to a log/print sink — it stays in-process and does not leave the application, but logged PII is still a privacy concern.
Fix: Avoid logging user identifiers; redact or omit PII from log/print statements.
print(f"Created: synonym map '{result.name}'")
PII-bearing data is written to a log/print sink — it stays in-process and does not leave the application, but logged PII is still a privacy concern.
Fix: Avoid logging user identifiers; redact or omit PII from log/print statements.
print(f"Created: synonym map '{result.name}'")
PII-bearing data is written to a log/print sink — it stays in-process and does not leave the application, but logged PII is still a privacy concern.
Fix: Avoid logging user identifiers; redact or omit PII from log/print statements.
print(f"Synonym maps ({len(result)}): {', '.join(names)}")
PII-bearing data is written to a log/print sink — it stays in-process and does not leave the application, but logged PII is still a privacy concern.
Fix: Avoid logging user identifiers; redact or omit PII from log/print statements.
print(f" {syn}")
PII-bearing data is written to a log/print sink — it stays in-process and does not leave the application, but logged PII is still a privacy concern.
Fix: Avoid logging user identifiers; redact or omit PII from log/print statements.
print(f"Created: indexer '{result.name}'")
PII-bearing data is written to a log/print sink — it stays in-process and does not leave the application, but logged PII is still a privacy concern.
Fix: Avoid logging user identifiers; redact or omit PII from log/print statements.
print(f"Indexers ({len(result)}): {', '.join(names)}")
PII-bearing data is written to a log/print sink — it stays in-process and does not leave the application, but logged PII is still a privacy concern.
Fix: Avoid logging user identifiers; redact or omit PII from log/print statements.
print(f"Retrieved: indexer '{result.name}'")
PII-bearing data is written to a log/print sink — it stays in-process and does not leave the application, but logged PII is still a privacy concern.
Fix: Avoid logging user identifiers; redact or omit PII from log/print statements.
print(f"Status: indexer '{indexer_name}' is {status.status}")
PII-bearing data is written to a log/print sink — it stays in-process and does not leave the application, but logged PII is still a privacy concern.
Fix: Avoid logging user identifiers; redact or omit PII from log/print statements.
print(f"Created: indexer '{result.name}'")
PII-bearing data is written to a log/print sink — it stays in-process and does not leave the application, but logged PII is still a privacy concern.
Fix: Avoid logging user identifiers; redact or omit PII from log/print statements.
print(f"Indexers ({len(result)}): {', '.join(names)}")
PII-bearing data is written to a log/print sink — it stays in-process and does not leave the application, but logged PII is still a privacy concern.
Fix: Avoid logging user identifiers; redact or omit PII from log/print statements.
print(f"Retrieved: indexer '{result.name}'")
PII-bearing data is written to a log/print sink — it stays in-process and does not leave the application, but logged PII is still a privacy concern.
Fix: Avoid logging user identifiers; redact or omit PII from log/print statements.
print(f"Status: indexer '{indexer_name}' is {result.status}")
PII-bearing data is written to a log/print sink — it stays in-process and does not leave the application, but logged PII is still a privacy concern.
Fix: Avoid logging user identifiers; redact or omit PII from log/print statements.
print(f"Created: data source '{result.name}'")
PII-bearing data is written to a log/print sink — it stays in-process and does not leave the application, but logged PII is still a privacy concern.
Fix: Avoid logging user identifiers; redact or omit PII from log/print statements.
print(f"Data sources ({len(result)}): {', '.join(names)}")
PII-bearing data is written to a log/print sink — it stays in-process and does not leave the application, but logged PII is still a privacy concern.
Fix: Avoid logging user identifiers; redact or omit PII from log/print statements.
print(f"Retrieved: data source '{result.name}'")
PII-bearing data is written to a log/print sink — it stays in-process and does not leave the application, but logged PII is still a privacy concern.
Fix: Avoid logging user identifiers; redact or omit PII from log/print statements.
print(f"Created: data source '{result.name}'")
PII-bearing data is written to a log/print sink — it stays in-process and does not leave the application, but logged PII is still a privacy concern.
Fix: Avoid logging user identifiers; redact or omit PII from log/print statements.
print(f"Data sources ({len(result)}): {', '.join(names)}")
PII-bearing data is written to a log/print sink — it stays in-process and does not leave the application, but logged PII is still a privacy concern.
Fix: Avoid logging user identifiers; redact or omit PII from log/print statements.
print(f"Retrieved: data source '{result.name}'")
PII-bearing data is written to a log/print sink — it stays in-process and does not leave the application, but logged PII is still a privacy concern.
Fix: Avoid logging user identifiers; redact or omit PII from log/print statements.
print(f"Retrieved: indexer '{result.name}'")
PII-bearing data is written to a log/print sink — it stays in-process and does not leave the application, but logged PII is still a privacy concern.
Fix: Avoid logging user identifiers; redact or omit PII from log/print statements.
print(f"Scheduled: indexer every {updated_indexer.schedule.interval}")
PII-bearing data is written to a log/print sink — it stays in-process and does not leave the application, but logged PII is still a privacy concern.
Fix: Avoid logging user identifiers; redact or omit PII from log/print statements.
print(f"Status: indexer '{updated_indexer.name}' is {status.status}")
PII-bearing data is written to a log/print sink — it stays in-process and does not leave the application, but logged PII is still a privacy concern.
Fix: Avoid logging user identifiers; redact or omit PII from log/print statements.
print(f" Completion: {result['text']}")
PII-bearing data is written to a log/print sink — it stays in-process and does not leave the application, but logged PII is still a privacy concern.
Fix: Avoid logging user identifiers; redact or omit PII from log/print statements.
print(f" Completion: {result['text']}")
PII-bearing data is written to a log/print sink — it stays in-process and does not leave the application, but logged PII is still a privacy concern.
Fix: Avoid logging user identifiers; redact or omit PII from log/print statements.
print(f" {facet}")
PII-bearing data is written to a log/print sink — it stays in-process and does not leave the application, but logged PII is still a privacy concern.
Fix: Avoid logging user identifiers; redact or omit PII from log/print statements.
print(f" {facet}")
PII-bearing data is written to a log/print sink — it stays in-process and does not leave the application, but logged PII is still a privacy concern.
Fix: Avoid logging user identifiers; redact or omit PII from log/print statements.
print(f" HotelName: {result['HotelName']} (rating {result['Rating']})")
PII-bearing data is written to a log/print sink — it stays in-process and does not leave the application, but logged PII is still a privacy concern.
Fix: Avoid logging user identifiers; redact or omit PII from log/print statements.
print(f" HotelName: {result['HotelName']} (rating {result['Rating']})")
PII-bearing data is written to a log/print sink — it stays in-process and does not leave the application, but logged PII is still a privacy concern.
Fix: Avoid logging user identifiers; redact or omit PII from log/print statements.
print(f" HotelId: {result['HotelId']}")
PII-bearing data is written to a log/print sink — it stays in-process and does not leave the application, but logged PII is still a privacy concern.
Fix: Avoid logging user identifiers; redact or omit PII from log/print statements.
print(f" HotelName: {result['HotelName']}")
PII-bearing data is written to a log/print sink — it stays in-process and does not leave the application, but logged PII is still a privacy concern.
Fix: Avoid logging user identifiers; redact or omit PII from log/print statements.
print(f" HotelId: {result['HotelId']}")
PII-bearing data is written to a log/print sink — it stays in-process and does not leave the application, but logged PII is still a privacy concern.
Fix: Avoid logging user identifiers; redact or omit PII from log/print statements.
print(f" HotelName: {result['HotelName']}")
PII-bearing data is written to a log/print sink — it stays in-process and does not leave the application, but logged PII is still a privacy concern.
Fix: Avoid logging user identifiers; redact or omit PII from log/print statements.
print(f" HotelId: {result['HotelId']}")
PII-bearing data is written to a log/print sink — it stays in-process and does not leave the application, but logged PII is still a privacy concern.
Fix: Avoid logging user identifiers; redact or omit PII from log/print statements.
print(f" HotelName: {result['HotelName']}")
PII-bearing data is written to a log/print sink — it stays in-process and does not leave the application, but logged PII is still a privacy concern.
Fix: Avoid logging user identifiers; redact or omit PII from log/print statements.
print(f" HotelId: {result['HotelId']}")
PII-bearing data is written to a log/print sink — it stays in-process and does not leave the application, but logged PII is still a privacy concern.
Fix: Avoid logging user identifiers; redact or omit PII from log/print statements.
print(f" HotelName: {result['HotelName']}")
PII-bearing data is written to a log/print sink — it stays in-process and does not leave the application, but logged PII is still a privacy concern.
Fix: Avoid logging user identifiers; redact or omit PII from log/print statements.
print(f" HotelName: {result['HotelName']} (rating {result['Rating']})")
PII-bearing data is written to a log/print sink — it stays in-process and does not leave the application, but logged PII is still a privacy concern.
Fix: Avoid logging user identifiers; redact or omit PII from log/print statements.
print(f" HotelName: {result['HotelName']} (rating {result['Rating']})")
PII-bearing data is written to a log/print sink — it stays in-process and does not leave the application, but logged PII is still a privacy concern.
Fix: Avoid logging user identifiers; redact or omit PII from log/print statements.
print(f" HotelName: {result['HotelName']} (rating {result['Rating']})")
PII-bearing data is written to a log/print sink — it stays in-process and does not leave the application, but logged PII is still a privacy concern.
Fix: Avoid logging user identifiers; redact or omit PII from log/print statements.
print(f" HotelName: {result['HotelName']} (rating {result['Rating']})")
PII-bearing data is written to a log/print sink — it stays in-process and does not leave the application, but logged PII is still a privacy concern.
Fix: Avoid logging user identifiers; redact or omit PII from log/print statements.
print(f" Text: {result['text']!r}, HotelName: {hotel['HotelName']}")
PII-bearing data is written to a log/print sink — it stays in-process and does not leave the application, but logged PII is still a privacy concern.
Fix: Avoid logging user identifiers; redact or omit PII from log/print statements.
print(f" Text: {result['text']!r}, HotelName: {hotel['HotelName']}")
PII-bearing data is written to a log/print sink — it stays in-process and does not leave the application, but logged PII is still a privacy concern.
Fix: Avoid logging user identifiers; redact or omit PII from log/print statements.
print(f"Created: index '{result.name}'")
PII-bearing data is written to a log/print sink — it stays in-process and does not leave the application, but logged PII is still a privacy concern.
Fix: Avoid logging user identifiers; redact or omit PII from log/print statements.
print(f"Uploaded: {len(result)} documents to index '{index_name}'")
PII-bearing data is written to a log/print sink — it stays in-process and does not leave the application, but logged PII is still a privacy concern.
Fix: Avoid logging user identifiers; redact or omit PII from log/print statements.
print(
f" HotelId: {result['HotelId']}, HotelName: {result['HotelName']}, " f"Category: {result.get('Category')}"
)
PII-bearing data is written to a log/print sink — it stays in-process and does not leave the application, but logged PII is still a privacy concern.
Fix: Avoid logging user identifiers; redact or omit PII from log/print statements.
print(f" HotelId: {result['HotelId']}, HotelName: {result['HotelName']}, " f"Tags: {result.get('Tags')}")
PII-bearing data is written to a log/print sink — it stays in-process and does not leave the application, but logged PII is still a privacy concern.
Fix: Avoid logging user identifiers; redact or omit PII from log/print statements.
print(f" Score: {score}")
PII-bearing data is written to a log/print sink — it stays in-process and does not leave the application, but logged PII is still a privacy concern.
Fix: Avoid logging user identifiers; redact or omit PII from log/print statements.
print(f" HotelId: {result['HotelId']}")
PII-bearing data is written to a log/print sink — it stays in-process and does not leave the application, but logged PII is still a privacy concern.
Fix: Avoid logging user identifiers; redact or omit PII from log/print statements.
print(f" HotelName: {result['HotelName']}")
PII-bearing data is written to a log/print sink — it stays in-process and does not leave the application, but logged PII is still a privacy concern.
Fix: Avoid logging user identifiers; redact or omit PII from log/print statements.
print(f" Description: {result.get('Description')}")
PII-bearing data is written to a log/print sink — it stays in-process and does not leave the application, but logged PII is still a privacy concern.
Fix: Avoid logging user identifiers; redact or omit PII from log/print statements.
print(f" Category: {result.get('Category')}")
PII-bearing data is written to a log/print sink — it stays in-process and does not leave the application, but logged PII is still a privacy concern.
Fix: Avoid logging user identifiers; redact or omit PII from log/print statements.
print(f" Tags: {result.get('Tags', 'N/A')}")
PII-bearing data is written to a log/print sink — it stays in-process and does not leave the application, but logged PII is still a privacy concern.
Fix: Avoid logging user identifiers; redact or omit PII from log/print statements.
print(f"Created: index '{result.name}'")
PII-bearing data is written to a log/print sink — it stays in-process and does not leave the application, but logged PII is still a privacy concern.
Fix: Avoid logging user identifiers; redact or omit PII from log/print statements.
print(f"Uploaded: {len(result)} documents to index '{index_name}'")
PII-bearing data is written to a log/print sink — it stays in-process and does not leave the application, but logged PII is still a privacy concern.
Fix: Avoid logging user identifiers; redact or omit PII from log/print statements.
print(
f" HotelId: {result['HotelId']}, HotelName: {result['HotelName']}, "
f"Category: {result.get('Category')}"
)
PII-bearing data is written to a log/print sink — it stays in-process and does not leave the application, but logged PII is still a privacy concern.
Fix: Avoid logging user identifiers; redact or omit PII from log/print statements.
print(f" HotelId: {result['HotelId']}, HotelName: {result['HotelName']}, " f"Tags: {result.get('Tags')}")
PII-bearing data is written to a log/print sink — it stays in-process and does not leave the application, but logged PII is still a privacy concern.
Fix: Avoid logging user identifiers; redact or omit PII from log/print statements.
print(f" Score: {score}")
PII-bearing data is written to a log/print sink — it stays in-process and does not leave the application, but logged PII is still a privacy concern.
Fix: Avoid logging user identifiers; redact or omit PII from log/print statements.
print(f" HotelId: {result['HotelId']}")
PII-bearing data is written to a log/print sink — it stays in-process and does not leave the application, but logged PII is still a privacy concern.
Fix: Avoid logging user identifiers; redact or omit PII from log/print statements.
print(f" HotelName: {result['HotelName']}")
PII-bearing data is written to a log/print sink — it stays in-process and does not leave the application, but logged PII is still a privacy concern.
Fix: Avoid logging user identifiers; redact or omit PII from log/print statements.
print(f" Description: {result.get('Description')}")
PII-bearing data is written to a log/print sink — it stays in-process and does not leave the application, but logged PII is still a privacy concern.
Fix: Avoid logging user identifiers; redact or omit PII from log/print statements.
print(f" Category: {result.get('Category')}")
PII-bearing data is written to a log/print sink — it stays in-process and does not leave the application, but logged PII is still a privacy concern.
Fix: Avoid logging user identifiers; redact or omit PII from log/print statements.
print(f" Tags: {result.get('Tags', 'N/A')}")
PII-bearing data is written to a log/print sink — it stays in-process and does not leave the application, but logged PII is still a privacy concern.
Fix: Avoid logging user identifiers; redact or omit PII from log/print statements.
print(f"Document count: {response_body} (index '{index_name}')")
PII-bearing data is written to a log/print sink — it stays in-process and does not leave the application, but logged PII is still a privacy concern.
Fix: Avoid logging user identifiers; redact or omit PII from log/print statements.
print(f"Document count: {response_body} (index '{index_name}')")
PII-bearing data is written to a log/print sink — it stays in-process and does not leave the application, but logged PII is still a privacy concern.
Fix: Avoid logging user identifiers; redact or omit PII from log/print statements.
expand_more 133 low-confidence finding(s)
low env_fs — Environment-variable access. 127 locations
low env_fs — Filesystem access. 6 locations
chromadb
python dependency self.product_telemetry_client.capture(
ClientCreateCollectionEvent(
collection_uuid=str(id),
# embedding_function=embedding_function.__class__.__name__,
)
)
A telemetry/analytics SDK is used; event data is sent to a third-party collector.
Fix: Ensure user consent and a lawful basis; strip PII from event payloads.
self.product_telemetry_client.capture(
CollectionGetEvent(
collection_uuid=str(collection_id),
ids_count=ids_amount,
limit=limit if limit else 0,
include_metadata=ids_amount if "metadatas" in include else 0,
include_documents=ids_amount if "documents" in include else 0,
include_uris=ids_amount if "uris" in include else 0,
)
)
A telemetry/analytics SDK is used; event data is sent to a third-party collector.
Fix: Ensure user consent and a lawful basis; strip PII from event payloads.
self.product_telemetry_client.capture(
CollectionAddEvent(
collection_uuid=str(collection_id),
add_amount=len(ids),
with_metadata=len(ids) if metadatas is not None else 0,
with_documents=len(ids) if documents is not None else 0,
with_uris=len(ids) if uris is not None else 0,
)
)
A telemetry/analytics SDK is used; event data is sent to a third-party collector.
Fix: Ensure user consent and a lawful basis; strip PII from event payloads.
self.product_telemetry_client.capture(
CollectionUpdateEvent(
collection_uuid=str(collection_id),
update_amount=len(ids),
with_embeddings=len(embeddings) if embeddings else 0,
with_metadata=len(metadatas) if metadatas else 0,
with_documents=len(documents) if documents else 0,
with_uris=len(uris) if uris else 0,
)
)
A telemetry/analytics SDK is used; event data is sent to a third-party collector.
Fix: Ensure user consent and a lawful basis; strip PII from event payloads.
self.product_telemetry_client.capture(
CollectionQueryEvent(
collection_uuid=str(collection_id),
query_amount=query_amount,
filtered_ids_amount=filtered_ids_amount,
n_results=n_results,
with_metadata_filter=query_amount if where is not None else 0,
with_document_filter=query_amount if where_document is not None else 0,
include_metadatas=query_amount if "metadatas" in include else 0,
include_documents=query_amount if "documents" in include else 0,
include_uris=query_amount if "uris" in include else 0,
include_distances=query_amount if "distances" in include else 0,
)
)
A telemetry/analytics SDK is used; event data is sent to a third-party collector.
Fix: Ensure user consent and a lawful basis; strip PII from event payloads.
self.product_telemetry_client.capture(
CollectionDeleteEvent(
collection_uuid=str(collection_id),
delete_amount=deleted,
)
)
A telemetry/analytics SDK is used; event data is sent to a third-party collector.
Fix: Ensure user consent and a lawful basis; strip PII from event payloads.
self._product_telemetry_client.capture(
ClientCreateCollectionEvent(
collection_uuid=str(id),
# embedding_function=embedding_function.__class__.__name__,
)
)
A telemetry/analytics SDK is used; event data is sent to a third-party collector.
Fix: Ensure user consent and a lawful basis; strip PII from event payloads.
self._product_telemetry_client.capture(
CollectionAddEvent(
collection_uuid=str(collection_id),
add_amount=len(ids),
with_metadata=len(ids) if metadatas is not None else 0,
with_documents=len(ids) if documents is not None else 0,
with_uris=len(ids) if uris is not None else 0,
)
)
A telemetry/analytics SDK is used; event data is sent to a third-party collector.
Fix: Ensure user consent and a lawful basis; strip PII from event payloads.
self._product_telemetry_client.capture(
CollectionUpdateEvent(
collection_uuid=str(collection_id),
update_amount=len(ids),
with_embeddings=len(embeddings) if embeddings else 0,
with_metadata=len(metadatas) if metadatas else 0,
with_documents=len(documents) if documents else 0,
with_uris=len(uris) if uris else 0,
)
)
A telemetry/analytics SDK is used; event data is sent to a third-party collector.
Fix: Ensure user consent and a lawful basis; strip PII from event payloads.
self._product_telemetry_client.capture(
CollectionGetEvent(
collection_uuid=str(collection_id),
ids_count=ids_amount,
limit=limit if limit else 0,
include_metadata=ids_amount if "metadatas" in include else 0,
include_documents=ids_amount if "documents" in include else 0,
include_uris=ids_amount if "uris" in include else 0,
)
)
A telemetry/analytics SDK is used; event data is sent to a third-party collector.
Fix: Ensure user consent and a lawful basis; strip PII from event payloads.
self._product_telemetry_client.capture(
CollectionDeleteEvent(
collection_uuid=str(collection_id), delete_amount=deleted_count
)
)
A telemetry/analytics SDK is used; event data is sent to a third-party collector.
Fix: Ensure user consent and a lawful basis; strip PII from event payloads.
self._product_telemetry_client.capture(
CollectionQueryEvent(
collection_uuid=str(collection_id),
query_amount=query_amount,
filtered_ids_amount=ids_amount,
n_results=n_results,
with_metadata_filter=query_amount if where is not None else 0,
with_document_filter=query_amount if where_document is not None else 0,
include_metadatas=query_amount if "metadatas" in include else 0,
include_documents=query_amount if "documents" in include else 0,
include_uris=query_amount if "uris" in include else 0,
include_distances=query_amount if "distances" in include else 0,
)
)
A telemetry/analytics SDK is used; event data is sent to a third-party collector.
Fix: Ensure user consent and a lawful basis; strip PII from event payloads.
telemetry_client.capture(ClientStartEvent())
A telemetry/analytics SDK is used; event data is sent to a third-party collector.
Fix: Ensure user consent and a lawful basis; strip PII from event payloads.
from opentelemetry.trace import Span
A telemetry/analytics SDK is used; event data is sent to a third-party collector.
Fix: Ensure user consent and a lawful basis; strip PII from event payloads.
from opentelemetry.trace import Span
A telemetry/analytics SDK is used; event data is sent to a third-party collector.
Fix: Ensure user consent and a lawful basis; strip PII from event payloads.
from opentelemetry import trace
A telemetry/analytics SDK is used; event data is sent to a third-party collector.
Fix: Ensure user consent and a lawful basis; strip PII from event payloads.
telemetry_client.capture(ServerStartEvent())
A telemetry/analytics SDK is used; event data is sent to a third-party collector.
Fix: Ensure user consent and a lawful basis; strip PII from event payloads.
from opentelemetry import trace
A telemetry/analytics SDK is used; event data is sent to a third-party collector.
Fix: Ensure user consent and a lawful basis; strip PII from event payloads.
from opentelemetry.sdk.resources import SERVICE_NAME, Resource
A telemetry/analytics SDK is used; event data is sent to a third-party collector.
Fix: Ensure user consent and a lawful basis; strip PII from event payloads.
from opentelemetry.sdk.trace import TracerProvider
A telemetry/analytics SDK is used; event data is sent to a third-party collector.
Fix: Ensure user consent and a lawful basis; strip PII from event payloads.
from opentelemetry.sdk.trace.export import (
BatchSpanProcessor,
A telemetry/analytics SDK is used; event data is sent to a third-party collector.
Fix: Ensure user consent and a lawful basis; strip PII from event payloads.
from opentelemetry.exporter.otlp.proto.grpc.trace_exporter import OTLPSpanExporter
A telemetry/analytics SDK is used; event data is sent to a third-party collector.
Fix: Ensure user consent and a lawful basis; strip PII from event payloads.
from opentelemetry.instrumentation.fastapi import FastAPIInstrumentor
A telemetry/analytics SDK is used; event data is sent to a third-party collector.
Fix: Ensure user consent and a lawful basis; strip PII from event payloads.
from opentelemetry.trace import StatusCode, SpanKind
A telemetry/analytics SDK is used; event data is sent to a third-party collector.
Fix: Ensure user consent and a lawful basis; strip PII from event payloads.
expand_more 67 low-confidence finding(s)
low env_fs — Environment-variable access. 41 locations
low egress — Outbound request to a variable or assembled URL on a network client. Review what data is sent to this destination. 12 locations
low env_fs — Filesystem access. 12 locations
low egress — Hardcoded external endpoint. Review what data is sent to this destination. 2 locations
redis
python dependency from opentelemetry.metrics import Observation
A telemetry/analytics SDK is used; event data is sent to a third-party collector.
Fix: Ensure user consent and a lawful basis; strip PII from event payloads.
from opentelemetry.metrics import Meter
A telemetry/analytics SDK is used; event data is sent to a third-party collector.
Fix: Ensure user consent and a lawful basis; strip PII from event payloads.
from opentelemetry.sdk.metrics import MeterProvider
A telemetry/analytics SDK is used; event data is sent to a third-party collector.
Fix: Ensure user consent and a lawful basis; strip PII from event payloads.
from opentelemetry import metrics
A telemetry/analytics SDK is used; event data is sent to a third-party collector.
Fix: Ensure user consent and a lawful basis; strip PII from event payloads.
from opentelemetry.metrics import NoOpMeterProvider
A telemetry/analytics SDK is used; event data is sent to a third-party collector.
Fix: Ensure user consent and a lawful basis; strip PII from event payloads.
from opentelemetry.metrics import Observation
A telemetry/analytics SDK is used; event data is sent to a third-party collector.
Fix: Ensure user consent and a lawful basis; strip PII from event payloads.
from opentelemetry.metrics import Observation
A telemetry/analytics SDK is used; event data is sent to a third-party collector.
Fix: Ensure user consent and a lawful basis; strip PII from event payloads.
from opentelemetry.metrics import Observation
A telemetry/analytics SDK is used; event data is sent to a third-party collector.
Fix: Ensure user consent and a lawful basis; strip PII from event payloads.
expand_more 6 low-confidence finding(s)
low egress — Outbound request to a variable or assembled URL on a network client. Review what data is sent to this destination. 4 locations
low env_fs — Filesystem access. 2 locations
transformers
python dependency logger.debug(f"[Kubeflow] Token file not found: {token_path}")
PII-bearing data is written to a log/print sink — it stays in-process and does not leave the application, but logged PII is still a privacy concern.
Fix: Avoid logging user identifiers; redact or omit PII from log/print statements.
from opentelemetry import metrics
A telemetry/analytics SDK is used; event data is sent to a third-party collector.
Fix: Ensure user consent and a lawful basis; strip PII from event payloads.
from opentelemetry.trace import Status, StatusCode, get_tracer
A telemetry/analytics SDK is used; event data is sent to a third-party collector.
Fix: Ensure user consent and a lawful basis; strip PII from event payloads.
expand_more 387 low-confidence finding(s)
low env_fs — Filesystem access. 243 locations
low egress — Outbound request to a variable or assembled URL on a network client. Review what data is sent to this destination. 13 locations
low env_fs — Environment-variable access. 130 locations
img = Image.open(io.BytesIO(httpx.get(img, follow_redirects=True).content))
Data is sent to a hardcoded external endpoint; review what leaves the process.
Fix: Verify the destination and that only non-sensitive data is sent; pin and audit the dependency.
azure-identity
python dependency _LOGGER.info("Environment is configured for %s", self._credential.__class__.__name__)
PII-bearing data is written to a log/print sink — it stays in-process and does not leave the application, but logged PII is still a privacy concern.
Fix: Avoid logging user identifiers; redact or omit PII from log/print statements.
_LOGGER.info("Environment is configured for %s", self._credential.__class__.__name__)
PII-bearing data is written to a log/print sink — it stays in-process and does not leave the application, but logged PII is still a privacy concern.
Fix: Avoid logging user identifiers; redact or omit PII from log/print statements.
expand_more 105 low-confidence finding(s)
low env_fs — Environment-variable access. 101 locations
low env_fs — Filesystem access. 4 locations
google-cloud-storage
python dependency from opentelemetry import trace
A telemetry/analytics SDK is used; event data is sent to a third-party collector.
Fix: Ensure user consent and a lawful basis; strip PII from event payloads.
expand_more 31 low-confidence finding(s)
low env_fs — Environment-variable access. 11 locations
low env_fs — Filesystem access. 7 locations
low egress — Outbound request to a variable or assembled URL on a network client. Review what data is sent to this destination. 13 locations
APScheduler
python dependencyexpand_more 6 low-confidence finding(s)
low egress — Outbound request to a variable or assembled URL on a network client. Review what data is sent to this destination. 4 locations
low env_fs — Filesystem access. 2 locations
Brotli
python dependencyexpand_more 5 low-confidence finding(s)
low env_fs — Filesystem access. 4 locations
value = os.environ.get(key)
Reads environment variables or the filesystem — an inventory-level capability, not a leak on its own.
Fix: Usually benign; confirm any secret read here is not later sent externally.
PyJWT
python dependencyexpand_more 5 low-confidence finding(s)
with open(os.path.join(here, *parts), encoding="utf-8") as f:
Reads environment variables or the filesystem — an inventory-level capability, not a leak on its own.
Fix: Usually benign; confirm any secret read here is not later sent externally.
low env_fs — Environment-variable access. 3 locations
with urllib.request.urlopen(
r, timeout=self.timeout, context=self.ssl_context
) as response:
Data is sent to a hardcoded external endpoint; review what leaves the process.
Fix: Verify the destination and that only non-sensitive data is sent; pin and audit the dependency.
PyMySQL
python dependencyexpand_more 1 low-confidence finding(s)
with open(self.filename, "rb") as open_file:
Reads environment variables or the filesystem — an inventory-level capability, not a leak on its own.
Fix: Usually benign; confirm any secret read here is not later sent externally.
aiocache
python dependencyexpand_more 7 low-confidence finding(s)
low egress — Outbound request to a variable or assembled URL on a network client. Review what data is sent to this destination. 2 locations
low env_fs — Environment-variable access. 2 locations
low env_fs — Filesystem access. 3 locations
aiohttp
python dependencyexpand_more 28 low-confidence finding(s)
low env_fs — Environment-variable access. 8 locations
low egress — Outbound request to a variable or assembled URL on a network client. Review what data is sent to this destination. 5 locations
low egress — Hardcoded external endpoint. Review what data is sent to this destination. 6 locations
low env_fs — Filesystem access. 9 locations
alembic
python dependencyexpand_more 30 low-confidence finding(s)
low env_fs — Filesystem access. 14 locations
low env_fs — Environment-variable access. 16 locations
anthropic
python dependencyexpand_more 38 low-confidence finding(s)
return await self._client.request(self._page_cls, self._options)
Data is sent to a hardcoded external endpoint; review what leaves the process.
Fix: Verify the destination and that only non-sensitive data is sent; pin and audit the dependency.
low env_fs — Environment-variable access. 22 locations
low env_fs — Filesystem access. 15 locations
authlib
python dependencyexpand_more 17 low-confidence finding(s)
if os.getenv("AUTHLIB_INSECURE_TRANSPORT"):
Reads environment variables or the filesystem — an inventory-level capability, not a leak on its own.
Fix: Usually benign; confirm any secret read here is not later sent externally.
low egress — Outbound request to a variable or assembled URL on a network client. Review what data is sent to this destination. 16 locations
azure-storage-blob
python dependencyexpand_more 60 low-confidence finding(s)
low env_fs — Filesystem access. 29 locations
low env_fs — Environment-variable access. 31 locations
boto3
python dependencyexpand_more 4 low-confidence finding(s)
brotlicffi
python dependencyexpand_more 4 low-confidence finding(s)
low env_fs — Filesystem access. 2 locations
low env_fs — Environment-variable access. 2 locations
cryptography
python dependencyexpand_more 26 low-confidence finding(s)
low env_fs — Filesystem access. 20 locations
low env_fs — Environment-variable access. 6 locations
fake-useragent
python dependencyexpand_more 1 low-confidence finding(s)
for line in json_path.read_text().splitlines():
Reads environment variables or the filesystem — an inventory-level capability, not a leak on its own.
Fix: Usually benign; confirm any secret read here is not later sent externally.
fastapi
python dependencyexpand_more 66 low-confidence finding(s)
low env_fs — Filesystem access. 49 locations
low egress — Outbound request to a variable or assembled URL on a network client. Review what data is sent to this destination. 12 locations
low egress — Hardcoded external endpoint. Review what data is sent to this destination. 4 locations
os.environ["DYLD_FALLBACK_LIBRARY_PATH"] = "/opt/homebrew/lib"
Reads environment variables or the filesystem — an inventory-level capability, not a leak on its own.
Fix: Usually benign; confirm any secret read here is not later sent externally.
google-genai
python dependencyexpand_more 93 low-confidence finding(s)
low env_fs — Environment-variable access. 26 locations
low env_fs — Filesystem access. 17 locations
low egress — Outbound request to a variable or assembled URL on a network client. Review what data is sent to this destination. 50 locations
httpx
python dependencyexpand_more 4 low-confidence finding(s)
low env_fs — Environment-variable access. 4 locations
katex
python dependencyexpand_more 1 low-confidence finding(s)
with open(file_name, 'rb') as f:
Reads environment variables or the filesystem — an inventory-level capability, not a leak on its own.
Fix: Usually benign; confirm any secret read here is not later sent externally.
langchain
python dependencyexpand_more 4 low-confidence finding(s)
host_env = os.environ.copy()
Reads environment variables or the filesystem — an inventory-level capability, not a leak on its own.
Fix: Usually benign; confirm any secret read here is not later sent externally.
langchain-classic
python dependencyexpand_more 2 low-confidence finding(s)
return requests.request(method, url, **_kwargs, timeout=timeout)
Data is sent to a hardcoded external endpoint; review what leaves the process.
Fix: Verify the destination and that only non-sensitive data is sent; pin and audit the dependency.
value = full_path.read_bytes()
Reads environment variables or the filesystem — an inventory-level capability, not a leak on its own.
Fix: Usually benign; confirm any secret read here is not later sent externally.
langchain-text-splitters
python dependencyexpand_more 2 low-confidence finding(s)
response = client.get(url, timeout=timeout)
Data is sent to a hardcoded external endpoint; review what leaves the process.
Fix: Verify the destination and that only non-sensitive data is sent; pin and audit the dependency.
html_content = pathlib.Path(file).read_text(encoding="utf-8")
Reads environment variables or the filesystem — an inventory-level capability, not a leak on its own.
Fix: Usually benign; confirm any secret read here is not later sent externally.
loguru
python dependencyexpand_more 9 low-confidence finding(s)
low env_fs — Environment-variable access. 6 locations
low env_fs — Filesystem access. 3 locations
mcp
python dependencyexpand_more 39 low-confidence finding(s)
low env_fs — Environment-variable access. 16 locations
pkgs/python/[email protected]/examples/clients/simple-auth-client/mcp_simple_auth_client/main.py:343
pkgs/python/[email protected]/examples/clients/simple-auth-client/mcp_simple_auth_client/main.py:344
low egress — Outbound request to a variable or assembled URL on a network client. Review what data is sent to this destination. 6 locations
low env_fs — Filesystem access. 15 locations
low egress — Hardcoded external endpoint. Review what data is sent to this destination. 2 locations
openai
python dependencyexpand_more 60 low-confidence finding(s)
low env_fs — Filesystem access. 22 locations
low env_fs — Environment-variable access. 36 locations
low egress — Outbound request to a variable or assembled URL on a network client. Review what data is sent to this destination. 2 locations
opensearch-py
python dependencyexpand_more 14 low-confidence finding(s)
low env_fs — Environment-variable access. 9 locations
low egress — Outbound request to a variable or assembled URL on a network client. Review what data is sent to this destination. 3 locations
low env_fs — Filesystem access. 2 locations
psycopg
python dependencyexpand_more 9 low-confidence finding(s)
low env_fs — Environment-variable access. 7 locations
low env_fs — Filesystem access. 2 locations
pydantic
python dependencyexpand_more 9 low-confidence finding(s)
low env_fs — Filesystem access. 5 locations
python-mimeparse
python dependencyexpand_more 1 low-confidence finding(s)
with open("testdata.json") as f:
Reads environment variables or the filesystem — an inventory-level capability, not a leak on its own.
Fix: Usually benign; confirm any secret read here is not later sent externally.
python-multipart
python dependencyexpand_more 1 low-confidence finding(s)
tmp_file = open(path, "w+b")
Reads environment variables or the filesystem — an inventory-level capability, not a leak on its own.
Fix: Usually benign; confirm any secret read here is not later sent externally.
pytz
python dependencyexpand_more 6 low-confidence finding(s)
low env_fs — Environment-variable access. 2 locations
low env_fs — Filesystem access. 4 locations
requests
python dependencyexpand_more 8 low-confidence finding(s)
low env_fs — Environment-variable access. 8 locations
sentence-transformers
python dependencyexpand_more 58 low-confidence finding(s)
low env_fs — Environment-variable access. 7 locations
low env_fs — Filesystem access. 51 locations
pkgs/python/[email protected]/sentence_transformers/sentence_transformer/evaluation/nano_beir.py:353
pkgs/python/[email protected]/sentence_transformers/sentence_transformer/evaluation/nano_beir.py:358
sqlalchemy
python dependencyexpand_more 29 low-confidence finding(s)
self._pool.put(record, False)
Data is sent to a hardcoded external endpoint; review what leaves the process.
Fix: Verify the destination and that only non-sensitive data is sent; pin and audit the dependency.
low env_fs — Filesystem access. 19 locations
low env_fs — Environment-variable access. 9 locations
tiktoken
python dependencyexpand_more 16 low-confidence finding(s)
low env_fs — Environment-variable access. 5 locations
low env_fs — Filesystem access. 8 locations
low egress — Outbound request to a variable or assembled URL on a network client. Review what data is sent to this destination. 3 locations
uvicorn
python dependencyexpand_more 5 low-confidence finding(s)
low env_fs — Environment-variable access. 3 locations
low env_fs — Filesystem access. 2 locations
Skipped dependencies
Production
- @floating-ui/dom prod — dist-only: no readable source
- @sveltejs/svelte-virtual-list prod — no javascript source
- @xyflow/svelte prod — dist-only: no readable source
- codemirror-lang-hcl prod — dist-only: no readable source
- kokoro-js prod — tarball exceeds byte cap
- langchain-community prod — sdist exceeds byte cap
- accelerate prod — scan budget exceeded
- pyarrow prod — scan budget exceeded
- einops prod — scan budget exceeded
- ftfy prod — scan budget exceeded
- chardet prod — scan budget exceeded
- pypdf prod — scan budget exceeded
- fpdf2 prod — scan budget exceeded
- pymdown-extensions prod — scan budget exceeded
- docx2txt prod — scan budget exceeded
- python-pptx prod — scan budget exceeded
- msoffcrypto-tool prod — scan budget exceeded
- nltk prod — scan budget exceeded
- Markdown prod — scan budget exceeded
- beautifulsoup4 prod — scan budget exceeded
- pypandoc prod — scan budget exceeded
- pandas prod — scan budget exceeded
- openpyxl prod — scan budget exceeded
- pyxlsb prod — scan budget exceeded
- xlrd prod — scan budget exceeded
- validators prod — scan budget exceeded
- psutil prod — scan budget exceeded
- sentencepiece prod — scan budget exceeded
- soundfile prod — scan budget exceeded
- pillow prod — scan budget exceeded
- opencv-python-headless prod — scan budget exceeded
- rapidocr-onnxruntime prod — scan budget exceeded
- rank-bm25 prod — scan budget exceeded
- onnxruntime prod — scan budget exceeded
- faster-whisper prod — scan budget exceeded
- black prod — scan budget exceeded
- youtube-transcript-api prod — scan budget exceeded
- pytube prod — scan budget exceeded
- pydub prod — scan budget exceeded
- ddgs prod — scan budget exceeded
- google-api-python-client prod — scan budget exceeded
- google-auth-httplib2 prod — scan budget exceeded
- google-auth-oauthlib prod — scan budget exceeded
- googleapis-common-protos prod — scan budget exceeded
- ldap3 prod — scan budget exceeded
- psycopg2-binary prod — scan budget exceeded
- pgvector prod — scan budget exceeded
- mariadb prod — scan budget exceeded
- unstructured prod — scan budget exceeded
- pymongo prod — scan budget exceeded
- moto prod — scan budget exceeded
- gcp-storage-emulator prod — scan budget exceeded
- docker prod — scan budget exceeded
- pytest prod — scan budget exceeded
- pytest-docker prod — scan budget exceeded
- playwright prod — scan budget exceeded
- elasticsearch prod — scan budget exceeded
- qdrant-client prod — scan budget exceeded
- weaviate-client prod — scan budget exceeded
- pymilvus prod — scan budget exceeded
- pinecone prod — scan budget exceeded
- oracledb prod — scan budget exceeded
- colbert-ai prod — scan budget exceeded