@defra-fish/sales-api-service SEE LICENSE IN LICENSE 69 versions

@defra-fish/sales-api-service

npm Repository Homepage

Rod Licensing Sales API

69

Versions

SEE LICENSE IN LICENSE

License

No

Install Scripts

Attested

Provenance

Supply chain provenance

Status for the latest visible version.

SLSA provenance attestation (unverified) npm registry signatures gitHead linked

Maintainers

npm-envagedefradigitaladmindefradigitalcijaucourtifarawaydefra

Keywords

rodlicensingsalesapi

Accepted risks

Findings the reviewer chose to accept rather than block on.

Source	Rule	Reason	Accepted by	When
semgrep	semgrep:shady-links-raw-ip	AI (semgrep): Raw IP appears only in test fixtures for local SQS emulator; not production code.	ai	2026/05/18
semgrep	semgrep:dynamic-require	AI (semgrep): Dynamic require resolves only package.json by a fixed path join; no arbitrary module loading.	ai	2026/05/18

Versions (showing 69 of 69)

Version	Deps	Published
1.72.0	16 / 0	2026-06-17
1.71.0	16 / 0	2026-05-12
1.70.1	16 / 0	2026-05-12
1.70.0	16 / 0	2026-05-01
1.68.0	16 / 0	2026-03-17
1.66.0	16 / 0	2026-01-26
1.63.0	16 / 0	2025-09-25
1.62.0	16 / 0	2025-07-30
1.61.0	16 / 0	2025-06-25
1.58.0	16 / 0	2025-01-27
1.57.0	16 / 0	2024-12-16
1.56.0	16 / 0	2024-11-26
1.55.0	16 / 0	2024-11-26
1.54.0	16 / 0	2024-11-12
1.53.0	16 / 0	2024-11-12
1.52.0	16 / 0	2024-11-12
1.51.0	16 / 0	2024-11-12
1.50.0	16 / 0	2024-10-14
1.49.0	16 / 0	2024-09-09
1.48.0	16 / 0	2024-08-13
1.47.0	16 / 0	2024-07-24
1.46.0	16 / 0	2024-06-04
1.45.0	16 / 0	2024-05-14
1.44.0	16 / 0	2024-04-08
1.43.0	16 / 0	2024-03-12
1.42.0	16 / 0	2024-02-27
1.41.0	16 / 0	2024-02-21
1.40.0	16 / 0	2024-02-14
1.39.0	16 / 0	2024-02-12
1.38.0	16 / 0	2024-01-15
1.37.0	16 / 0	2023-12-08
1.36.0	16 / 0	2023-10-12
1.35.0	16 / 0	2023-09-11
1.34.0	16 / 0	2023-05-25
1.33.0	16 / 0	2023-05-22
1.32.0	16 / 0	2023-03-07
1.31.0	16 / 0	2023-02-27
1.30.0	16 / 0	2023-02-01
1.29.0	16 / 0	2022-12-09
1.28.0	16 / 0	2022-12-08
1.27.0	16 / 0	2022-11-21
1.26.0	16 / 0	2022-09-21
1.25.0	15 / 0	2022-07-04
1.24.0	15 / 0	2022-06-08
1.23.0	15 / 0	2022-05-16
1.22.1	15 / 0	2022-03-17
1.21.0	15 / 0	2021-11-17
1.20.0	15 / 0	2021-10-29
1.19.0	15 / 0	2021-09-06
1.18.0	15 / 0	2021-08-24
1.17.0	15 / 0	2021-08-11
1.16.0	15 / 0	2021-07-27
1.15.0	15 / 0	2021-07-14
1.14.0	15 / 0	2021-06-29
1.13.0	15 / 0	2021-06-16
1.12.0	15 / 0	2021-06-01
1.11.0	15 / 0	2021-05-26
1.10.0	15 / 0	2021-05-18
1.9.0	15 / 0	2021-04-23
1.8.0	15 / 0	2021-03-24
1.7.1	15 / 0	2021-03-29
1.7.0	15 / 0	2021-03-24
1.6.0	15 / 0	2021-03-09
1.5.0	15 / 0	2021-02-09
1.4.0	15 / 0	2020-11-06
1.3.0	15 / 0	2020-10-27
1.2.0	15 / 0	2020-10-15
1.1.0	15 / 0	2020-10-14
1.0.0	15 / 0	2020-10-13

v1.58.0

1 finding

LOW No provenance attestation provenance

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

v1.57.0

1 finding

LOW No provenance attestation provenance

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

v1.56.0

1 finding

LOW No provenance attestation provenance

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

v1.55.0

1 finding

LOW No provenance attestation provenance

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

v1.54.0

1 finding

LOW No provenance attestation provenance

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

v1.53.0

1 finding

LOW No provenance attestation provenance

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

v1.52.0

1 finding

LOW No provenance attestation provenance

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

v1.51.0

1 finding

LOW No provenance attestation provenance

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

v1.50.0

1 finding

LOW No provenance attestation provenance

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

v1.49.0

1 finding

LOW No provenance attestation provenance

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

v1.48.0

1 finding

LOW No provenance attestation provenance

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

v1.47.0

1 finding

LOW No provenance attestation provenance

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

v1.46.0

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.45.0

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.44.0

1 finding

LOW No provenance attestation provenance

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

v1.43.0

1 finding

LOW No provenance attestation provenance

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

v1.42.0

1 finding

LOW No provenance attestation provenance

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

v1.41.0

1 finding

LOW No provenance attestation provenance

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

v1.40.0

1 finding

LOW No provenance attestation provenance

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

v1.39.0

1 finding

LOW No provenance attestation provenance

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

v1.38.0

1 finding

LOW No provenance attestation provenance

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

v1.37.0

1 finding

LOW No provenance attestation provenance

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

v1.36.0

1 finding

LOW No provenance attestation provenance

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

v1.35.0

2 findings

LOW No provenance attestation provenance

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

INFO Publisher changed: npm-envage → jaucourt (on 2023-09-11, known maintainer) provenance

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 finding

LOW No provenance attestation provenance

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

v1.33.0

1 finding

LOW No provenance attestation provenance

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

v1.32.0

1 finding

LOW No provenance attestation provenance

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

v1.31.0

1 finding

LOW No provenance attestation provenance

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

v1.30.0

1 finding

LOW No provenance attestation provenance

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

v1.29.0

1 finding

LOW No provenance attestation provenance

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

v1.28.0

1 finding

LOW No provenance attestation provenance

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

v1.27.0

1 finding

LOW No provenance attestation provenance

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

v1.26.0

1 finding

LOW No provenance attestation provenance

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

v1.25.0

1 finding

LOW No provenance attestation provenance

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

v1.24.0

2 findings

LOW No provenance attestation provenance

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

INFO Publisher changed: jaucourt → npm-envage (on 2022-06-08, known maintainer) provenance

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 findings

LOW No provenance attestation provenance

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

INFO Publisher changed: jaucourt → npm-envage (on 2022-05-16, known maintainer) provenance

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 findings

LOW No provenance attestation provenance

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

INFO Publisher changed: npm-envage → jaucourt (on 2022-03-17, known maintainer) provenance

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 finding

LOW No provenance attestation provenance

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

v1.20.0

1 finding

LOW No provenance attestation provenance

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

v1.19.0

1 finding

LOW No provenance attestation provenance

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

v1.18.0

1 finding

LOW No provenance attestation provenance

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

v1.17.0

1 finding

LOW No provenance attestation provenance

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

v1.16.0

1 finding

LOW No provenance attestation provenance

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

v1.15.0

1 finding

LOW No provenance attestation provenance

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

v1.14.0

1 finding

LOW No provenance attestation provenance

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

v1.13.0

1 finding

LOW No provenance attestation provenance

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

v1.12.0

1 finding

LOW No provenance attestation provenance

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

v1.11.0

1 finding

LOW No provenance attestation provenance

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

v1.10.0

1 finding

LOW No provenance attestation provenance

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

v1.9.0

1 finding

LOW No provenance attestation provenance

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

v1.8.0

2 findings

LOW No provenance attestation provenance

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

INFO Publisher changed: jaucourt → npm-envage (on 2021-03-24, known maintainer) provenance

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 findings

LOW No provenance attestation provenance

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

INFO Publisher changed: npm-envage → jaucourt (on 2021-03-29, known maintainer) provenance

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 finding

LOW No provenance attestation provenance

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

v1.6.0

1 finding

LOW No provenance attestation provenance

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

v1.5.0

2 findings

MEDIUM Publisher changed: npm-envage → jaucourt (on 2021-02-09, unremoved on npm for 1992d) provenance

This 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.

LOW No provenance attestation provenance

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

v1.4.0

1 finding

LOW No provenance attestation provenance

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

v1.3.0

1 finding

LOW No provenance attestation provenance

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

v1.2.0

1 finding

LOW No provenance attestation provenance

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

v1.1.0

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.0.0

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.