@accordproject/concerto-linter
Concerto Linter using Spectral rulesets
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 | publisher-changed | AI (provenance): Transition from personal account to GitHub Actions CI/CD is expected for this org; SLSA attestation confirms legitimate pipeline. | ai | |
| publish-pattern | dormant-publish | AI (publish-pattern): SLSA provenance attestation confirms CI/CD publish; dormancy explained by project cadence, not account takeover indicators. | ai | |
| dependencies | unvetted-dep:@stoplight/spectral-cli | AI (dependencies): @stoplight/spectral-cli is a well-known, widely-used API linting tool from Stoplight; not a risk for this package. | ai | |
| dependencies | unvetted-dep:@accordproject/concerto-metamodel | AI (dependencies): Same org scope as this package (@accordproject); stable sibling dependency, not a risk. | ai | |
| phantom-deps | phantom-dep:@accordproject/concerto-metamodel | AI (phantom-deps): Same-org dependency; phantom-dep heuristic fires on transitive/config usage, stable false positive for this package. | ai | |
| phantom-deps | phantom-dep:ajv | AI (phantom-deps): ajv declared as direct dep and used in config; phantom-dep false positive for this package. | ai | |
| phantom-deps | phantom-dep:@accordproject/concerto-core | AI (phantom-deps): Same-org dependency; phantom-dep heuristic fires on transitive/config usage, stable false positive for this package. | ai |
Versions (showing 12 of 12)
| Version | Deps | Published |
|---|---|---|
| 4.1.4 | 9 / 8 | |
| 4.1.3 | 9 / 8 | |
| 4.1.2 | 9 / 8 | |
| 4.1.0 | 9 / 8 | |
| 4.0.3 | 9 / 8 | |
| 4.0.2 | 8 / 8 | |
| 4.0.1 | 8 / 8 | |
| 4.0.0 | 8 / 8 | |
| 3.26.0 | 6 / 8 | |
| 3.25.7 | 6 / 8 | |
| 3.25.6 | 6 / 8 | |
| 3.25.0 | 6 / 8 |
v4.1.4
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v4.1.3
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v4.1.2
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v4.1.0
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v4.0.3
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v4.0.2
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v4.0.0
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v3.26.0
2 findingsThis version was published by a different npm account than previous versions on 2026-03-18. 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.
v3.25.7
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v3.25.6
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v3.25.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.