@eventuras/fides-auth-next
Next.js bindings for @eventuras/fides-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 compensates; missing gitHead is a metadata gap, not a security risk for this package. | ai | |
| phantom-deps | phantom-dep:@eventuras/typescript-config | AI (phantom-deps): Build/type config dep from same org monorepo; not imported at runtime by design. | ai | |
| dependencies | unvetted-dep:@eventuras/logger | AI (dependencies): Same-org monorepo sibling dependency; consistent with the eventuras/losol ecosystem across versions. | ai |
v0.2.0
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: GitHub Actions.
Published via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.1.12
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: GitHub Actions.
Published via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.1.11
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.1.5
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.