write-file-atomic
Write files in an atomic fashion w/configurable ownership
Supply chain provenance
Status for the latest visible version.
Maintainers
Keywords
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| provenance | no-provenance | AI (provenance): Legacy package predates Sigstore provenance; no code-level risk from missing attestation. | ai |
Versions (showing 35 of 35)
| Version | Deps | Published |
|---|---|---|
| 8.0.0 | 1 / 3 | |
| 7.0.1 | 1 / 3 | |
| 7.0.0 | 2 / 3 | |
| 6.0.0 | 2 / 3 | |
| 5.0.1 | 2 / 3 | |
| 5.0.0 | 2 / 5 | |
| 4.0.2 | 2 / 5 | |
| 4.0.1 | 2 / 4 | |
| 4.0.0 | 4 / 4 | |
| 3.0.3 | 4 / 5 | |
| 3.0.2 | 4 / 5 | |
| 3.0.1 | 4 / 5 | |
| 3.0.0 | 4 / 5 | |
| 2.4.3 | 3 / 5 | |
| 2.4.2 | 3 / 5 | |
| 2.4.1 | 3 / 5 | |
| 2.4.0 | 3 / 5 | |
| 2.3.0 | 3 / 5 | |
| 2.1.0 | 3 / 5 | |
| 2.0.0 | 3 / 5 | |
| 1.3.4 | 3 / 5 | |
| 1.3.3 | 3 / 5 | |
| 1.3.2 | 3 / 5 | |
| 1.3.1 | 3 / 5 | |
| 1.3.0 | 3 / 5 | |
| 1.2.0 | 3 / 4 | |
| 1.1.4 | 3 / 3 | |
| 1.1.3 | 2 / 2 | |
| 1.1.2 | 2 / 2 | |
| 1.1.1 | 2 / 2 | |
| 1.1.0 | 2 / 2 | |
| 1.0.3 | 1 / 2 | |
| 1.0.2 | 1 / 2 | |
| 1.0.1 | 1 / 2 | |
| 1.0.0 | 1 / 2 |
v8.0.0
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v7.0.0
2 findingsThis version was published by a different npm account than previous versions on 2025-10-22. This could indicate a legitimate maintainer transition or an account compromise.
Published via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v6.0.0
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v2.4.1
2 findingsMaintainer email '[email protected]' uses domain 'aoaioxxysz.net' which has no DNS records. An attacker could register this domain to hijack the maintainer identity.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.