← Home

@compas-oscd/plugins

npm Repository Homepage

The official plug-ins of open-scd.

12
Versions
Apache-2.0
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 — the axios compromise (March 2026) relied on exactly this gap.

Maintainers

virtualstations

Keywords

SCLsubstation configurationIEC61850-6SCDeditor

Accepted risks

Findings the reviewer chose to accept rather than block on.

SourceRuleReasonAccepted byWhen
dependencies unvetted-dep:panzoom AI (dependencies): panzoom is a legitimate UI library; its use in an SCD editor plugin is expected and benign. ai
phantom-deps phantom-dep:lit AI (phantom-deps): lit is a transitive peer dep commonly referenced in config without direct import in plugin bundles. ai
phantom-deps phantom-dep:@openscd/wizards AI (phantom-deps): Aliased via npm: to @compas-oscd/wizards; phantom detection is a false positive for aliased deps. ai
provenance no-provenance AI (provenance): Open-source SCL tooling package; missing provenance is common and not a risk signal here. ai

Versions (showing 12 of 12)

Version Deps Published
0.0.13 21 / 35
0.0.12 21 / 35
0.0.11 21 / 35
0.0.10 21 / 35
0.0.9 21 / 35
0.0.8 21 / 35
0.0.7 21 / 35
0.0.6 21 / 34
0.0.5 21 / 34
0.0.4 21 / 34
0.0.3 21 / 34
0.0.2 21 / 34

v0.0.13

1 finding
INFO No provenance attestation provenance

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

v0.0.12

1 finding
INFO No provenance attestation provenance

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

v0.0.11

1 finding
INFO No provenance attestation provenance

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

v0.0.10

1 finding
INFO No provenance attestation provenance

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

v0.0.9

1 finding
INFO No provenance attestation provenance

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

v0.0.8

1 finding
INFO No provenance attestation provenance

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

v0.0.7

1 finding
INFO No provenance attestation provenance

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

v0.0.5

1 finding
INFO No provenance attestation provenance

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

v0.0.4

1 finding
INFO No provenance attestation provenance

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

v0.0.3

1 finding
INFO No provenance attestation provenance

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

v0.0.2

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.