@kerebron/extension-menu
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
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| phantom-deps | phantom-dep:prosemirror-view | AI (phantom-deps): dnt-generated build, prosemirror is core dep of editor ecosystem | ai | |
| phantom-deps | phantom-dep:prosemirror-model | AI (phantom-deps): dnt-generated build, prosemirror is core dep of editor ecosystem | ai | |
| phantom-deps | phantom-dep:prosemirror-state | AI (phantom-deps): dnt-generated build, prosemirror is core dep of editor ecosystem | ai | |
| phantom-deps | phantom-dep:@kerebron/editor | AI (phantom-deps): same-org monorepo dependency | ai | |
| semgrep | semgrep:api-obfuscation-reflect | AI (semgrep): dnt-generated import-meta polyfill boilerplate, not real obfuscation. | ai | |
| publish-pattern | new-deps-added | AI (publish-pattern): @deno/shim-deno is standard dnt-generated build dependency, not a foreign injection. | ai | |
| source-diff | large-new-source-files | AI (source-diff): New files are dnt-generated shim/esm output, consistent with build tooling. | ai |
Versions (showing 51 of 83)
| Version | Deps | Published |
|---|---|---|
| 0.8.6 | 4 / 1 | |
| 0.8.5 | 4 / 1 | |
| 0.8.4 | 4 / 1 | |
| 0.8.3 | 4 / 1 | |
| 0.8.2 | 4 / 1 | |
| 0.8.1 | 4 / 1 | |
| 0.7.9 | 4 / 1 | |
| 0.7.8 | 4 / 1 | |
| 0.7.7 | 4 / 1 | |
| 0.7.6 | 4 / 1 | |
| 0.7.5 | 4 / 1 | |
| 0.7.4 | 4 / 1 | |
| 0.7.3 | 4 / 1 | |
| 0.7.2 | 4 / 1 | |
| 0.7.1 | 4 / 1 | |
| 0.7.0 | 4 / 1 | |
| 0.6.7 | 4 / 1 | |
| 0.6.6 | 4 / 1 | |
| 0.6.5 | 4 / 1 | |
| 0.6.4 | 4 / 1 | |
| 0.6.3 | 4 / 1 | |
| 0.6.2 | 4 / 1 | |
| 0.6.1 | 4 / 1 | |
| 0.6.0 | 4 / 1 | |
| 0.5.5 | 4 / 1 | |
| 0.5.4 | 4 / 1 | |
| 0.5.3 | 4 / 1 | |
| 0.5.2 | 4 / 1 | |
| 0.5.1 | 4 / 1 | |
| 0.5.0 | 4 / 1 | |
| 0.4.31 | 4 / 1 | |
| 0.4.30 | 4 / 1 | |
| 0.4.29 | 4 / 1 | |
| 0.4.28 | 4 / 1 | |
| 0.4.27 | 4 / 1 | |
| 0.4.26 | 4 / 1 | |
| 0.4.25 | 4 / 1 | |
| 0.4.24 | 4 / 1 | |
| 0.4.23 | 4 / 1 | |
| 0.4.22 | 4 / 1 | |
| 0.4.21 | 4 / 1 | |
| 0.4.20 | 4 / 1 | |
| 0.4.19 | 4 / 1 | |
| 0.4.18 | 4 / 1 | |
| 0.4.17 | 4 / 1 | |
| 0.4.16 | 4 / 1 | |
| 0.4.15 | 4 / 1 | |
| 0.4.14 | 4 / 1 | |
| 0.4.13 | 4 / 1 | |
| 0.4.12 | 4 / 1 | |
| 0.4.11 | 4 / 1 |
v0.8.6
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.8.5
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.8.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.8.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.8.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.8.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.7.9
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.7.8
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.7.7
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.7.6
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.7.5
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.7.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.7.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.7.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.7.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.7.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.6.7
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.6.6
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.6.5
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.6.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.6.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.6.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.6.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.6.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.5.5
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.5.4
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.5.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.5.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.5.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.5.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.4.31
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.4.30
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.4.29
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.4.28
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.4.27
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.4.26
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.4.25
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.4.24
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.4.23
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.4.22
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.4.21
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.4.20
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.4.19
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.4.18
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.4.17
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.4.16
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.4.15
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.4.14
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.4.13
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.4.12
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.4.11
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.