rotating-file-stream
Opens a stream.Writable to a file rotated by interval and/or size. A logrotate alternative.
Supply chain provenance
Status for the latest visible version.
Without SLSA provenance there is no cryptographic link between this tarball and the public source, so a manually published version cannot be tied back to a reviewed commit.
Maintainers
Keywords
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| semgrep | semgrep:child-process-import | AI (semgrep): Documented external-command support in a mature file-rotation library; not malicious. | ai |
Versions (showing 17 of 17)
| Version | Deps | Published |
|---|---|---|
| 3.2.9 | 0 / 12 | |
| 3.2.8 | 0 / 12 | |
| 3.2.7 | 0 / 12 | |
| 3.2.6 | 0 / 12 | |
| 3.2.5 | 0 / 12 | |
| 3.2.4 | 0 / 12 | |
| 3.2.3 | 0 / 12 | |
| 3.2.2 | 0 / 11 | |
| 3.2.1 | 0 / 11 | |
| 3.2.0 | 0 / 11 | |
| 3.1.1 | 0 / 10 | |
| 3.1.0 | 0 / 10 | |
| 3.0.4 | 0 / 10 | |
| 3.0.3 | 0 / 10 | |
| 3.0.2 | 0 / 10 | |
| 3.0.1 | 0 / 10 | |
| 3.0.0 | 0 / 10 |
v3.2.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.2.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.1.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.0.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.0.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.0.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.0.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.0.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.