@matter/types
Definitions for Matter application
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/model | AI (phantom-deps): Package uses Node.js 'imports' field aliasing (#model -> @matter/model) rather than direct imports; phantom-dep false positive for this monorepo pattern. | ai |
Versions (showing 46 of 46)
| Version | Deps | Published |
|---|---|---|
| 0.17.7 | 2 / 1 | |
| 0.17.6 | 2 / 1 | |
| 0.17.5 | 2 / 1 | |
| 0.17.4 | 2 / 1 | |
| 0.17.3 | 2 / 1 | |
| 0.17.2 | 2 / 1 | |
| 0.17.1 | 2 / 1 | |
| 0.17.0 | 2 / 1 | |
| 0.16.11 | 2 / 2 | |
| 0.16.10 | 2 / 2 | |
| 0.16.9 | 2 / 2 | |
| 0.16.8 | 2 / 2 | |
| 0.16.7 | 2 / 2 | |
| 0.16.6 | 2 / 2 | |
| 0.16.5 | 2 / 2 | |
| 0.16.4 | 2 / 2 | |
| 0.16.3 | 2 / 2 | |
| 0.16.2 | 2 / 2 | |
| 0.16.1 | 2 / 2 | |
| 0.16.0 | 2 / 2 | |
| 0.15.6 | 2 / 2 | |
| 0.15.5 | 2 / 2 | |
| 0.15.4 | 2 / 2 | |
| 0.15.3 | 2 / 2 | |
| 0.15.2 | 2 / 2 | |
| 0.15.1 | 2 / 2 | |
| 0.15.0 | 2 / 2 | |
| 0.14.0 | 2 / 2 | |
| 0.13.0 | 2 / 2 | |
| 0.12.6 | 3 / 2 | |
| 0.12.5 | 3 / 2 | |
| 0.12.4 | 3 / 2 | |
| 0.12.3 | 3 / 2 | |
| 0.12.2 | 3 / 2 | |
| 0.12.1 | 3 / 2 | |
| 0.12.0 | 3 / 2 | |
| 0.11.9 | 3 / 2 | |
| 0.11.8 | 3 / 2 | |
| 0.11.7 | 3 / 2 | |
| 0.11.6 | 3 / 2 | |
| 0.11.5 | 3 / 2 | |
| 0.11.4 | 3 / 2 | |
| 0.11.3 | 3 / 2 | |
| 0.11.2 | 3 / 2 | |
| 0.11.1 | 3 / 2 | |
| 0.11.0 | 3 / 2 |
v0.17.7
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.17.6
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.17.5
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.17.4
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.12.6
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.12.5
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.12.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.12.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.12.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.12.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.12.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.11.9
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.11.8
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.11.7
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.11.6
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.11.5
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.11.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.11.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.11.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.11.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.11.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.