@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 |
|---|---|---|---|---|
| dependencies | unvetted-dep:@quatrain/http | AI (dependencies): Same-org @quatrain/* package; consistent with existing dependency pattern in this monorepo. | ai | |
| 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 34 of 34)
| Version | Deps | Published |
|---|---|---|
| 1.2.4 | 4 / 10 | |
| 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 | |
| 1.1.16 | 2 / 10 | |
| 1.1.15 | 2 / 10 | |
| 1.1.14 | 1 / 10 | |
| 1.1.13 | 1 / 10 | |
| 1.1.12 | 1 / 10 | |
| 1.1.10 | 1 / 10 | |
| 1.1.9 | 1 / 10 | |
| 1.1.8 | 1 / 10 | |
| 1.1.7 | 1 / 10 | |
| 1.1.6 | 1 / 10 | |
| 1.1.5 | 1 / 10 | |
| 1.1.4 | 1 / 10 | |
| 1.0.3 | 0 / 11 | |
| 1.0.2 | 0 / 11 | |
| 1.0.1 | 0 / 11 | |
| 1.0.0 | 0 / 11 |
v1.1.16
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.1.15
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.1.14
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.1.13
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.1.12
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.1.10
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.1.9
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.1.8
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.1.7
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.1.6
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.1.5
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.1.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.