← Home

@atproto/oauth-types

npm Repository Homepage

OAuth typing & validation library

33
Versions
MIT
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

atprotooauthtypesisomorphic

Accepted risks

Findings the reviewer chose to accept rather than block on.

SourceRuleReasonAccepted byWhen
provenance publisher-changed AI (provenance): bluesky-social/atproto monorepo switched to GitHub Actions publishing; SLSA attestation confirms CI provenance. ai
publish-pattern dormant-publish AI (publish-pattern): Dormancy reflects monorepo release cadence, not account takeover; SLSA attestation corroborates legitimacy. ai
semgrep semgrep:shady-links-raw-ip AI (semgrep): Loopback IPs (127.0.0.1, ::1) in OAuth redirect URI constants are RFC 8252-compliant; stable false positive for this package. ai

Versions (showing 33 of 33)

Version Deps Published
0.7.5 3 / 0
0.7.4 3 / 0
0.7.3 3 / 0
0.7.2 3 / 0
0.7.1 3 / 1
0.7.0 3 / 1
0.6.3 3 / 1
0.6.2 3 / 1
0.6.1 3 / 1
0.6.0 3 / 1
0.5.2 3 / 1
0.5.1 3 / 1
0.5.0 3 / 1
0.4.2 3 / 1
0.4.1 2 / 1
0.4.0 2 / 1
0.3.1 2 / 1
0.3.0 2 / 1
0.2.8 2 / 1
0.2.7 2 / 1
0.2.6 2 / 1
0.2.5 2 / 1
0.2.4 2 / 1
0.2.3 2 / 1
0.2.2 2 / 1
0.2.1 2 / 1
0.2.0 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

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.2.6

1 finding
LOW No provenance attestation provenance

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

v0.2.5

1 finding
LOW No provenance attestation provenance

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

v0.2.4

1 finding
LOW No provenance attestation provenance

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

v0.2.3

1 finding
LOW No provenance attestation provenance

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

v0.2.2

1 finding
LOW No provenance attestation provenance

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

v0.2.1

1 finding
LOW No provenance attestation provenance

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

v0.2.0

1 finding
LOW No provenance attestation provenance

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

v0.1.5

1 finding
LOW No provenance attestation provenance

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

v0.1.4

1 finding
LOW No provenance attestation provenance

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

v0.1.3

1 finding
LOW No provenance attestation provenance

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

v0.1.2

1 finding
LOW No provenance attestation provenance

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

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. Only ~12% of npm packages have provenance, so this is common but not ideal.