@iyio/aws-sqs
Supply chain provenance
Status for the latest visible version.
Without SLSA provenance there is no cryptographic link between this tarball and the public source — the axios compromise (March 2026) relied on exactly this gap.
Maintainers
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| phantom-deps | phantom-dep:@aws-crypto/sha256-browser | AI (phantom-deps): AWS crypto peer dep; stable FP. | ai | |
| phantom-deps | phantom-dep:@smithy/signature-v4 | AI (phantom-deps): Framework-scoped Smithy dep; stable FP. | ai | |
| phantom-deps | phantom-dep:@smithy/protocol-http | AI (phantom-deps): Framework-scoped Smithy dep; stable FP. | ai | |
| phantom-deps | phantom-dep:zod | AI (phantom-deps): Monorepo peer dep pattern; stable FP for this package. | ai | |
| phantom-deps | phantom-dep:rxjs | AI (phantom-deps): Monorepo peer dep pattern; stable FP for this package. | ai | |
| phantom-deps | phantom-dep:uuid | AI (phantom-deps): Monorepo peer dep pattern; stable FP for this package. | ai | |
| phantom-deps | phantom-dep:date-fns | AI (phantom-deps): Monorepo peer dep pattern; stable FP for this package. | ai | |
| phantom-deps | phantom-dep:@aws-sdk/types | AI (phantom-deps): Framework-scoped AWS SDK type dep; stable FP. | ai | |
| bogus-package | bogus-package | AI (bogus-package): Internal monorepo package; missing metadata is typical for this publisher's package style. | ai | |
| typosquat | typosquat.levenshtein:aws-sdk | AI (typosquat): Scoped @iyio monorepo package; name similarity to aws-sdk is coincidental, not impersonation. | ai |
Versions (showing 24 of 24)
| Version | Deps | Published |
|---|---|---|
| 0.9.1 | 0 / 0 | |
| 0.8.18 | 0 / 0 | |
| 0.8.17 | 0 / 0 | |
| 0.8.11 | 0 / 0 | |
| 0.8.1 | 0 / 0 | |
| 0.8.0 | 0 / 0 | |
| 0.7.50 | 8 / 0 | |
| 0.7.43 | 8 / 0 | |
| 0.7.42 | 8 / 0 | |
| 0.7.37 | 8 / 0 | |
| 0.7.36 | 8 / 0 | |
| 0.7.34 | 8 / 0 | |
| 0.7.33 | 8 / 0 | |
| 0.7.31 | 8 / 0 | |
| 0.7.29 | 8 / 0 | |
| 0.7.28 | 8 / 0 | |
| 0.7.24 | 8 / 0 | |
| 0.7.23 | 9 / 0 | |
| 0.7.22 | 9 / 0 | |
| 0.7.19 | 9 / 0 | |
| 0.7.17 | 9 / 0 | |
| 0.7.15 | 9 / 0 | |
| 0.7.14 | 9 / 0 | |
| 0.7.13 | 9 / 0 |
v0.9.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.8.18
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.8.17
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.8.11
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.8.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.8.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.7.50
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.7.43
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.7.42
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.7.37
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.7.36
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.7.34
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.7.33
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.7.31
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.7.29
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.7.28
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.7.24
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.7.23
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.7.22
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.7.19
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.7.17
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.7.15
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.7.14
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.7.13
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.