@defra-fish/payment-mop-up-job
Process incomplete web-sales
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 |
|---|---|---|---|---|
| license | uncommon-license:SEE LICENSE IN LICENSE | AI (license): DEFRA internal package with custom license file; consistent across versions. | ai | |
| dependencies | unvetted-dep:@defra-fish/connectors-lib | AI (dependencies): Sibling package from the same DEFRA monorepo (rod-licensing); consistently co-versioned, not a third-party risk. | ai |
Versions (showing 12 of 12)
| Version | Deps | Published |
|---|---|---|
| 1.71.0 | 5 / 0 | |
| 1.70.1 | 5 / 0 | |
| 1.70.0 | 5 / 0 | |
| 1.69.0 | 5 / 0 | |
| 1.68.0 | 5 / 0 | |
| 1.67.0 | 5 / 0 | |
| 1.66.0 | 5 / 0 | |
| 1.65.0 | 5 / 0 | |
| 1.64.0 | 5 / 0 | |
| 1.63.0 | 5 / 0 | |
| 1.62.0 | 5 / 0 | |
| 1.61.0 | 5 / 0 |
v1.71.0
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v1.70.1
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v1.70.0
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v1.68.0
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v1.67.0
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v1.66.0
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v1.65.0
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v1.64.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.63.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.62.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.61.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.