@stoplight/spectral-core
Supply chain provenance
Status for the latest visible version.
Without SLSA provenance there is no cryptographic link between this tarball and the public source, so a manually published version cannot be tied back to a reviewed commit.
Maintainers
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| maintainer-change | maintainer-added | AI (maintainer-change): Known CI bot account, stable across many prior approved versions. | ai | |
| publish-pattern | new-deps-added | AI (publish-pattern): @types/json-schema is a benign type-only dependency swap. | ai | |
| provenance | publisher-changed-stale | AI (provenance): Stale change from 2022, long-unremoved, consistent history since. | ai | |
| phantom-deps | phantom-dep:treeify | AI (phantom-deps): Declared and used for tree output formatting; stable false positive. | ai | |
| phantom-deps | phantom-dep:nanoid | AI (phantom-deps): Likely used internally; established library, no malicious signal. | ai | |
| dependencies | unvetted-dep:simple-eval | AI (dependencies): simple-eval is a documented, pinned runtime dep used for ruleset expression evaluation in Spectral; stable across versions. | ai | |
| phantom-deps | phantom-dep:@stoplight/better-ajv-errors | AI (phantom-deps): Same-org package from Stoplight; phantom-dep finding is a false positive for this well-known package. | ai | |
| phantom-deps | phantom-dep:lodash.topath | AI (phantom-deps): lodash.topath is referenced in config files; its phantom-dep status is a known pattern for this package and not a security concern. | ai | |
| phantom-deps | phantom-dep:@types/es-aggregate-error | AI (phantom-deps): @types/es-aggregate-error is a TypeScript type package declared for type resolution; stable false positive for this package. | ai | |
| phantom-deps | phantom-dep:@types/json-schema | AI (phantom-deps): @types/json-schema is a TypeScript type package declared as a runtime dep for type resolution; stable false positive for this package. | ai |
Versions (showing 50 of 50)
| Version | Deps | Published |
|---|---|---|
| 1.23.1 | 22 / 8 | |
| 1.23.0 | 21 / 8 | |
| 1.22.0 | 21 / 8 | |
| 1.21.0 | 21 / 8 | |
| 1.20.0 | 21 / 8 | |
| 1.19.5 | 21 / 8 | |
| 1.19.4 | 21 / 8 | |
| 1.19.3 | 21 / 8 | |
| 1.19.2 | 21 / 8 | |
| 1.19.1 | 21 / 8 | |
| 1.19.0 | 21 / 8 | |
| 1.18.3 | 21 / 8 | |
| 1.18.2 | 21 / 8 | |
| 1.18.1 | 21 / 8 | |
| 1.18.0 | 21 / 8 | |
| 1.17.0 | 21 / 8 | |
| 1.16.1 | 21 / 8 | |
| 1.16.0 | 21 / 8 | |
| 1.15.2 | 21 / 8 | |
| 1.15.1 | 21 / 8 | |
| 1.15.0 | 22 / 8 | |
| 1.14.2 | 22 / 8 | |
| 1.14.1 | 23 / 8 | |
| 1.14.0 | 23 / 8 | |
| 1.13.1 | 23 / 8 | |
| 1.13.0 | 23 / 8 | |
| 1.12.4 | 21 / 8 | |
| 1.12.3 | 21 / 8 | |
| 1.12.2 | 21 / 8 | |
| 1.12.1 | 21 / 8 | |
| 1.12.0 | 21 / 9 | |
| 1.11.1 | 21 / 9 | |
| 1.11.0 | 21 / 9 | |
| 1.10.2 | 20 / 9 | |
| 1.10.1 | 20 / 9 | |
| 1.10.0 | 20 / 9 | |
| 1.9.0 | 20 / 9 | |
| 1.8.1 | 20 / 9 | |
| 1.8.0 | 20 / 9 | |
| 1.7.0 | 20 / 9 | |
| 1.6.1 | 20 / 9 | |
| 1.6.0 | 20 / 9 | |
| 1.5.1 | 20 / 9 | |
| 1.5.0 | 20 / 11 | |
| 1.4.0 | 19 / 11 | |
| 1.3.0 | 19 / 11 | |
| 1.2.1 | 19 / 11 | |
| 1.2.0 | 21 / 10 | |
| 1.1.0 | 21 / 10 | |
| 1.0.0 | 21 / 10 |
v1.23.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.20.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.19.5
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.19.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.19.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.19.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.19.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.19.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.18.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.18.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.18.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.18.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.17.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.16.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.16.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.15.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.15.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.15.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.14.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.14.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.14.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.13.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.13.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.12.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.12.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.12.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.12.1
2 findingsThis version was published by a different npm account (stoplight-spectral-bot) than the most recent previously approved version (stoplight-devops) on 2022-04-29. It has since remained available on npm for 1544 days without being unpublished, which is inconsistent with an account takeover — those are typically removed by npm shortly after discovery.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.12.0
2 findingsThis version was published by a different npm account (stoplight-spectral-bot) than the most recent previously approved version (stoplight-devops) on 2022-04-18. It has since remained available on npm for 1555 days without being unpublished, which is inconsistent with an account takeover — those are typically removed by npm shortly after discovery.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.11.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.11.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.10.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.10.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.10.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.9.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.8.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.8.0
2 findingsPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
This version was published by a different npm account (stoplight-devops) than the most recent previously approved version (marbemac) on 2021-12-15, but stoplight-devops is listed as a maintainer on prior approved versions (matched on name). This looks like a manual publish by a known maintainer rather than a publisher change. Recorded as INFO for audit trail.
v1.7.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.6.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.6.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.5.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.5.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.4.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.3.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.2.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.2.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.1.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 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.