What is read_write_at?

48/100
Trust Score (D)
⚠️ Use Caution

read_write_at is a crates that Abstraction over a file or block device that can be read/written with offset.. It has a Nerq Trust Score of 48/100 (D). 0 GitHub stars. Published by Unknown. Last analyzed October 2026.

Why This Score

Trust & Safety Overview

48
TRUST SCORE
D
GRADE
0
STARS
0
DOWNLOADS

What read_write_at Does

read_write_at is a crates in the crates category. Abstraction over a file or block device that can be read/written with offset.. It is published by Unknown and has no specified license. With 0 GitHub stars and 0 downloads, it has a small community of users and contributors.

Who Should Use read_write_at

read_write_at is recommended only for experimental use. Consider alternatives with higher trust scores for production systems.

Details

AuthorUnknown
Categorycrates
LicenseNot specified
Typecrates
SourceView on GitHub
Security Score0/100
Activity Score0/100

How to Get Started

Check the trust score before installing:

curl nerq.ai/v1/preflight?target=read-write-at

Setup guide · Full safety report · Production review · Is it safe?

Frequently Asked Questions

What is read_write_at used for?
read_write_at is a crates tool. Abstraction over a file or block device that can be read/written with offset..
Is read_write_at free?
License: Check project page. read_write_at has 0 GitHub stars.
Is read_write_at safe?
read_write_at has a Nerq Trust Score of 48/100 (D). Evaluate carefully.
What are alternatives to read_write_at?
Top alternatives: . See full comparison.

Last updated October 2026. Trust scores based on automated analysis of public data.

We use cookies for analytics and caching. Privacy Policy