@matter/model
Matter data model
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 |
|---|---|---|---|---|
| source-diff | obfuscated-file:dist/esm/standard/resources/access-control.resource.js | AI (source-diff): ESM variant of same resource data; long spec description strings, not obfuscation. | ai | |
| source-diff | obfuscated-file:dist/esm/standard/resources/account-login.resource.js | AI (source-diff): ESM variant of same resource data; not obfuscated. | ai | |
| source-diff | large-new-source-files | AI (source-diff): Dual CJS/ESM resource files for Matter spec clusters; expected for this package's build output. | ai | |
| source-diff | obfuscated-file:dist/cjs/standard/resources/access-control.resource.js | AI (source-diff): Long lines are Matter spec description strings, not obfuscation; stable pattern for this package. | ai | |
| source-diff | obfuscated-file:dist/cjs/standard/resources/account-login.resource.js | AI (source-diff): Matter cluster resource definition with long description strings; not obfuscated. | ai | |
| dependencies | unvetted-dep:@matter/general | AI (dependencies): @matter/general is a sibling package in the same matter.js monorepo, always pinned to the same version. This is a stable monorepo dependency pattern, not a supply chain risk. | ai | |
| semgrep | semgrep:api-obfuscation-reflect | AI (semgrep): Reflect.get() is used in a standard Proxy get trap handler — idiomatic JavaScript for forwarding property access. No obfuscation intent; stable pattern for this data model library. | ai |
Versions (showing 23 of 23)
| Version | Deps | Published |
|---|---|---|
| 0.17.1 | 1 / 1 | |
| 0.17.0 | 1 / 1 | |
| 0.16.11 | 1 / 2 | |
| 0.16.10 | 1 / 2 | |
| 0.16.9 | 1 / 2 | |
| 0.16.8 | 1 / 2 | |
| 0.16.7 | 1 / 2 | |
| 0.16.6 | 1 / 2 | |
| 0.16.5 | 1 / 2 | |
| 0.16.4 | 1 / 2 | |
| 0.16.3 | 1 / 2 | |
| 0.16.2 | 1 / 2 | |
| 0.16.1 | 1 / 2 | |
| 0.16.0 | 1 / 2 | |
| 0.15.6 | 1 / 2 | |
| 0.15.5 | 1 / 2 | |
| 0.15.4 | 1 / 2 | |
| 0.15.3 | 1 / 2 | |
| 0.15.2 | 1 / 2 | |
| 0.15.1 | 1 / 2 | |
| 0.15.0 | 1 / 2 | |
| 0.14.0 | 1 / 2 | |
| 0.13.0 | 1 / 2 |
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.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.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
5 findingsNewly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Newly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Newly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Newly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.15.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.15.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.15.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.14.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.13.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.