@defra-fish/pocl-job SEE LICENSE IN LICENSE 51 versions

@defra-fish/pocl-job

npm Repository Homepage

Post Office Counter Licence sales processor

51

Versions

SEE LICENSE IN LICENSE

License

No

Install Scripts

Verified

Provenance

Supply chain provenance

Status for the latest visible version.

SLSA provenance attestation 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:dynamic-require	AI (semgrep): Resolves own package.json via Path.join(__dirname) — not arbitrary module loading, stable pattern across versions.	ai	2026/05/04

Versions (showing 51 of 75)

View all versions

Version	Deps	Published
1.72.0	9 / 0	2026-06-17
1.71.0	9 / 0	2026-05-12
1.70.1	9 / 0	2026-05-12
1.70.0	9 / 0	2026-05-01
1.69.0	9 / 0	2026-04-02
1.68.0	9 / 0	2026-03-17
1.67.0	9 / 0	2026-02-20
1.66.0	9 / 0	2026-01-26
1.65.0	9 / 0	2026-01-22
1.64.0	9 / 0	2025-11-24
1.63.0	9 / 0	2025-09-25
1.62.0	9 / 0	2025-07-30
1.61.0	9 / 0	2025-06-25
1.60.0	9 / 0	2025-04-09
1.59.0	9 / 0	2025-03-11
1.58.0	9 / 0	2025-01-27
1.57.0	9 / 0	2024-12-16
1.56.0	9 / 0	2024-11-26
1.55.0	10 / 0	2024-11-26
1.54.0	10 / 0	2024-11-12
1.53.0	10 / 0	2024-11-12
1.52.0	10 / 0	2024-11-12
1.51.0	10 / 0	2024-11-12
1.50.0	10 / 0	2024-10-14
1.49.0	10 / 0	2024-09-09
1.48.0	10 / 0	2024-08-13
1.47.0	10 / 0	2024-07-24
1.46.0	10 / 0	2024-06-04
1.45.0	10 / 0	2024-05-14
1.44.0	10 / 0	2024-04-08
1.43.0	10 / 0	2024-03-12
1.42.0	10 / 0	2024-02-27
1.41.0	10 / 0	2024-02-21
1.40.0	10 / 0	2024-02-14
1.39.0	10 / 0	2024-02-12
1.38.0	10 / 0	2024-01-15
1.37.0	10 / 0	2023-12-08
1.36.0	10 / 0	2023-10-12
1.35.0	10 / 0	2023-09-11
1.34.0	10 / 0	2023-05-25
1.33.0	10 / 0	2023-05-22
1.32.0	10 / 0	2023-03-07
1.31.0	10 / 0	2023-02-27
1.30.0	10 / 0	2023-02-01
1.29.0	10 / 0	2022-12-09
1.28.0	10 / 0	2022-12-08
1.27.0	10 / 0	2022-11-21
1.26.0	10 / 0	2022-09-21
1.25.0	10 / 0	2022-07-04
1.24.0	10 / 0	2022-06-08
1.23.0	10 / 0	2022-05-16

v1.60.0

1 finding

LOW No provenance attestation provenance

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

v1.59.0

1 finding

LOW No provenance attestation provenance

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

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. Consider requesting the maintainer enable provenance via CI/CD.

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

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 2024-03-12, known maintainer) provenance

This version was published by a different npm account (npm-envage) than the most recent previously approved version (jaucourt) on 2024-03-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.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

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 2023-10-12, known maintainer) provenance

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

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