@intlayer/editor
Provides the utilities to interface the application with the Intlayer editor and manipulate dictionaries
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 |
|---|---|---|---|---|
| provenance | missing-githead | AI (provenance): Publish tooling changed to bun; missing gitHead is expected and consistent with the new publish scripts added in this version. | ai | |
| provenance | no-provenance | AI (provenance): Established intlayer monorepo package; provenance attestation not historically used by this publisher. | ai | |
| source-diff | obfuscated-file:dist/cjs/components/ContentSelectorWrapper.cjs | AI (source-diff): Standard rolldown minified output; code is readable LitElement component logic with no malicious patterns. | ai | |
| phantom-deps | phantom-dep:@intlayer/config | AI (phantom-deps): Same-org sibling package; phantom-dep heuristic unreliable for monorepo packages. | ai | |
| phantom-deps | phantom-dep:@intlayer/unmerged-dictionaries-entry | AI (phantom-deps): Same-org monorepo dep; likely used via subpath or re-exported, stable false positive for this package. | ai | |
| source-diff | obfuscated-file:dist/cjs/core/EditorStateManager.cjs | AI (source-diff): Standard minified build output from tsdown/bun; readable logic with no malicious patterns. | ai | |
| source-diff | obfuscated-file:dist/esm/core/EditorStateManager.mjs | AI (source-diff): Standard minified ESM build output; same pattern as CJS counterpart, no malicious indicators. | ai | |
| phantom-deps | phantom-dep:@intlayer/core | AI (phantom-deps): Same-org monorepo dep; phantom-dep heuristic fires on subpath imports like @intlayer/core/dictionaryManipulator. | ai | |
| dependencies | unvetted-dep:@intlayer/core | AI (dependencies): Sibling monorepo package co-released at the same version; stable pattern for this package. | ai | |
| dependencies | unvetted-dep:@intlayer/unmerged-dictionaries-entry | AI (dependencies): Sibling monorepo package co-released at the same version; stable pattern for this package. | ai |
Versions (showing 51 of 136)
| Version | Deps | Published |
|---|---|---|
| 8.12.2 | 4 / 8 | |
| 8.12.1 | 4 / 8 | |
| 8.12.0 | 4 / 8 | |
| 8.11.3 | 4 / 8 | |
| 8.11.2 | 4 / 8 | |
| 8.11.1 | 4 / 8 | |
| 8.11.0 | 4 / 8 | |
| 8.10.1 | 4 / 8 | |
| 8.10.0 | 4 / 8 | |
| 8.9.8 | 4 / 8 | |
| 8.9.7 | 4 / 8 | |
| 8.9.6 | 4 / 8 | |
| 8.9.5 | 4 / 8 | |
| 8.9.4 | 4 / 8 | |
| 8.9.3 | 4 / 8 | |
| 8.9.2 | 4 / 8 | |
| 8.9.1 | 4 / 8 | |
| 8.9.0 | 4 / 8 | |
| 8.8.0 | 4 / 8 | |
| 8.7.14 | 4 / 8 | |
| 8.7.13 | 4 / 8 | |
| 8.7.12 | 4 / 8 | |
| 8.7.11 | 4 / 8 | |
| 8.7.10 | 4 / 8 | |
| 8.7.9 | 4 / 8 | |
| 8.7.8 | 4 / 8 | |
| 8.7.7 | 4 / 8 | |
| 8.7.6 | 5 / 8 | |
| 8.7.5 | 5 / 8 | |
| 8.7.4 | 5 / 8 | |
| 8.7.3 | 5 / 8 | |
| 8.7.2 | 5 / 8 | |
| 8.7.1 | 5 / 8 | |
| 8.7.0 | 5 / 8 | |
| 8.6.10 | 5 / 8 | |
| 8.6.9 | 5 / 8 | |
| 8.6.8 | 5 / 8 | |
| 8.6.7 | 5 / 8 | |
| 8.6.6 | 5 / 8 | |
| 8.6.5 | 5 / 8 | |
| 8.6.4 | 5 / 8 | |
| 8.6.3 | 5 / 8 | |
| 8.6.2 | 5 / 8 | |
| 8.6.1 | 5 / 8 | |
| 8.6.0 | 5 / 8 | |
| 8.5.2 | 5 / 8 | |
| 8.5.1 | 5 / 8 | |
| 8.5.0 | 5 / 8 | |
| 8.4.10 | 5 / 8 | |
| 8.4.9 | 5 / 8 | |
| 8.4.8 | 5 / 8 |
v8.12.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v8.12.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v8.12.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v8.11.3
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v8.11.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v8.11.1
2 findingsThis version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: ay.pineau.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v8.11.0
2 findingsThis version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: ay.pineau.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v8.10.1
2 findingsThis version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: ay.pineau.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v8.10.0
2 findingsThis version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: ay.pineau.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v8.9.8
2 findingsThis version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: ay.pineau.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v8.9.7
2 findingsThis version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: ay.pineau.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v8.9.6
2 findingsThis version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: ay.pineau.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v8.9.5
2 findingsThis version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: ay.pineau.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v8.9.4
2 findingsThis version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: ay.pineau.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v8.9.3
2 findingsThis version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: ay.pineau.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v8.9.2
2 findingsThis version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: ay.pineau.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v8.9.1
2 findingsThis version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: ay.pineau.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v8.9.0
2 findingsThis version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: ay.pineau.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v8.8.0
2 findingsThis version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: ay.pineau.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v8.7.14
2 findingsThis version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: ay.pineau.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v8.7.13
2 findingsThis version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: ay.pineau.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v8.7.12
2 findingsThis version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: ay.pineau.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v8.7.10
2 findingsThis version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: ay.pineau.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v8.7.9
2 findingsThis version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: ay.pineau.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v8.7.8
2 findingsThis version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: ay.pineau.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v8.7.7
2 findingsThis version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: ay.pineau.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v8.7.6
2 findingsThis version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: ay.pineau.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v8.7.5
2 findingsThis version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: ay.pineau.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v8.7.4
2 findingsThis version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: ay.pineau.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v8.7.3
2 findingsThis version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: ay.pineau.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v8.7.2
2 findingsThis version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: ay.pineau.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v8.7.1
2 findingsThis version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: ay.pineau.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v8.7.0
2 findingsThis version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: ay.pineau.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v8.6.10
2 findingsThis version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: ay.pineau.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v8.6.9
2 findingsThis version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: ay.pineau.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v8.6.8
2 findingsThis version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: ay.pineau.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v8.6.7
2 findingsThis version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: ay.pineau.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v8.6.6
2 findingsThis version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: ay.pineau.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v8.6.5
2 findingsThis version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: ay.pineau.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v8.6.4
2 findingsThis version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: ay.pineau.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v8.6.3
2 findingsThis version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: ay.pineau.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v8.6.2
2 findingsThis version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: ay.pineau.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v8.6.1
2 findingsThis version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: ay.pineau.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v8.6.0
2 findingsThis version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: ay.pineau.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v8.5.2
2 findingsThis version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: ay.pineau.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v8.5.1
2 findingsThis version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: ay.pineau.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v8.5.0
2 findingsThis version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: ay.pineau.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v8.4.10
2 findingsThis version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: ay.pineau.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v8.4.9
2 findingsThis version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: ay.pineau.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v8.4.8
2 findingsThis version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: ay.pineau.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.