daemon — Greenflagged

Add-on for creating *nix daemons

Supply chain provenance

Status for the latest visible version.

No SLSA provenance npm registry signatures No source commit

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

indexzeroavianflushtylman

Accepted risks

Findings the reviewer chose to accept rather than block on.

Source	Rule	Reason	Accepted by	When
provenance	no-provenance	AI (provenance): Package is 15+ years old; provenance attestation did not exist when it was published. No concern for this package.	ai	2026/04/24
install-scripts	install-script:preinstall	AI (install-scripts): This is a native C addon; preinstall runs 'bash ./install' to compile the platform-specific daemon.node binary. Standard pattern for native bindings, stable across versions.	ai	2026/04/24
semgrep	semgrep:dynamic-require	AI (semgrep): Dynamic require loads version-specific precompiled native binary (daemon.<node_version>). Standard native addon loading pattern, not arbitrary code execution.	ai	2026/04/24
semgrep	semgrep:child-process-import	AI (semgrep): daemon is a Unix daemonizer; child_process is its core mechanism for spawning daemonized processes. Expected and legitimate for this package.	ai	2026/04/24
semgrep	semgrep:child-process-spawn	AI (semgrep): spawn(process.execPath, ...) is the documented daemonization mechanism — spawning the same Node binary with a user script. Not malicious.	ai	2026/04/24
provenance	publisher-changed	AI (provenance): Change from avianflu to shtylman (the listed author) occurred in 2013; legitimate long-standing maintainer transition, not a recent compromise.	ai	2026/04/24

Versions (showing 7 of 7)

Version	Deps	Published
1.1.0	0 / 2	2013-04-02
1.0.0	0 / 2	2013-03-14
0.5.1	0 / 1	2012-05-17
0.5.0	0 / 1	2012-05-11
0.3.2	0 / 0	2011-10-09
0.3.0	0 / 0	2011-02-11
0.1.0	0 / 0	2011-02-11

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

2 findings

HIGH Publisher changed: avianflu → shtylman (on 2013-03-14) provenance

This version was published by a different npm account than previous versions on 2013-03-14. This could indicate a legitimate maintainer transition or an account compromise.

LOW No provenance attestation provenance

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

v0.5.1

1 finding

LOW No provenance attestation provenance

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

v0.5.0

3 findings

HIGH Package has 'preinstall' script install-scripts

Script: bash ./install

LOW No provenance attestation provenance

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

INFO Publisher changed: indexzero → avianflu (on 2012-05-11) provenance

[Accepted risk] This version was published by a different npm account than previous versions on 2012-05-11. This could indicate a legitimate maintainer transition or an account compromise.