@matter/nodejs-ble
Matter BLE support for node.js
Supply chain provenance
Status for the latest visible version.
Maintainers
Keywords
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| phantom-deps | phantom-dep:@matter/types | AI (phantom-deps): Same-org monorepo dep; not directly imported but legitimately declared. | ai | |
| phantom-deps | phantom-dep:@matter/general | AI (phantom-deps): Same-org monorepo dep; not directly imported but legitimately declared. | ai | |
| phantom-deps | phantom-dep:@matter/protocol | AI (phantom-deps): Same-org monorepo dep; not directly imported but legitimately declared. | ai |
Versions (showing 23 of 23)
| Version | Deps | Published |
|---|---|---|
| 0.17.1 | 3 / 0 | |
| 0.17.0 | 3 / 0 | |
| 0.16.11 | 3 / 1 | |
| 0.16.10 | 3 / 1 | |
| 0.16.9 | 3 / 1 | |
| 0.16.8 | 3 / 1 | |
| 0.16.7 | 3 / 1 | |
| 0.16.6 | 3 / 1 | |
| 0.16.5 | 3 / 1 | |
| 0.16.4 | 3 / 1 | |
| 0.16.3 | 3 / 1 | |
| 0.16.2 | 3 / 1 | |
| 0.16.1 | 3 / 1 | |
| 0.16.0 | 3 / 1 | |
| 0.15.6 | 3 / 1 | |
| 0.15.5 | 3 / 1 | |
| 0.15.4 | 3 / 1 | |
| 0.15.3 | 3 / 1 | |
| 0.15.2 | 3 / 1 | |
| 0.15.1 | 3 / 1 | |
| 0.15.0 | 3 / 1 | |
| 0.14.0 | 3 / 1 | |
| 0.13.0 | 3 / 1 |
v0.17.1
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.17.0
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.16.11
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.16.10
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.16.9
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.16.8
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.16.7
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.16.6
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.16.5
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.16.4
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.16.3
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.16.2
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.16.1
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.16.0
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.15.6
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.15.5
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.15.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.15.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.15.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.15.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.15.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.14.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.13.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.