@milkdown/plugin-emoji
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 |
|---|---|---|---|---|
| phantom-deps | phantom-dep:tslib | AI (phantom-deps): tslib is a known implicit runtime dep for TypeScript-compiled packages; stable FP for this package. | ai | |
| phantom-deps | phantom-dep:unist-util-visit | AI (phantom-deps): Referenced in config files per analyzer note; stable FP for this monorepo package. | ai | |
| phantom-deps | phantom-dep:@milkdown/core | AI (phantom-deps): Same-org peer dependency in a monorepo; stable false positive for this package. | ai | |
| dependencies | unvetted-dep:twemoji | AI (dependencies): twemoji is a well-known emoji rendering library; expected dependency for an emoji plugin. | ai |
Versions (showing 47 of 47)
| Version | Deps | Published |
|---|---|---|
| 7.21.3 | 11 / 1 | |
| 7.21.2 | 11 / 1 | |
| 7.21.1 | 11 / 1 | |
| 7.21.0 | 11 / 1 | |
| 7.20.0 | 11 / 1 | |
| 7.19.2 | 11 / 1 | |
| 7.19.1 | 11 / 1 | |
| 7.19.0 | 11 / 1 | |
| 7.18.0 | 11 / 1 | |
| 7.17.3 | 11 / 1 | |
| 7.17.2 | 11 / 1 | |
| 7.17.1 | 11 / 1 | |
| 7.17.0 | 11 / 1 | |
| 7.16.0 | 11 / 1 | |
| 7.15.5 | 13 / 1 | |
| 7.15.4 | 13 / 1 | |
| 7.15.3 | 13 / 1 | |
| 7.15.2 | 13 / 1 | |
| 7.15.1 | 13 / 1 | |
| 7.15.0 | 13 / 1 | |
| 7.14.0 | 12 / 0 | |
| 7.13.2 | 12 / 0 | |
| 7.13.1 | 12 / 0 | |
| 7.13.0 | 12 / 0 | |
| 7.12.1 | 12 / 0 | |
| 7.12.0 | 12 / 0 | |
| 7.11.1 | 12 / 0 | |
| 7.11.0 | 12 / 0 | |
| 7.10.5 | 12 / 0 | |
| 7.10.4 | 12 / 0 | |
| 7.10.3 | 12 / 0 | |
| 7.10.2 | 12 / 0 | |
| 7.10.1 | 12 / 0 | |
| 7.10.0 | 12 / 0 | |
| 7.9.1 | 12 / 0 | |
| 7.9.0 | 12 / 0 | |
| 7.8.0 | 8 / 4 | |
| 7.7.0 | 8 / 4 | |
| 7.6.4 | 8 / 4 | |
| 7.6.3 | 8 / 4 | |
| 7.6.2 | 8 / 4 | |
| 7.6.1 | 8 / 4 | |
| 7.6.0 | 8 / 4 | |
| 7.5.9 | 8 / 4 | |
| 7.5.8 | 8 / 4 | |
| 7.5.0 | 8 / 4 | |
| 7.4.0 | 8 / 4 |
v7.21.3
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v7.21.2
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v7.21.1
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v7.21.0
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v7.19.1
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v7.19.0
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v7.18.0
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v7.17.3
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v7.17.2
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v7.16.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v7.15.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v7.15.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v7.15.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v7.15.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v7.15.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v7.14.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v7.13.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v7.13.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v7.13.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v7.12.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v7.12.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v7.11.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v7.11.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v7.10.5
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v7.10.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v7.10.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v7.10.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v7.10.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v7.10.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v7.9.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v7.9.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v7.8.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v7.7.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v7.6.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v7.6.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v7.6.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v7.6.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v7.6.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v7.5.9
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v7.5.8
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v7.5.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v7.4.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.