@contractspec/module.alpic
Alpic MCP and ChatGPT App hosting helpers
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 | no-provenance | AI (provenance): Consistent across all versions of this package; no provenance is common and not a risk signal here. | ai | |
| phantom-deps | phantom-dep:zod | AI (phantom-deps): zod is declared in dependencies and used via framework/config; phantom-dep is a stable false positive for this package. | ai |
Versions (showing 50 of 50)
| Version | Deps | Published |
|---|---|---|
| 3.7.29 | 5 / 3 | |
| 3.7.28 | 5 / 3 | |
| 3.7.27 | 5 / 3 | |
| 3.7.26 | 5 / 3 | |
| 3.7.25 | 5 / 3 | |
| 3.7.24 | 5 / 3 | |
| 3.7.23 | 5 / 3 | |
| 3.7.22 | 5 / 3 | |
| 3.7.21 | 5 / 3 | |
| 3.7.20 | 5 / 3 | |
| 3.7.19 | 5 / 3 | |
| 3.7.18 | 5 / 3 | |
| 3.7.17 | 5 / 3 | |
| 3.7.16 | 5 / 3 | |
| 3.7.15 | 5 / 3 | |
| 3.7.14 | 5 / 3 | |
| 3.7.12 | 5 / 3 | |
| 3.7.10 | 5 / 3 | |
| 3.7.7 | 5 / 3 | |
| 3.7.6 | 5 / 3 | |
| 3.7.5 | 5 / 3 | |
| 3.7.4 | 5 / 3 | |
| 3.7.3 | 5 / 3 | |
| 3.7.1 | 5 / 3 | |
| 3.7.0 | 5 / 3 | |
| 3.6.0 | 5 / 3 | |
| 3.5.5 | 5 / 3 | |
| 3.5.4 | 5 / 3 | |
| 3.5.3 | 4 / 3 | |
| 3.5.2 | 4 / 3 | |
| 3.5.0 | 4 / 3 | |
| 3.4.3 | 4 / 3 | |
| 3.4.2 | 4 / 3 | |
| 3.4.1 | 4 / 3 | |
| 3.4.0 | 4 / 3 | |
| 3.3.0 | 4 / 3 | |
| 3.2.0 | 4 / 3 | |
| 3.1.0 | 4 / 3 | |
| 3.0.0 | 4 / 3 | |
| 2.9.0 | 4 / 3 | |
| 2.8.0 | 4 / 3 | |
| 2.7.0 | 4 / 3 | |
| 2.6.0 | 5 / 3 | |
| 2.4.0 | 5 / 3 | |
| 2.2.0 | 5 / 3 | |
| 2.0.0 | 5 / 3 | |
| 1.62.0 | 5 / 3 | |
| 1.60.0 | 5 / 3 | |
| 1.58.0 | 5 / 3 | |
| 1.57.0 | 5 / 4 |
v3.7.29
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v3.7.28
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v3.7.17
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v3.7.16
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v3.7.15
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v3.7.14
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v3.7.12
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v3.7.10
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v3.7.7
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v3.7.6
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v3.7.5
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v3.7.4
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v3.7.3
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v3.7.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.7.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.6.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.5.5
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.5.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.5.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.5.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.5.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.4.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.4.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.4.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.4.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.3.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.2.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.1.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.0.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.9.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.8.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.7.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.6.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.4.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.2.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.0.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.62.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.60.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.58.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.57.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.