@mj-biz-apps/common-server
BizApps Common server bootstrap - GraphQL resolvers and class registrations for the Common business entities Open App
Supply chain provenance
Status for the latest visible version.
Maintainers
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| provenance | publisher-changed | AI (provenance): Publisher changed to GitHub Actions with SLSA provenance attestation; this is the documented CI/CD publishing pattern for this org. | ai | |
| publish-pattern | new-deps-added | AI (publish-pattern): New dep is a same-org sibling at matching version, consistent with coordinated monorepo releases. | ai |
Versions (showing 11 of 11)
| Version | Deps | Published |
|---|---|---|
| 5.30.0 | 4 / 1 | |
| 5.29.0 | 3 / 1 | |
| 5.28.0 | 3 / 1 | |
| 5.27.1 | 3 / 1 | |
| 5.27.0 | 7 / 1 | |
| 5.26.2 | 7 / 1 | |
| 5.26.1 | 7 / 1 | |
| 5.26.0 | 7 / 1 | |
| 5.17.0 | 7 / 1 | |
| 5.10.1 | 7 / 1 | |
| 5.4.0 | 7 / 1 |
v5.30.0
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v5.29.0
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v5.28.0
2 findingsThis version was published by a different npm account than previous versions on 2026-05-13. 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.
v5.27.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.26.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.26.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.26.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.17.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v5.10.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.4.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.