@editorjs/quote
Supply chain provenance
Status for the latest visible version.
Without SLSA provenance there is no cryptographic link between this tarball and the public source, so a manually published version cannot be tied back to a reviewed commit.
Maintainers
Keywords
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| phantom-deps | phantom-dep:@editorjs/dom | AI (phantom-deps): Same-org dep bundled via vite build; not directly imported in source but legitimately declared. | ai | |
| phantom-deps | phantom-dep:@codexteam/icons | AI (phantom-deps): Icons dep referenced in config/build tooling; stable false positive for this package. | ai |
Versions (showing 7 of 7)
| Version | Deps | Published |
|---|---|---|
| 2.7.6 | 2 / 7 | |
| 2.7.5 | 2 / 7 | |
| 2.7.4 | 2 / 5 | |
| 2.7.3 | 2 / 5 | |
| 2.7.2 | 2 / 5 | |
| 2.7.1 | 2 / 5 | |
| 2.7.0 | 2 / 5 |
v2.7.5
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.7.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.7.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.7.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.7.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.7.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.