← Home

@matter/node

npm Repository Homepage

API for building Matter nodes

22
Versions
Apache-2.0
License
No
Install Scripts
Verified
Provenance

Supply chain provenance

Status for the latest visible version.

SLSA provenance attestation npm registry signatures gitHead linked

Maintainers

apollon77lauckhartballoob

Keywords

iothome automationmattersmart device

Accepted risks

Findings the reviewer chose to accept rather than block on.

SourceRuleReasonAccepted byWhen
typosquat typosquat.levenshtein:zod AI (typosquat): @matter/node is a scoped IoT/Matter protocol package with no relation to zod; the Levenshtein match is a false positive that will never be relevant for this package. ai
semgrep semgrep:api-obfuscation-reflect AI (semgrep): Reflect.get() is used in a Proxy handler for transparent property delegation — standard idiomatic JavaScript, not obfuscation. Stable pattern for this package. ai
semgrep semgrep:dynamic-require AI (semgrep): load.cjs is an intentional CJS/ESM interop loader utility; dynamic require is the documented purpose of this file, not a security risk. ai
dependencies unvetted-dep:@matter/model AI (dependencies): Sibling monorepo package pinned to the same version; standard monorepo pattern. ai
dependencies unvetted-dep:@matter/types AI (dependencies): Sibling monorepo package pinned to the same version; standard monorepo pattern. ai
dependencies unvetted-dep:@matter/general AI (dependencies): Sibling monorepo package pinned to the same version; standard monorepo pattern. ai
dependencies unvetted-dep:@matter/protocol AI (dependencies): Sibling monorepo package pinned to the same version; standard monorepo pattern. ai

Versions (showing 22 of 22)

Version Deps Published
0.17.1 4 / 2
0.17.0 4 / 2
0.16.11 4 / 2
0.16.10 4 / 2
0.16.9 4 / 2
0.16.8 4 / 2
0.16.7 4 / 2
0.16.6 4 / 2
0.16.5 4 / 2
0.16.4 4 / 2
0.16.3 4 / 2
0.16.2 4 / 2
0.16.1 4 / 2
0.16.0 4 / 2
0.15.6 4 / 2
0.15.4 4 / 2
0.15.3 4 / 2
0.15.2 4 / 2
0.15.1 4 / 2
0.15.0 4 / 2
0.14.0 4 / 2
0.13.0 4 / 2

v0.17.1

1 finding
INFO Has SLSA provenance attestation provenance

Published via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.

v0.17.0

1 finding
INFO Has SLSA provenance attestation provenance

Published via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.

v0.16.11

1 finding
INFO Has SLSA provenance attestation provenance

Published via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.

v0.16.5

1 finding
INFO Has SLSA provenance attestation provenance

Published via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.

v0.16.3

1 finding
INFO Has SLSA provenance attestation provenance

Published via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.

v0.16.2

1 finding
INFO Has SLSA provenance attestation provenance

Published via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.

v0.16.1

1 finding
INFO Has SLSA provenance attestation provenance

Published via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.

v0.16.0

1 finding
INFO Has SLSA provenance attestation provenance

Published via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.

v0.15.6

1 finding
LOW No provenance attestation provenance

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

v0.15.4

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.

v0.15.3

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.

v0.15.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.

v0.15.1

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.

v0.15.0

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.

v0.14.0

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.

v0.13.0

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.