@avalabs/avalanche-module
This package implements the core logic for the Avalanche (Avalanche Virtual Machine) module.
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 |
|---|---|---|---|---|
| maintainer-change | maintainer-removed | AI (maintainer-change): Avalabs org migrated to GitHub Actions CI publishing; maintainer consolidation is consistent with org-level automation. | ai | |
| publish-pattern | new-deps-added | AI (publish-pattern): New dep @avalabs/crypto-sdk is same org scope; consistent with internal SDK refactoring. | ai | |
| phantom-deps | phantom-dep:bn.js | AI (phantom-deps): Transitive dependency via @avalabs/avalanchejs; declared in package.json. | ai | |
| phantom-deps | phantom-dep:@avalabs/types | AI (phantom-deps): Transitive dependency via @avalabs/avalanchejs and core-chains-sdk; same-org scope. | ai | |
| phantom-deps | phantom-dep:@avalabs/core-chains-sdk | AI (phantom-deps): Direct dependency; declared in package.json. | ai | |
| phantom-deps | phantom-dep:@avalabs/core-etherscan-sdk | AI (phantom-deps): Direct dependency; declared in package.json. | ai |
Versions (showing 33 of 33)
| Version | Deps | Published |
|---|---|---|
| 3.9.0 | 14 / 9 | |
| 3.8.1 | 13 / 9 | |
| 3.8.0 | 13 / 9 | |
| 3.7.3 | 13 / 9 | |
| 3.7.2 | 13 / 9 | |
| 3.7.1 | 13 / 9 | |
| 3.7.0 | 13 / 9 | |
| 3.6.2 | 13 / 9 | |
| 3.6.1 | 13 / 9 | |
| 3.6.0 | 13 / 9 | |
| 3.5.1 | 13 / 9 | |
| 3.5.0 | 13 / 9 | |
| 3.4.0 | 13 / 9 | |
| 3.3.1 | 13 / 9 | |
| 3.3.0 | 13 / 9 | |
| 3.2.0 | 13 / 9 | |
| 3.1.4 | 13 / 9 | |
| 3.1.3 | 13 / 9 | |
| 3.1.2 | 13 / 9 | |
| 3.1.1 | 13 / 9 | |
| 3.1.0 | 13 / 9 | |
| 3.0.7 | 13 / 9 | |
| 3.0.5 | 13 / 9 | |
| 3.0.4 | 13 / 9 | |
| 3.0.3 | 13 / 9 | |
| 3.0.2 | 13 / 9 | |
| 3.0.1 | 13 / 9 | |
| 3.0.0 | 13 / 9 | |
| 2.2.1 | 13 / 9 | |
| 2.2.0 | 13 / 9 | |
| 2.1.0 | 13 / 9 | |
| 2.0.1 | 13 / 9 | |
| 2.0.0 | 13 / 9 |
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. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.2.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.1.4
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.1.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.1.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
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. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.0.7
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.0.5
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.0.4
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.0.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.0.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.0.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.0.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.2.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.2.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.1.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.0.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.0.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.