@atproto/repo MIT 53 versions

@atproto/repo

npm Repository Homepage

atproto repo and MST implementation

53

Versions

MIT

License

No

Install Scripts

Attested

Provenance

Supply chain provenance

Status for the latest visible version.

SLSA provenance attestation (unverified) npm registry signatures No source commit

Maintainers

dholmspfrazeedevinivyestrattonbaileymatthieu-bluesky

Keywords

atprotomst

Accepted risks

Findings the reviewer chose to accept rather than block on.

Source	Rule	Reason	Accepted by	When
source-diff	encoded-string-file:tests/mst.test.ts	AI (source-diff): Long string is a test fixture for key-length validation, not an encoded payload.	ai	2026/05/11
provenance	publisher-changed	AI (provenance): Transition from devinivy to GitHub Actions CI/CD is legitimate; backed by SLSA provenance attestation.	ai	2026/05/04
publish-pattern	dormant-publish	AI (publish-pattern): Dormancy followed by CI/CD migration is expected for atproto monorepo; SLSA attestation confirms integrity.	ai	2026/05/04
dependencies	unvetted-dep:@atproto/common	AI (dependencies): Sibling package in the bluesky-social/atproto monorepo; same publisher and trust chain.	ai	2026/04/29
dependencies	unvetted-dep:@atproto/crypto	AI (dependencies): Sibling package in the bluesky-social/atproto monorepo; same publisher and trust chain.	ai	2026/04/29

Versions (showing 53 of 53)

Version	Deps	Published
0.10.6	8 / 1	2026-07-09
0.10.5	8 / 1	2026-07-07
0.10.4	8 / 1	2026-07-06
0.10.3	8 / 1	2026-07-01
0.10.2	8 / 1	2026-06-25
0.10.1	8 / 1	2026-06-16
0.10.0	8 / 2	2026-05-19
0.9.1	8 / 2	2026-04-09
0.9.0	8 / 2	2026-03-26
0.8.13	9 / 2	2026-03-18
0.8.12	9 / 2	2025-12-08
0.8.11	9 / 2	2025-11-24
0.8.10	9 / 2	2025-09-26
0.8.9	9 / 2	2025-09-09
0.8.8	9 / 2	2025-08-29
0.8.7	9 / 2	2025-08-27
0.8.6	9 / 2	2025-08-20
0.8.5	9 / 2	2025-07-11
0.8.4	9 / 2	2025-06-24
0.8.3	9 / 2	2025-06-19
0.8.2	9 / 2	2025-06-17
0.8.1	9 / 2	2025-05-05
0.8.0	9 / 2	2025-04-02
0.7.3	9 / 2	2025-04-01
0.7.2	9 / 2	2025-03-20
0.7.1	9 / 2	2025-03-07
0.7.0	9 / 2	2025-02-24
0.6.5	9 / 2	2025-02-13
0.6.4	9 / 2	2025-02-05
0.6.3	9 / 2	2025-02-01
0.6.2	9 / 2	2025-01-07
0.6.1	9 / 2	2025-01-07
0.6.0	9 / 2	2024-12-11
0.5.5	9 / 2	2024-11-13
0.5.4	9 / 2	2024-11-08
0.5.3	9 / 1	2024-10-01
0.5.2	9 / 1	2024-09-27
0.5.1	9 / 1	2024-09-11
0.5.0	9 / 1	2024-09-05
0.4.3	9 / 1	2024-08-27
0.4.2	9 / 1	2024-08-12
0.4.1	9 / 1	2024-07-12
0.4.0	9 / 1	2024-03-18
0.3.9	11 / 0	2024-03-13
0.3.8	11 / 0	2024-02-29
0.3.7	11 / 0	2024-02-16
0.3.6	11 / 0	2023-12-01
0.3.5	11 / 0	2023-11-21
0.3.4	11 / 0	2023-11-02
0.3.3	11 / 0	2023-10-27
0.3.2	11 / 0	2023-09-27
0.3.1	11 / 0	2023-09-15
0.3.0	10 / 0	2023-08-30

v0.10.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.10.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.10.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.10.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.8.0

1 finding

LOW No provenance attestation provenance

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

v0.7.3

1 finding

LOW No provenance attestation provenance

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

v0.7.2

1 finding

LOW No provenance attestation provenance

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

v0.7.1

1 finding

LOW No provenance attestation provenance

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

v0.7.0

1 finding

LOW No provenance attestation provenance

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

v0.6.5

1 finding

LOW No provenance attestation provenance

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

v0.6.4

1 finding

LOW No provenance attestation provenance

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

v0.6.3

1 finding

LOW No provenance attestation provenance

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

v0.6.2

1 finding

LOW No provenance attestation provenance

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

v0.6.1

1 finding

LOW No provenance attestation provenance

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

v0.6.0

1 finding

LOW No provenance attestation provenance

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

v0.5.5

1 finding

LOW No provenance attestation provenance

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

v0.5.4

1 finding

LOW No provenance attestation provenance

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

v0.5.3

1 finding

LOW No provenance attestation provenance

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

v0.5.2

1 finding

LOW No provenance attestation provenance

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

v0.5.1

1 finding

LOW No provenance attestation provenance

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

v0.5.0

1 finding

LOW No provenance attestation provenance

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

v0.4.3

1 finding

LOW No provenance attestation provenance

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

v0.4.2

1 finding

LOW No provenance attestation provenance

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

v0.4.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.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.9

1 finding

LOW No provenance attestation provenance

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

v0.3.8

1 finding

LOW No provenance attestation provenance

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

v0.3.7

1 finding

LOW No provenance attestation provenance

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

v0.3.6

1 finding

LOW No provenance attestation provenance

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

v0.3.5

1 finding

LOW No provenance attestation provenance

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

v0.3.4

1 finding

LOW No provenance attestation provenance

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

v0.3.3

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

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: devinivy → dholms (on 2023-09-15, known maintainer) provenance

This version was published by a different npm account (dholms) than the most recent previously approved version (devinivy) on 2023-09-15, 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.3.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.