node-emoji
Friendly emoji lookups and parsing utilities for Node.js. 💖
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 |
|---|---|---|---|---|
| publish-pattern | new-deps-added | AI (publish-pattern): All 5 new deps (sindresorhus/is, char-regex, emojilib, skin-tone, tsup) are reputable packages consistent with the v2 rewrite. No suspicious or unknown packages. | ai | |
| maintainer-change | maintainer-added | AI (maintainer-change): charpeni is a known contributor to the node-emoji v2 rewrite; addition is consistent with legitimate project handoff/collaboration by original author omnidan. | ai | |
| source-diff | source-size-dropped | AI (source-diff): Size drop from 123KB to 28KB is explained by moving bundled emoji data into the emojilib dependency; not a stub/redirect. | ai | |
| source-diff | large-new-source-files | AI (source-diff): 29 new files reflect the v2 major rewrite restructuring the codebase; not indicative of injected code given the legitimate refactor context. | ai | |
| dependencies | unvetted-dep:tsup | AI (dependencies): tsup is a well-known ESM/CJS bundler used legitimately as a build tool here; phantom-dep finding confirms it is not imported at runtime, only used in build scripts. | ai | |
| provenance | publisher-changed | AI (provenance): Publisher change from omnidan to charpeni in 2019 is a documented, legitimate maintainer transition. charpeni has a strong track record (22 approved packages) and the package content is unchanged. | ai | |
| provenance | no-provenance | AI (provenance): node-emoji is a well-established, legitimate package; lack of provenance is common and not a risk signal here. | ai | |
| phantom-deps | phantom-dep:tsup | AI (phantom-deps): tsup is a build tool mistakenly placed in dependencies instead of devDependencies; it's used only in build scripts, not a security concern for this package. | ai | |
| dependencies | unvetted-dep:emojilib | AI (dependencies): emojilib is a well-known emoji data library; its use here is expected and appropriate for node-emoji's core functionality. | ai | |
| dependencies | unvetted-dep:@sindresorhus/is | AI (dependencies): @sindresorhus/is is a widely-used type-checking utility by a trusted author; no security concerns. | ai | |
| dependencies | unvetted-dep:char-regex | AI (dependencies): char-regex is a well-known utility for Unicode character regex; legitimate and expected dependency for emoji parsing. | ai | |
| dependencies | unvetted-dep:skin-tone | AI (dependencies): skin-tone is a small, well-known utility by sindresorhus for modifying emoji skin tones; legitimate dependency for this package. | ai |
Versions (showing 32 of 32)
| Version | Deps | Published |
|---|---|---|
| 2.2.0 | 4 / 38 | |
| 2.1.3 | 4 / 38 | |
| 2.1.2 | 4 / 38 | |
| 2.1.1 | 4 / 38 | |
| 2.1.0 | 4 / 6 | |
| 2.0.2 | 5 / 2 | |
| 2.0.1 | 5 / 2 | |
| 2.0.0 | 5 / 2 | |
| 1.11.0 | 1 / 3 | |
| 1.10.0 | 1 / 3 | |
| 1.9.0 | 1 / 3 | |
| 1.8.1 | 1 / 3 | |
| 1.8.0 | 1 / 3 | |
| 1.7.0 | 2 / 3 | |
| 1.6.1 | 1 / 3 | |
| 1.6.0 | 2 / 3 | |
| 1.5.1 | 1 / 3 | |
| 1.5.0 | 1 / 3 | |
| 1.4.3 | 1 / 3 | |
| 1.4.2 | 1 / 3 | |
| 1.4.1 | 1 / 2 | |
| 1.4.0 | 1 / 2 | |
| 1.3.1 | 1 / 2 | |
| 1.3.0 | 1 / 2 | |
| 1.2.1 | 0 / 2 | |
| 1.1.1 | 0 / 2 | |
| 1.1.0 | 0 / 2 | |
| 1.0.4 | 0 / 2 | |
| 1.0.3 | 0 / 2 | |
| 1.0.2 | 0 / 2 | |
| 1.0.1 | 0 / 2 | |
| 0.1.0 | 0 / 1 |
v2.1.3
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v2.1.2
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v2.1.1
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v2.1.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.0.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.0.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.0.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.11.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.10.0
2 findingsThis version was published by a different npm account than previous versions on 2019-02-15. This could indicate a legitimate maintainer transition or an account compromise.
[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.9.0
2 findingsThis version was published by a different npm account than previous versions on 2019-02-15. This could indicate a legitimate maintainer transition or an account compromise.
[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.8.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.8.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.7.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.6.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.6.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.5.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.5.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.4.3
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.4.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.4.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.4.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.3.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.3.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.2.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.1.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.1.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.4
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.3
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.1.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.