@manifesto-ai/compiler
Manifesto Compiler - MEL (Manifesto Expression Language) to DomainSchema compiler
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 | missing-githead | AI (provenance): No material changes vs prior version; likely a CI/publish environment change, not a supply-chain concern. | ai | |
| phantom-deps | phantom-dep:ink | AI (phantom-deps): Ink is a declared runtime dependency for terminal UI; used indirectly through CLI exports. | ai | |
| phantom-deps | phantom-dep:meow | AI (phantom-deps): Meow is a declared runtime dependency for CLI argument parsing; used indirectly. | ai | |
| phantom-deps | phantom-dep:react | AI (phantom-deps): React is a declared runtime dependency for ink-based terminal UI; used indirectly. | ai | |
| phantom-deps | phantom-dep:ink-spinner | AI (phantom-deps): Ink-spinner is a declared runtime dependency for UI components; used indirectly. | ai | |
| phantom-deps | phantom-dep:ink-select-input | AI (phantom-deps): Ink-select-input is a declared runtime dependency for UI components; used indirectly. | ai |
Versions (showing 27 of 27)
| Version | Deps | Published |
|---|---|---|
| 3.9.0 | 1 / 17 | |
| 3.8.0 | 1 / 17 | |
| 3.7.1 | 1 / 17 | |
| 3.7.0 | 1 / 17 | |
| 3.6.0 | 1 / 17 | |
| 3.5.0 | 1 / 17 | |
| 3.4.0 | 1 / 17 | |
| 3.3.1 | 1 / 17 | |
| 3.3.0 | 1 / 17 | |
| 3.2.0 | 1 / 17 | |
| 3.1.1 | 6 / 12 | |
| 3.1.0 | 6 / 12 | |
| 3.0.0 | 6 / 12 | |
| 1.9.1 | 6 / 13 | |
| 1.9.0 | 6 / 14 | |
| 1.8.3 | 6 / 14 | |
| 1.8.2 | 6 / 14 | |
| 1.8.1 | 6 / 14 | |
| 1.8.0 | 6 / 14 | |
| 1.7.0 | 6 / 14 | |
| 1.6.2 | 5 / 12 | |
| 1.6.1 | 5 / 12 | |
| 1.6.0 | 5 / 12 | |
| 1.5.0 | 5 / 12 | |
| 1.4.1 | 5 / 11 | |
| 1.3.0 | 5 / 11 | |
| 1.0.0 | 5 / 11 |
v3.9.0
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.1
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v3.7.0
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v3.6.0
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v3.5.0
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v3.4.0
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v3.3.1
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v3.3.0
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v3.2.0
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v3.1.1
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v3.1.0
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v3.0.0
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v1.9.1
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v1.9.0
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v1.8.3
2 findingsThis version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: eggplantiny.
Published via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v1.8.2
2 findingsThis version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: eggplantiny.
Published via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v1.8.1
2 findingsThis version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: eggplantiny.
Published via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v1.8.0
2 findingsThis version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: eggplantiny.
Published via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v1.7.0
2 findingsThis version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: eggplantiny.
Published via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v1.6.2
2 findingsThis version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: eggplantiny.
Published via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v1.6.1
2 findingsThis version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: eggplantiny.
Published via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v1.6.0
2 findingsThis version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: eggplantiny.
Published via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v1.5.0
2 findingsThis version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: eggplantiny.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.4.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.3.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.0
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.