try-catch-callback
try/catch block with a callback, used in [try-catch-core][]. Use it when you don't care about asyncness so much and don't want guarantees. If you care use [try-catch-core][].
Supply chain provenance
Status for the latest visible version.
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
Keywords
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| email-domain | unclaimed-email:tunnckocore | AI (email-domain): tunnckocore uses a social handle as email alias, not a real domain. Publisher has 326 approved packages and 4195-day history; domain hijack risk is theoretical and low for this established maintainer. | ai | |
| publish-pattern | new-deps-added | AI (publish-pattern): extend-shallow is a well-known, legitimate npm utility package. Its addition is consistent with the package's purpose and poses no supply chain risk. | ai |
Versions (showing 11 of 11)
| Version | Deps | Published |
|---|---|---|
| 2.0.2 | 1 / 8 | |
| 2.0.1 | 0 / 8 | |
| 2.0.0 | 0 / 8 | |
| 1.1.2 | 0 / 8 | |
| 1.1.1 | 0 / 8 | |
| 1.1.0 | 0 / 8 | |
| 1.0.2 | 0 / 8 | |
| 1.0.1 | 0 / 8 | |
| 1.0.0 | 0 / 8 | |
| 0.1.0 | 0 / 8 | |
| 0.0.0 | 0 / 8 |
v2.0.2
2 findingsMaintainer email '@tunnckoCore' uses domain 'tunnckocore' 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.
v2.0.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.0.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.1.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.1.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.1.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.