← Home

@archilogic/extension-sdk

npm

The Plugin SDK allows to create plugins for the Archilogic editor.

27
Versions
—
License
No
Install Scripts
Missing
Provenance

Supply chain provenance

Status for the latest visible version.

No SLSA provenance npm registry signatures gitHead linked

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

frederic-schwarzmredelebendevinearchilogic-ci

Accepted risks

Findings the reviewer chose to accept rather than block on.

SourceRuleReasonAccepted byWhen
dependencies unvetted-dep:@archilogic/penpal AI (dependencies): Same-org scoped package, replaces prior direct penpal dep. ai
provenance publisher-changed AI (provenance): CI account switch, consistent with automated release pipeline, no other malicious signal. ai
maintainer-change maintainer-removed AI (maintainer-change): Expected fallout of CI publishing migration, not a takeover indicator here. ai
phantom-deps phantom-dep:tiny-emitter AI (phantom-deps): Bundled SDK; deps may be consumed indirectly via build output rather than direct imports. ai
phantom-deps phantom-dep:@archilogic/penpal AI (phantom-deps): Same-org scoped package; likely consumed via bundled dist rather than direct import. ai

Versions (showing 27 of 27)

Version Deps Published
0.14.0 0 / 3
0.13.2 0 / 3
0.13.1 0 / 3
0.13.0 0 / 3
0.12.0 0 / 3
0.11.0 0 / 3
0.10.3 0 / 3
0.10.2 0 / 3
0.10.1 2 / 3
0.10.0 2 / 3
0.9.1 2 / 3
0.9.0 2 / 3
0.8.0 2 / 3
0.7.1 2 / 3
0.7.0 2 / 3
0.6.2 2 / 2
0.6.1 2 / 2
0.6.0 2 / 2
0.5.1 1 / 1
0.5.0 1 / 1
0.4.0 1 / 1
0.3.0 1 / 1
0.2.5 1 / 1
0.2.4 1 / 1
0.2.3 1 / 1
0.2.2 1 / 1
0.2.1 1 / 1

v0.14.0

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v0.13.2

2 findings
HIGH Publisher changed: archilogic-ci → GitHub Actions (on 2026-07-21) provenance

This version was published by a different npm account than previous versions on 2026-07-21. This could indicate a legitimate maintainer transition or an account compromise.

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v0.13.1

2 findings
HIGH Publisher changed: archilogic-ci → GitHub Actions (on 2026-07-03) provenance

This version was published by a different npm account than previous versions on 2026-07-03. This could indicate a legitimate maintainer transition or an account compromise.

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v0.10.0

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v0.9.1

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v0.9.0

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v0.8.0

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v0.7.1

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v0.7.0

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v0.6.2

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v0.6.1

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v0.6.0

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.