← Home

@bevry/file

npm Repository Homepage

Helpers for reading, writing, deleting, and accessing a file.

10
Versions
Artistic-2.0
License
No
Install Scripts
Missing
Provenance

Supply chain provenance

Status for the latest visible version.

No SLSA provenance npm registry signatures gitHead linked

Without SLSA provenance there is no cryptographic link between this tarball and the public source — the axios compromise (March 2026) relied on exactly this gap.

Maintainers

bevryme

Keywords

accessaccessiblebrowserecmascriptes2016es2019es2022es5filefrommodulenodereadreadabletotypedtypestypescriptwritablewrite

Accepted risks

Findings the reviewer chose to accept rather than block on.

SourceRuleReasonAccepted byWhen
typosquat typosquat.levenshtein:vite AI (typosquat): @bevry/file is a scoped utility package from the established bevry org; the name describes its purpose and has no relation to vite. Levenshtein match is coincidental. ai
semgrep semgrep:child-process-import AI (semgrep): This is a file utility package; child_process import is consistent with file system operations. No evidence of malicious usage — this is a generic import detection rule firing on legitimate code. ai

Versions (showing 10 of 10)

Version Deps Published
2.3.0 2 / 17
2.2.0 2 / 17
2.1.0 2 / 17
2.0.0 2 / 17
1.5.0 0 / 17
1.4.0 0 / 18
1.3.0 0 / 18
1.2.0 0 / 17
1.1.0 0 / 17
1.0.0 0 / 17

v2.3.0

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v2.2.0

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v2.1.0

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v2.0.0

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v1.5.0

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v1.4.0

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v1.3.0

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v1.2.0

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v1.1.0

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v1.0.0

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.