@aptos-labs/script-composer-pack
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 |
|---|---|---|---|---|
| provenance | publisher-changed | AI (provenance): Aptos Labs publishes via GitHub Actions CI/CD with SLSA attestation; publisher=GitHub Actions is expected for this package. | ai | |
| source-diff | encoded-string-file:dist/cjs/main.js | AI (source-diff): Base64-encoded WASM binary bundled from @aptos-labs/aptos-dynamic-transaction-composer; stable pattern for this package. | ai | |
| source-diff | encoded-string-file:dist/esm/main.mjs | AI (source-diff): Same base64-encoded WASM binary in ESM build; stable pattern for this package. | ai | |
| phantom-deps | phantom-dep:@aptos-labs/aptos-dynamic-transaction-composer | AI (phantom-deps): Same-org dependency used as a bundled/WASM dep; not directly imported in TS sources but legitimately declared. | ai |
Versions (showing 7 of 7)
| Version | Deps | Published |
|---|---|---|
| 0.2.4 | 0 / 9 | |
| 0.2.3 | 0 / 9 | |
| 0.2.2 | 0 / 9 | |
| 0.2.1 | 0 / 8 | |
| 0.2.0 | 0 / 8 | |
| 0.1.0 | 0 / 8 | |
| 0.0.9 | 1 / 5 |
v0.2.4
2 findingsThis version was published by a different npm account than previous versions on 2026-05-31. 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.
v0.2.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.2.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.2.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.2.0
3 findingsModified file contains 1 long encoded string(s) (200+ chars). These are commonly used to hide malicious payloads.
Modified file contains 1 long encoded string(s) (200+ chars). These are commonly used to hide malicious payloads.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.9
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.