npmpackage.info

Gathering detailed insights and metrics for @types/write-file-atomic

Other packages similar to @types/write-file-atomic

@types/write-file-atomically

2.0.3

TypeScript definitions for write-file-atomically

@types/write-file-atomic

The repository for high quality TypeScript type definitions.

4.0.3

49,133

NOASSERTION

TypeScript

4.84 kB

24,185,380 6.9

Installations

npm install @types/write-file-atomic

Developer Guide

BETA

Typescript

Yes

Module System

N/A

Score

Supply Chain

79.5

Quality

75.7

Maintenance

100

Vulnerability

100

License

Pull Requests

Open

152

Total

60,661

Closed

9,570

Merged

50,939

Issues

Open

563

Total

8,074

Closed

7,511

Releases

0.1.450

Published on 04 Sept 2019

View all 1 releases

Contributors

9,978

View all 9,978 contributors

Languages

TypeScript

JavaScript

Shell

TypeScript (99.9%)

JavaScript (0.09%)

Shell (0.01%)

Love this project? Help keep it running — sponsor us today! 🚀

Developer

DefinitelyTyped

Download Statistics

Total Downloads

24,185,380

Last Day

324

Last Week

324

Last Month

135,015

Last Year

2,008,885

GitHub Statistics

49,133 Stars

88,671 Commits

30,298 Forks

640 Watching

5 Branches

9,978 Contributors

Maintainers

Package Meta Information

Latest Version

4.0.3

Package Id

@types/write-file-atomic@4.0.3

Unpacked Size

4.84 kB

Size

1.86 kB

File Count

Publised On

07 Nov 2023

Total Downloads

Cumulative downloads

Total Downloads

24,185,380

Last day

324

Compared to previous day

Last week

-98.9%

324

Compared to previous week

Last month

-11.7%

135,015

Compared to previous month

Last year

-15.1%

2,008,885

Compared to previous year

Daily Downloads

Weekly Downloads

Monthly Downloads

Yearly Downloads

Dependencies

@types/node

Versions

Installation

npm install --save @types/write-file-atomic

Summary

This package contains type definitions for write-file-atomic (https://github.com/npm/write-file-atomic).

Details

Files were exported from https://github.com/DefinitelyTyped/DefinitelyTyped/tree/master/types/write-file-atomic.

index.d.ts

1/// <reference types="node" />
2
3export = writeFile;
4
5declare function writeFile(
6    filename: string,
7    data: string | Buffer,
8    options: writeFile.Options | BufferEncoding,
9    callback: (error?: Error) => void,
10): void;
11declare function writeFile(filename: string, data: string | Buffer, callback: (error?: Error) => void): void;
12declare function writeFile(
13    filename: string,
14    data: string | Buffer,
15    options?: writeFile.Options | BufferEncoding,
16): Promise<void>;
17
18declare namespace writeFile {
19    function sync(filename: string, data: string | Buffer, options?: Options | BufferEncoding): void;
20
21    interface Options {
22        chown?:
23            | {
24                uid: number;
25                gid: number;
26            }
27            | undefined;
28        /**
29         * @default 'utf8'
30         */
31        encoding?: BufferEncoding | undefined;
32        fsync?: boolean | undefined;
33        mode?: number | undefined;
34        tmpfileCreated?: ((tmpfile: string) => void) | undefined;
35    }
36}
37

Additional Details

Last updated: Tue, 07 Nov 2023 15:11:36 GMT
Dependencies: @types/node

Credits

These definitions were written by BendingBender, and Piotr Błażejewicz.

No vulnerabilities found.

10

Maintained

Determines if the project is "actively maintained".

10

Security-Policy

Determines if the project has published a security policy.

10

Dangerous-Workflow

Determines if the project's GitHub Action workflows avoid dangerous patterns.

10

Vulnerabilities

Determines if the project has open, known unfixed vulnerabilities.

10

Binary-Artifacts

Determines if the project has generated executable (binary) artifacts in the source repository.

9

License

Determines if the project has defined a license.

8

Code-Review

Determines if the project requires human code review before pull requests (aka merge requests) are merged.

8

Pinned-Dependencies

Determines if the project has declared and pinned the dependencies of its build process.

0

CII-Best-Practices

Determines if the project has an OpenSSF (formerly CII) Best Practices Badge.

0

Token-Permissions

Determines if the project's workflows follow the principle of least privilege.

0

SAST

Determines if the project uses static code analysis.

0

Fuzzing

Determines if the project uses fuzzing.

Score

6.9

/10

Last Scanned on 2025-02-03

The Open Source Security Foundation is a cross-industry collaboration to improve the security of open source software (OSS). The Scorecard provides security health metrics for open source projects.

Learn More