← Home

@atproto/common-web

npm Repository Homepage

Shared web-platform-friendly code for atproto libraries

38
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

atproto

Accepted risks

Findings the reviewer chose to accept rather than block on.

SourceRuleReasonAccepted byWhen
provenance publisher-changed AI (provenance): bluesky-social/atproto migrated to GitHub Actions CI publishing; SLSA attestation confirms legitimate org-controlled release. ai
publish-pattern dormant-publish AI (publish-pattern): Dormancy reflects release cadence of this monorepo package, not account takeover; SLSA provenance confirms CI origin. ai
dependencies unvetted-dep:@atproto/syntax AI (dependencies): Same-monorepo sibling dep from bluesky-social/atproto; stable false positive for this package. ai
dependencies unvetted-dep:@atproto/lex-data AI (dependencies): Same-monorepo sibling dep from bluesky-social/atproto; stable false positive for this package. ai
dependencies unvetted-dep:@atproto/lex-json AI (dependencies): Same-monorepo sibling dep from bluesky-social/atproto; stable false positive for this package. ai

Versions (showing 38 of 38)

Version Deps Published
0.5.6 4 / 1
0.5.5 4 / 1
0.5.4 4 / 1
0.5.3 4 / 1
0.5.2 4 / 1
0.5.1 4 / 1
0.5.0 4 / 2
0.4.21 4 / 2
0.4.20 4 / 2
0.4.19 4 / 2
0.4.18 4 / 2
0.4.17 4 / 2
0.4.16 4 / 2
0.4.15 4 / 2
0.4.14 4 / 2
0.4.13 4 / 2
0.4.12 3 / 2
0.4.11 3 / 2
0.4.10 3 / 2
0.4.9 3 / 2
0.4.8 3 / 2
0.4.7 3 / 2
0.4.6 3 / 2
0.4.5 3 / 2
0.4.4 3 / 2
0.4.3 4 / 2
0.4.2 4 / 2
0.4.1 4 / 2
0.4.0 4 / 2
0.3.2 4 / 2
0.3.1 4 / 1
0.3.0 4 / 1
0.2.4 4 / 0
0.2.3 4 / 0
0.2.2 4 / 0
0.2.1 4 / 0
0.2.0 4 / 0
0.1.0 3 / 0

v0.5.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.5.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.5.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.5.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.4.1

1 finding
LOW No provenance attestation provenance

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

v0.4.0

1 finding
LOW No provenance attestation provenance

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

v0.3.2

1 finding
LOW No provenance attestation provenance

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

v0.3.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.

v0.3.0

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

2 findings
LOW No provenance attestation provenance

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

INFO Publisher changed: pfrazee → dholms (on 2023-07-06, known maintainer) provenance

This version was published by a different npm account (dholms) than the most recent previously approved version (pfrazee) on 2023-07-06, but dholms is listed as a maintainer on prior approved versions (matched on name). This looks like a manual publish by a known maintainer rather than a publisher change. Recorded as INFO for audit trail.

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.