@contractspec/tool.create-contractspec-plugin
CLI tool for creating ContractSpec plugins from templates
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 |
|---|---|---|---|---|
| phantom-deps | phantom-dep:zod | AI (phantom-deps): Declared dependency; used by CLI tool for schema validation. | ai | |
| phantom-deps | phantom-dep:chalk | AI (phantom-deps): Declared dependency; used by CLI tool for terminal output formatting. | ai | |
| phantom-deps | phantom-dep:fs-extra | AI (phantom-deps): Declared dependency; used by CLI tool for file operations. | ai | |
| phantom-deps | phantom-dep:mustache | AI (phantom-deps): Declared dependency; used by CLI tool for template rendering. | ai | |
| phantom-deps | phantom-dep:commander | AI (phantom-deps): Declared dependency; used by CLI tool for command-line argument parsing. | ai | |
| phantom-deps | phantom-dep:@inquirer/prompts | AI (phantom-deps): Declared dependency; used by CLI tool for interactive prompts. | ai |
Versions (showing 67 of 67)
| Version | Deps | Published |
|---|---|---|
| 3.8.21 | 8 / 5 | |
| 3.8.20 | 8 / 5 | |
| 3.8.19 | 8 / 5 | |
| 3.8.18 | 8 / 5 | |
| 3.8.17 | 8 / 5 | |
| 3.8.16 | 8 / 5 | |
| 3.8.15 | 8 / 5 | |
| 3.8.14 | 8 / 5 | |
| 3.8.13 | 8 / 5 | |
| 3.8.12 | 8 / 5 | |
| 3.8.11 | 8 / 5 | |
| 3.8.10 | 8 / 5 | |
| 3.8.9 | 8 / 5 | |
| 3.8.8 | 8 / 5 | |
| 3.8.7 | 8 / 5 | |
| 3.8.6 | 8 / 5 | |
| 3.8.5 | 8 / 5 | |
| 3.8.3 | 8 / 5 | |
| 3.8.0 | 8 / 5 | |
| 3.7.6 | 8 / 5 | |
| 3.7.5 | 8 / 5 | |
| 3.7.4 | 8 / 5 | |
| 3.7.3 | 8 / 5 | |
| 3.7.1 | 8 / 5 | |
| 3.7.0 | 8 / 5 | |
| 3.6.0 | 8 / 5 | |
| 3.5.5 | 8 / 5 | |
| 3.5.4 | 8 / 5 | |
| 3.5.3 | 8 / 5 | |
| 3.5.2 | 8 / 5 | |
| 3.5.0 | 8 / 5 | |
| 3.4.3 | 8 / 5 | |
| 3.4.2 | 8 / 5 | |
| 3.4.1 | 8 / 5 | |
| 3.4.0 | 8 / 5 | |
| 3.3.0 | 8 / 5 | |
| 3.2.0 | 8 / 5 | |
| 3.1.1 | 8 / 5 | |
| 3.0.0 | 8 / 5 | |
| 2.9.1 | 8 / 5 | |
| 2.9.0 | 8 / 5 | |
| 2.8.0 | 8 / 5 | |
| 2.7.0 | 8 / 5 | |
| 2.6.0 | 8 / 5 | |
| 2.5.0 | 8 / 5 | |
| 2.4.0 | 8 / 5 | |
| 2.3.0 | 8 / 5 | |
| 2.2.0 | 8 / 5 | |
| 2.1.1 | 8 / 5 | |
| 2.1.0 | 8 / 5 | |
| 2.0.0 | 8 / 5 | |
| 1.62.0 | 8 / 5 | |
| 1.61.0 | 8 / 5 | |
| 1.60.0 | 8 / 5 | |
| 1.59.0 | 8 / 5 | |
| 1.58.0 | 8 / 5 | |
| 1.57.0 | 8 / 6 | |
| 1.56.1 | 8 / 6 | |
| 1.56.0 | 8 / 6 | |
| 1.55.0 | 8 / 6 | |
| 1.54.0 | 8 / 6 | |
| 1.53.0 | 8 / 6 | |
| 1.52.0 | 8 / 6 | |
| 1.51.0 | 8 / 6 | |
| 1.50.0 | 8 / 6 | |
| 1.49.0 | 8 / 6 | |
| 1.48.1 | 8 / 6 |
v3.8.21
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v3.8.20
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v3.8.19
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v3.8.9
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v3.8.8
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v3.8.7
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v3.8.6
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v3.8.5
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v3.8.3
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v3.8.0
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.1
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.1
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. Consider requesting the maintainer enable provenance via CI/CD.
v2.6.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.5.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.4.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.3.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.2.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.1.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.1.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.0.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.62.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.61.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.60.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.59.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.58.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.57.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.56.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.56.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.55.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.54.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.53.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.52.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.51.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.50.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.49.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.48.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.