get-fn-name — Greenflagged

Get function name with strictness and correctness in mind. Also works for arrow functions and getting correct name of bounded functions. Powered by [fn-name][].

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

tunnckocore

Keywords

fnfn-namefnsfuncfunctionfunction-namegetget-function-nameget-fn-namename

Accepted risks

Findings the reviewer chose to accept rather than block on.

Source	Rule	Reason	Accepted by	When
npm-metadata	suspicious-initial-version	AI (npm-metadata): Package is 10+ years old from a well-established publisher; 0.0.0 reflects early-era npm versioning conventions, not malicious intent.	ai	2026/04/24
email-domain	unclaimed-email:tunnckocore	AI (email-domain): Package is 10+ years old with a well-established publisher track record (319 approved packages). The unclaimed domain is a legacy artifact, not an active threat vector for this package.	ai	2026/04/23

Versions (showing 2 of 2)

Version	Deps	Published
1.0.0	1 / 2	2016-03-03
0.0.0	1 / 2	2016-03-03

v1.0.0

2 findings

HIGH Unclaimed maintainer email domain: tunnckocore email-domain

Maintainer email '@tunnckoCore' uses domain 'tunnckocore' which has no DNS records. An attacker could register this domain to hijack the maintainer identity.

LOW No provenance attestation provenance

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

v0.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.