pretty-quick
Get Pretty Quick
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 |
|---|---|---|---|---|
| email-domain | unclaimed-email:azz | AI (email-domain): '@azz' in the author field is a social handle placeholder, not a real email address. No actual email domain 'azz' is in use; this is a stable false positive for this package. | ai |
Versions (showing 40 of 40)
| Version | Deps | Published |
|---|---|---|
| 4.2.2 | 7 / 0 | |
| 4.2.1 | 7 / 0 | |
| 4.2.0 | 7 / 0 | |
| 4.1.1 | 7 / 0 | |
| 4.1.0 | 7 / 0 | |
| 4.0.0 | 7 / 0 | |
| 3.3.1 | 7 / 0 | |
| 3.3.0 | 7 / 0 | |
| 3.2.1 | 7 / 0 | |
| 3.2.0 | 6 / 0 | |
| 3.1.3 | 6 / 12 | |
| 3.1.2 | 6 / 12 | |
| 3.1.1 | 6 / 12 | |
| 3.1.0 | 6 / 12 | |
| 3.0.2 | 6 / 12 | |
| 3.0.1 | 6 / 12 | |
| 3.0.0 | 6 / 12 | |
| 2.0.2 | 6 / 12 | |
| 2.0.1 | 6 / 12 | |
| 2.0.0 | 6 / 11 | |
| 1.11.1 | 6 / 12 | |
| 1.11.0 | 6 / 12 | |
| 1.10.0 | 6 / 12 | |
| 1.9.0 | 6 / 12 | |
| 1.8.1 | 5 / 12 | |
| 1.8.0 | 5 / 12 | |
| 1.7.0 | 5 / 12 | |
| 1.6.0 | 5 / 12 | |
| 1.5.1 | 5 / 12 | |
| 1.5.0 | 5 / 12 | |
| 1.4.1 | 5 / 12 | |
| 1.4.0 | 5 / 12 | |
| 1.3.0 | 5 / 12 | |
| 1.2.3 | 5 / 12 | |
| 1.2.2 | 5 / 12 | |
| 1.2.1 | 5 / 12 | |
| 1.2.0 | 5 / 12 | |
| 1.1.0 | 4 / 12 | |
| 1.0.0 | 4 / 10 | |
| 0.0.0 | 4 / 10 |
v4.2.2
2 findingsMaintainer email '@azz' uses domain 'azz' which has no DNS records. An attacker could register this domain to hijack the maintainer identity.
Published via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v4.2.1
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v4.2.0
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v4.1.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.1.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.0.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.3.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.3.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.2.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.2.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.1.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.1.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.1.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.1.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.0.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.0.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.0.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.