@quatrain/log
Supply chain provenance
Status for the latest visible version.
Maintainers
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| typosquat | typosquat.levenshtein:glob | AI (typosquat): Scoped @quatrain org package; not a typosquat of glob. | ai | |
| typosquat | typosquat.levenshtein:koa | AI (typosquat): Scoped @quatrain org package; not a typosquat of koa. | ai | |
| typosquat | typosquat.levenshtein:got | AI (typosquat): Scoped @quatrain org package; not a typosquat of got. | ai | |
| typosquat | typosquat.levenshtein:pg | AI (typosquat): Scoped @quatrain org package; not a typosquat of pg. | ai | |
| typosquat | typosquat.levenshtein:joi | AI (typosquat): Scoped @quatrain org package; not a typosquat of joi. | ai | |
| typosquat | typosquat.levenshtein:zod | AI (typosquat): Scoped @quatrain org package; not a typosquat of zod. | ai |
Versions (showing 17 of 17)
| Version | Deps | Published |
|---|---|---|
| 1.2.3 | 2 / 8 | |
| 1.2.2 | 2 / 8 | |
| 1.2.1 | 2 / 8 | |
| 1.1.11 | 2 / 8 | |
| 1.1.10 | 2 / 8 | |
| 1.1.9 | 2 / 8 | |
| 1.1.8 | 2 / 8 | |
| 1.1.7 | 2 / 8 | |
| 1.1.6 | 2 / 8 | |
| 1.1.5 | 2 / 8 | |
| 1.1.4 | 2 / 8 | |
| 1.1.3 | 2 / 8 | |
| 1.1.2 | 2 / 8 | |
| 1.1.1 | 2 / 8 | |
| 1.0.3 | 2 / 9 | |
| 1.0.2 | 1 / 9 | |
| 1.0.1 | 1 / 9 |
v1.2.3
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v1.2.2
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v1.2.1
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v1.1.11
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v1.1.10
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v1.1.9
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.1.8
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.1.7
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.1.6
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.1.5
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.1.4
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.1.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.1.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.1.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.