@defra-fish/sqs-receiver-service
SQS Receiver service
Supply chain provenance
Status for the latest visible version.
Maintainers
Keywords
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| provenance | publisher-changed | AI (provenance): Transition to GitHub Actions publisher with SLSA provenance attestation; consistent with CI/CD automation for DEFRA org. | ai | |
| maintainer-change | maintainer-removed | AI (maintainer-change): Maintainer removal accompanies move to GitHub Actions automation; no malicious indicators present. | ai | |
| semgrep | semgrep:shady-links-raw-ip | AI (semgrep): Raw IP appears only in test fixtures as a mock SQS queue URL; stable false positive for this package. | ai | |
| phantom-deps | phantom-dep:uuid | AI (phantom-deps): uuid is listed as a runtime dependency in package.json; phantom-dep heuristic is a false positive here. | ai |
Versions (showing 75 of 75)
| Version | Deps | Published |
|---|---|---|
| 1.72.0 | 5 / 1 | |
| 1.71.0 | 5 / 1 | |
| 1.70.1 | 5 / 1 | |
| 1.70.0 | 5 / 1 | |
| 1.69.0 | 5 / 1 | |
| 1.68.0 | 5 / 1 | |
| 1.67.0 | 5 / 1 | |
| 1.66.0 | 5 / 1 | |
| 1.65.0 | 5 / 1 | |
| 1.64.0 | 5 / 1 | |
| 1.63.0 | 5 / 1 | |
| 1.62.0 | 5 / 1 | |
| 1.61.0 | 5 / 1 | |
| 1.60.0 | 5 / 1 | |
| 1.59.0 | 5 / 1 | |
| 1.58.0 | 5 / 1 | |
| 1.57.0 | 5 / 1 | |
| 1.56.0 | 5 / 1 | |
| 1.55.0 | 5 / 1 | |
| 1.54.0 | 5 / 1 | |
| 1.53.0 | 5 / 1 | |
| 1.52.0 | 5 / 1 | |
| 1.51.0 | 5 / 1 | |
| 1.50.0 | 5 / 1 | |
| 1.49.0 | 5 / 1 | |
| 1.48.0 | 5 / 1 | |
| 1.47.0 | 5 / 1 | |
| 1.46.0 | 5 / 1 | |
| 1.45.0 | 5 / 1 | |
| 1.44.0 | 5 / 1 | |
| 1.43.0 | 5 / 1 | |
| 1.42.0 | 5 / 1 | |
| 1.41.0 | 5 / 1 | |
| 1.40.0 | 5 / 1 | |
| 1.39.0 | 5 / 1 | |
| 1.38.0 | 5 / 1 | |
| 1.37.0 | 5 / 1 | |
| 1.36.0 | 5 / 1 | |
| 1.35.0 | 5 / 1 | |
| 1.34.0 | 5 / 1 | |
| 1.33.0 | 5 / 1 | |
| 1.32.0 | 5 / 1 | |
| 1.31.0 | 5 / 1 | |
| 1.30.0 | 5 / 1 | |
| 1.29.0 | 5 / 1 | |
| 1.28.0 | 5 / 1 | |
| 1.27.0 | 5 / 1 | |
| 1.26.0 | 5 / 1 | |
| 1.25.0 | 5 / 1 | |
| 1.24.0 | 5 / 1 | |
| 1.23.0 | 5 / 1 | |
| 1.22.1 | 5 / 1 | |
| 1.21.0 | 5 / 1 | |
| 1.20.0 | 5 / 1 | |
| 1.19.0 | 5 / 1 | |
| 1.18.0 | 5 / 1 | |
| 1.17.0 | 5 / 1 | |
| 1.16.0 | 5 / 1 | |
| 1.15.0 | 5 / 1 | |
| 1.14.0 | 5 / 1 | |
| 1.13.0 | 5 / 1 | |
| 1.12.0 | 5 / 1 | |
| 1.11.0 | 5 / 1 | |
| 1.10.0 | 5 / 1 | |
| 1.9.0 | 5 / 1 | |
| 1.8.0 | 5 / 1 | |
| 1.7.1 | 5 / 1 | |
| 1.7.0 | 5 / 1 | |
| 1.6.0 | 5 / 1 | |
| 1.5.0 | 5 / 1 | |
| 1.4.0 | 5 / 1 | |
| 1.3.0 | 5 / 1 | |
| 1.2.0 | 5 / 1 | |
| 1.1.0 | 5 / 1 | |
| 1.0.0 | 5 / 1 |
v1.60.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.59.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.58.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.57.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.56.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.55.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.54.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.53.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.52.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.51.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.50.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.49.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.48.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.47.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.46.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.45.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.44.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.43.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.42.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.41.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.40.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.39.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.38.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.37.0
2 findingsPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
This version was published by a different npm account (npm-envage) than the most recent previously approved version (jaucourt) on 2023-12-08, but npm-envage is listed as a maintainer on prior approved versions (matched on name). This looks like a manual publish by a known maintainer rather than a publisher change. Recorded as INFO for audit trail.
v1.36.0
2 findingsPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
This version was published by a different npm account (npm-envage) than the most recent previously approved version (jaucourt) on 2023-10-12, but npm-envage is listed as a maintainer on prior approved versions (matched on name). This looks like a manual publish by a known maintainer rather than a publisher change. Recorded as INFO for audit trail.
v1.35.0
2 findingsPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
This version was published by a different npm account (jaucourt) than the most recent previously approved version (npm-envage) on 2023-09-11, but jaucourt is listed as a maintainer on prior approved versions (matched on name). This looks like a manual publish by a known maintainer rather than a publisher change. Recorded as INFO for audit trail.
v1.34.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.33.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.32.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.31.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.30.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.29.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.28.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.27.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.26.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.25.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.24.0
2 findingsPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
This version was published by a different npm account (npm-envage) than the most recent previously approved version (jaucourt) on 2022-06-08, but npm-envage is listed as a maintainer on prior approved versions (matched on name). This looks like a manual publish by a known maintainer rather than a publisher change. Recorded as INFO for audit trail.
v1.23.0
2 findingsPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
This version was published by a different npm account (npm-envage) than the most recent previously approved version (jaucourt) on 2022-05-16, but npm-envage is listed as a maintainer on prior approved versions (matched on name). This looks like a manual publish by a known maintainer rather than a publisher change. Recorded as INFO for audit trail.
v1.22.1
2 findingsPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
This version was published by a different npm account (jaucourt) than the most recent previously approved version (npm-envage) on 2022-03-17, but jaucourt is listed as a maintainer on prior approved versions (matched on name). This looks like a manual publish by a known maintainer rather than a publisher change. Recorded as INFO for audit trail.
v1.21.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.20.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.19.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.18.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.17.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.16.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.15.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.14.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.13.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.12.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.11.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.10.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.9.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.8.0
2 findingsPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
This version was published by a different npm account (npm-envage) than the most recent previously approved version (jaucourt) on 2021-03-24, but npm-envage is listed as a maintainer on prior approved versions (matched on name). This looks like a manual publish by a known maintainer rather than a publisher change. Recorded as INFO for audit trail.
v1.7.1
2 findingsPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
This version was published by a different npm account (jaucourt) than the most recent previously approved version (npm-envage) on 2021-03-29, but jaucourt is listed as a maintainer on prior approved versions (matched on name). This looks like a manual publish by a known maintainer rather than a publisher change. Recorded as INFO for audit trail.
v1.7.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.6.0
2 findingsThis version was published by a different npm account (jaucourt) than the most recent previously approved version (npm-envage) on 2021-03-09. It has since remained available on npm for 1964 days without being unpublished, which is inconsistent with an account takeover — those are typically removed by npm shortly after discovery.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.5.0
2 findingsThis version was published by a different npm account (jaucourt) than the most recent previously approved version (npm-envage) on 2021-02-09. It has since remained available on npm for 1992 days without being unpublished, which is inconsistent with an account takeover — those are typically removed by npm shortly after discovery.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.4.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
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. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.