@wormhole-labs/wallet-aggregator-aptos
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 |
|---|---|---|---|---|
| phantom-deps | phantom-dep:@martianwallet/aptos-wallet-adapter | AI (phantom-deps): Wallet aggregator re-exports adapters via config; not directly imported by design. | ai | |
| phantom-deps | phantom-dep:fewcha-plugin-wallet-adapter | AI (phantom-deps): Wallet aggregator re-exports adapters via config; not directly imported by design. | ai | |
| phantom-deps | phantom-dep:@pontem/wallet-adapter-plugin | AI (phantom-deps): Wallet aggregator re-exports adapters via config; not directly imported by design. | ai | |
| phantom-deps | phantom-dep:@bitget-wallet/aptos-wallet-adapter | AI (phantom-deps): Wallet aggregator re-exports adapters via config; not directly imported by design. | ai | |
| phantom-deps | phantom-dep:petra-plugin-wallet-adapter | AI (phantom-deps): Wallet aggregator re-exports adapters via config; not directly imported by design. | ai | |
| provenance | missing-githead | AI (provenance): SLSA provenance attestation present; gitHead absence is offset by Sigstore-signed CI provenance. | ai | |
| provenance | publisher-changed | AI (provenance): Transition to GitHub Actions CI/CD publishing is confirmed by SLSA provenance attestation; stable pattern for this package going forward. | ai | |
| dependencies | unvetted-dep:@wormhole-labs/wallet-aggregator-core | AI (dependencies): Sibling package from the same wormhole-labs monorepo; expected internal dependency across all versions. | ai |
Versions (showing 17 of 17)
| Version | Deps | Published |
|---|---|---|
| 1.7.4 | 4 / 4 | |
| 1.7.3 | 4 / 4 | |
| 1.7.2 | 4 / 4 | |
| 1.7.1 | 4 / 4 | |
| 1.7.0 | 4 / 4 | |
| 1.6.0 | 4 / 4 | |
| 1.5.1 | 4 / 4 | |
| 1.5.0 | 4 / 4 | |
| 1.4.0 | 4 / 4 | |
| 1.3.3 | 4 / 4 | |
| 1.3.2 | 4 / 4 | |
| 1.3.1 | 4 / 4 | |
| 1.3.0 | 4 / 4 | |
| 1.2.0 | 4 / 4 | |
| 1.1.0 | 4 / 4 | |
| 1.0.1 | 9 / 4 | |
| 1.0.0 | 9 / 4 |
v1.7.4
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v1.7.3
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v1.7.2
2 findingsThis version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: GitHub Actions.
Published via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v1.7.1
2 findingsThis version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: GitHub Actions.
Published via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v1.7.0
2 findingsThis version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: GitHub Actions.
Published via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v1.6.0
2 findingsThis version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: GitHub Actions.
Published via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v1.5.1
2 findingsThis version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: GitHub Actions.
Published via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v1.5.0
2 findingsThis version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: GitHub Actions.
Published via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v1.4.0
2 findingsThis version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: GitHub Actions.
Published via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v1.3.3
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v1.3.2
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v1.3.1
2 findingsThis version was published by a different npm account than previous versions on 2025-10-29. This could indicate a legitimate maintainer transition or an account compromise.
Published via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v1.3.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.2.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.1.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.