@open-keystone/auth-passport
Provides Social Authentication Strategies based on PassportJS.
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 |
|---|---|---|---|---|
| publish-pattern | dormant-publish | AI (publish-pattern): SLSA provenance attestation confirms CI/CD publish; dormancy risk is mitigated by verified build provenance. | ai | |
| dependencies | unvetted-dep:passport-twitter | AI (dependencies): passport-twitter is a well-known PassportJS strategy; stable dependency for this auth package. | ai | |
| dependencies | unvetted-dep:passport-wordpress | AI (dependencies): passport-wordpress is a known PassportJS strategy; consistent with this package's social auth purpose. | ai | |
| provenance | no-provenance | AI (provenance): Consistent across all versions of this package; no provenance is standard for this publisher. | ai | |
| phantom-deps | phantom-dep:passport-wordpress | AI (phantom-deps): Declared as a peer/optional strategy dep; not directly imported but legitimately listed for consumers. | ai | |
| phantom-deps | phantom-dep:@open-keystone/session | AI (phantom-deps): Same org scope; used indirectly via framework internals, stable false positive for this package. | ai |
Versions (showing 27 of 27)
| Version | Deps | Published |
|---|---|---|
| 7.0.30 | 10 / 0 | |
| 7.0.29 | 10 / 0 | |
| 7.0.28 | 10 / 0 | |
| 7.0.26 | 10 / 0 | |
| 7.0.25 | 10 / 0 | |
| 7.0.24 | 10 / 0 | |
| 7.0.23 | 10 / 0 | |
| 7.0.21 | 10 / 0 | |
| 7.0.20 | 10 / 0 | |
| 7.0.17 | 10 / 0 | |
| 7.0.16 | 10 / 0 | |
| 7.0.15 | 10 / 0 | |
| 7.0.14 | 10 / 0 | |
| 7.0.13 | 10 / 0 | |
| 7.0.12 | 10 / 0 | |
| 7.0.11 | 10 / 0 | |
| 7.0.10 | 10 / 0 | |
| 7.0.9 | 10 / 0 | |
| 7.0.8 | 10 / 0 | |
| 7.0.7 | 10 / 0 | |
| 7.0.6 | 10 / 0 | |
| 7.0.5 | 10 / 0 | |
| 7.0.4 | 10 / 0 | |
| 7.0.3 | 10 / 0 | |
| 7.0.2 | 10 / 0 | |
| 7.0.1 | 10 / 0 | |
| 7.0.0 | 10 / 0 |
v7.0.30
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v7.0.29
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v7.0.28
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v7.0.26
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v7.0.25
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v7.0.24
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v7.0.23
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v7.0.21
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v7.0.20
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v7.0.17
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v7.0.16
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v7.0.15
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v7.0.14
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v7.0.13
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v7.0.12
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v7.0.11
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v7.0.10
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v7.0.9
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v7.0.8
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v7.0.7
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v7.0.6
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v7.0.5
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v7.0.4
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v7.0.3
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v7.0.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v7.0.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v7.0.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.