← Home

@atproto/oauth-provider-api

npm Repository Homepage
30
Versions
—
License
No
Install Scripts
Verified
Provenance

Supply chain provenance

Status for the latest visible version.

SLSA provenance attestation npm registry signatures No source commit

Maintainers

dholmspfrazeedevinivyestrattonbaileymatthieu-bluesky

Keywords

atprotooauthprovidertypes

Accepted risks

Findings the reviewer chose to accept rather than block on.

SourceRuleReasonAccepted byWhen
provenance publisher-changed AI (provenance): bluesky-social/atproto monorepo migrated to GitHub Actions publishing with SLSA attestation; expected for all future versions. ai

Versions (showing 30 of 30)

Version Deps Published
0.7.6 3 / 0
0.7.5 3 / 0
0.7.4 3 / 0
0.7.3 3 / 0
0.7.2 3 / 0
0.7.1 3 / 0
0.7.0 3 / 0
0.6.2 2 / 0
0.6.1 2 / 1
0.6.0 2 / 1
0.5.0 2 / 1
0.4.0 2 / 1
0.3.7 2 / 1
0.3.6 2 / 1
0.3.5 2 / 1
0.3.4 2 / 1
0.3.3 2 / 1
0.3.2 2 / 1
0.3.1 2 / 1
0.3.0 2 / 1
0.2.1 2 / 1
0.2.0 2 / 1
0.1.6 2 / 1
0.1.5 2 / 1
0.1.4 2 / 1
0.1.3 2 / 1
0.1.2 2 / 1
0.1.1 2 / 1
0.1.0 2 / 1
0.0.1 1 / 1

v0.7.6

1 finding
INFO Has SLSA provenance attestation provenance

Published via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.

v0.7.5

1 finding
INFO Has SLSA provenance attestation provenance

Published via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.

v0.7.4

1 finding
INFO Has SLSA provenance attestation provenance

Published via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.

v0.7.3

1 finding
INFO Has SLSA provenance attestation provenance

Published via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.

v0.1.1

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v0.1.0

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v0.0.1

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.