← Home

@mj-biz-apps/common-actions

12
Versions
License
No
Install Scripts
Verified
Provenance

Supply chain provenance

Status for the latest visible version.

SLSA provenance attestation npm registry signatures gitHead linked

Maintainers

craig.adam.bcethan-bcrkihm-bcanag123jordanfanapourianzygmunt

Accepted risks

Findings the reviewer chose to accept rather than block on.

SourceRuleReasonAccepted byWhen
phantom-deps phantom-dep:zod AI (phantom-deps): Config-file reference; stable for generated action subclass pattern. ai
phantom-deps phantom-dep:@memberjunction/ai AI (phantom-deps): Config-file reference; stable for generated action subclass pattern. ai
phantom-deps phantom-dep:@memberjunction/core AI (phantom-deps): Config-file reference; stable for generated action subclass pattern. ai
phantom-deps phantom-dep:@memberjunction/global AI (phantom-deps): Config-file reference; stable for generated action subclass pattern. ai
phantom-deps phantom-dep:@memberjunction/actions AI (phantom-deps): Config-file reference; stable for generated action subclass pattern. ai
phantom-deps phantom-dep:@memberjunction/aiengine AI (phantom-deps): Config-file reference; stable for generated action subclass pattern. ai
phantom-deps phantom-dep:@memberjunction/actions-base AI (phantom-deps): Config-file reference; stable for generated action subclass pattern. ai
phantom-deps phantom-dep:@memberjunction/core-entities AI (phantom-deps): Config-file reference; stable for generated action subclass pattern. ai
phantom-deps phantom-dep:@memberjunction/core-entities-server AI (phantom-deps): Config-file reference; stable for generated action subclass pattern. ai

Versions (showing 12 of 12)

Version Deps Published
5.30.1 1 / 2
5.30.0 1 / 2
5.29.0 1 / 2
5.28.0 1 / 2
5.27.1 1 / 2
5.27.0 9 / 2
5.26.2 9 / 2
5.26.1 9 / 2
5.26.0 9 / 2
5.17.0 9 / 2
5.10.1 9 / 2
5.4.0 9 / 2

v5.30.1

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.

v5.30.0

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.

v5.29.0

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.

v5.28.0

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.

v5.27.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.

v5.26.2

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.

v5.26.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.

v5.26.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.

v5.17.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.

v5.10.1

1 finding
LOW No provenance attestation provenance

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

v5.4.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.