@lowdefy/operators
Supply chain provenance
Status for the latest visible version.
Maintainers
Keywords
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| provenance | publisher-changed | AI (provenance): Transition to GitHub Actions publisher is covered by SLSA attestation; consistent with org-level CI/CD automation for the Lowdefy monorepo. | ai | |
| maintainer-change | maintainer-added | AI (maintainer-change): New maintainer is a known Lowdefy contributor; addition is consistent with legitimate team growth in an established monorepo. | ai | |
| publish-pattern | new-deps-added | AI (publish-pattern): Added dep is @lowdefy/errors at matching version 4.6.0 — first-party scoped package, not a suspicious third-party. | ai |
Versions (showing 11 of 11)
| Version | Deps | Published |
|---|---|---|
| 5.3.0 | 2 / 6 | |
| 5.2.0 | 2 / 6 | |
| 5.1.0 | 2 / 6 | |
| 5.0.0 | 2 / 6 | |
| 4.7.3 | 2 / 6 | |
| 4.7.2 | 2 / 6 | |
| 4.7.1 | 2 / 6 | |
| 4.7.0 | 2 / 6 | |
| 4.6.0 | 2 / 6 | |
| 4.5.2 | 1 / 6 | |
| 4.5.1 | 1 / 6 |
v5.3.0
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v5.2.0
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v5.0.0
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v4.7.3
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v4.7.2
2 findingsThis version was published by a different npm account than previous versions on 2026-03-25. This could indicate a legitimate maintainer transition or an account compromise.
Published via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v4.7.1
2 findingsThis version was published by a different npm account than previous versions on 2026-03-19. This could indicate a legitimate maintainer transition or an account compromise.
Published via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v4.7.0
2 findingsThis version was published by a different npm account than previous versions on 2026-03-11. This could indicate a legitimate maintainer transition or an account compromise.
Published via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v4.6.0
2 findingsThis version was published by a different npm account than previous versions on 2026-03-09. This could indicate a legitimate maintainer transition or an account compromise.
Published via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v4.5.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.5.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.