@avalabs/vm-module-types
Supply chain provenance
Status for the latest visible version.
Maintainers
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| dependencies | unvetted-dep:hypersdk-client | AI (dependencies): hypersdk-client is an Avalanche ecosystem library consistent with this package's purpose; stable dependency across versions. | ai | |
| phantom-deps | phantom-dep:bitcoinjs-lib | AI (phantom-deps): Type-definitions package; bitcoinjs-lib is a declared dep used for type re-exports, not a direct import in source. | ai | |
| phantom-deps | phantom-dep:@blockaid/client | AI (phantom-deps): Declared dep referenced in config/type files; phantom-dep heuristic fires on type-only usage patterns common in this package. | ai |
Versions (showing 33 of 33)
| Version | Deps | Published |
|---|---|---|
| 3.9.0 | 7 / 6 | |
| 3.8.1 | 7 / 6 | |
| 3.8.0 | 7 / 6 | |
| 3.7.3 | 7 / 6 | |
| 3.7.2 | 7 / 6 | |
| 3.7.1 | 7 / 6 | |
| 3.7.0 | 7 / 6 | |
| 3.6.2 | 7 / 6 | |
| 3.6.1 | 7 / 6 | |
| 3.6.0 | 7 / 6 | |
| 3.5.1 | 7 / 6 | |
| 3.5.0 | 7 / 6 | |
| 3.4.0 | 7 / 6 | |
| 3.3.1 | 7 / 6 | |
| 3.3.0 | 7 / 6 | |
| 3.2.0 | 7 / 6 | |
| 3.1.4 | 7 / 6 | |
| 3.1.3 | 7 / 6 | |
| 3.1.2 | 7 / 6 | |
| 3.1.1 | 7 / 6 | |
| 3.1.0 | 7 / 6 | |
| 3.0.7 | 7 / 6 | |
| 3.0.5 | 7 / 6 | |
| 3.0.4 | 7 / 6 | |
| 3.0.3 | 7 / 6 | |
| 3.0.2 | 7 / 6 | |
| 3.0.1 | 7 / 6 | |
| 3.0.0 | 7 / 6 | |
| 2.2.1 | 7 / 6 | |
| 2.2.0 | 7 / 6 | |
| 2.1.0 | 7 / 6 | |
| 2.0.1 | 7 / 6 | |
| 2.0.0 | 7 / 6 |
v3.9.0
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v3.8.1
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v3.8.0
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v3.7.3
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v3.7.2
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v3.7.1
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v3.7.0
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v3.6.2
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v3.6.1
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v3.6.0
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v3.5.1
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v3.5.0
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v3.4.0
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v3.3.1
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v3.3.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.2.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.1.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.1.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.1.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.1.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.1.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.0.7
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.0.5
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.0.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.0.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.0.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.0.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.0.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.2.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.2.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.1.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.0.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.0.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.