@quatrain/auth
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 |
|---|---|---|---|---|
| provenance | missing-githead | AI (provenance): SLSA provenance attestation present; missing gitHead is a minor publish-env change, not a supply-chain risk for this package. | ai | |
| dependencies | unvetted-dep:@quatrain/api | AI (dependencies): @quatrain/api is a sibling package in the same Quatrain monorepo; intra-org dep, not a suspicious third-party addition. | ai | |
| license | copyleft-license:AGPL-3.0-only | AI (license): Package is intentionally AGPL-3.0; stable license choice for this org's packages. | ai |
Versions (showing 17 of 17)
| Version | Deps | Published |
|---|---|---|
| 1.2.3 | 3 / 10 | |
| 1.2.2 | 2 / 10 | |
| 1.2.1 | 2 / 10 | |
| 1.1.31 | 2 / 10 | |
| 1.1.30 | 2 / 10 | |
| 1.1.29 | 2 / 10 | |
| 1.1.28 | 2 / 10 | |
| 1.1.27 | 2 / 10 | |
| 1.1.26 | 2 / 10 | |
| 1.1.25 | 2 / 10 | |
| 1.1.24 | 2 / 10 | |
| 1.1.23 | 2 / 10 | |
| 1.1.22 | 2 / 10 | |
| 1.1.21 | 2 / 10 | |
| 1.1.20 | 2 / 10 | |
| 1.1.19 | 2 / 10 | |
| 1.1.17 | 2 / 10 |
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
2 findingsThis version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: crapougnax.
Published via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v1.1.31
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v1.1.30
2 findingsThis version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: crapougnax.
Published via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v1.1.29
2 findingsThis version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: crapougnax.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.1.28
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.1.27
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.1.26
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.1.25
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.1.24
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.1.23
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.1.22
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.1.21
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.1.20
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.1.19
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.1.17
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.