← Home

@quatrain/queue-aws

npm Repository Homepage

Queue adapter for AWS SQS

23
Versions
AGPL-3.0-only
License
No
Install Scripts
Attested
Provenance

Supply chain provenance

Status for the latest visible version.

SLSA provenance attestation (unverified) npm registry signatures No source commit

Maintainers

crapougnaxelliottlepine

Accepted risks

Findings the reviewer chose to accept rather than block on.

SourceRuleReasonAccepted byWhen
publish-pattern dormant-publish AI (publish-pattern): Publisher has 326 approved packages and 0 rejected; no material changes from prior version; low-risk context. ai
provenance slsa-provenance AI (provenance): Package consistently published via CI/CD with Sigstore attestation; strong supply chain integrity signal. ai
license copyleft-license:AGPL-3.0-only AI (license): AGPL-3.0 is the declared license for this package; stable across all versions. ai

Versions (showing 23 of 23)

Version Deps Published
1.1.28 2 / 11
1.1.27 2 / 11
1.1.26 2 / 11
1.1.25 2 / 11
1.1.24 2 / 11
1.1.23 2 / 11
1.1.22 2 / 11
1.1.21 2 / 11
1.1.20 2 / 11
1.1.19 2 / 11
1.1.18 2 / 11
1.1.17 2 / 11
1.1.16 2 / 11
1.1.15 2 / 11
1.1.14 2 / 11
1.1.13 2 / 11
1.1.12 2 / 11
1.1.11 2 / 11
1.1.10 2 / 11
1.1.9 2 / 11
1.1.8 2 / 11
1.1.7 2 / 11
1.1.6 2 / 11

v1.1.11

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v1.1.10

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v1.1.9

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v1.1.8

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v1.1.7

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v1.1.6

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.