@stoplight/spectral-functions
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 |
|---|---|---|---|---|
| phantom-deps | phantom-dep:json-schema-traverse | AI (phantom-deps): Used transitively via ajv; intentional direct dep in this JSON-schema linting lib. | ai | |
| phantom-deps | phantom-dep:tslib | AI (phantom-deps): Known implicit TS runtime helper dependency. | ai | |
| phantom-deps | phantom-dep:@stoplight/types | AI (phantom-deps): Same-org type package, implicit dep, benign. | ai | |
| dependencies | unvetted-dep:@stoplight/spectral-runtime | AI (dependencies): First-party @stoplight scoped dependency from the same organization; not a third-party risk. | ai | |
| dependencies | unvetted-dep:@stoplight/json | AI (dependencies): First-party @stoplight scoped dependency from the same organization; not a third-party risk. | ai | |
| dependencies | unvetted-dep:@stoplight/better-ajv-errors | AI (dependencies): First-party @stoplight scoped dependency from the same organization; not a third-party risk. | ai | |
| dependencies | unvetted-dep:@stoplight/spectral-core | AI (dependencies): First-party @stoplight scoped dependency from the same organization; not a third-party risk. | ai | |
| dependencies | unvetted-dep:@stoplight/spectral-formats | AI (dependencies): First-party @stoplight scoped dependency from the same organization; not a third-party risk. | ai |
Versions (showing 29 of 29)
| Version | Deps | Published |
|---|---|---|
| 1.10.5 | 12 / 1 | |
| 1.10.4 | 12 / 1 | |
| 1.10.3 | 11 / 1 | |
| 1.10.2 | 11 / 1 | |
| 1.10.1 | 11 / 1 | |
| 1.10.0 | 11 / 1 | |
| 1.9.4 | 11 / 1 | |
| 1.9.3 | 11 / 1 | |
| 1.9.2 | 11 / 1 | |
| 1.9.1 | 11 / 1 | |
| 1.9.0 | 11 / 1 | |
| 1.8.0 | 11 / 1 | |
| 1.7.2 | 11 / 1 | |
| 1.7.1 | 11 / 1 | |
| 1.7.0 | 12 / 1 | |
| 1.6.2 | 12 / 1 | |
| 1.6.1 | 12 / 1 | |
| 1.6.0 | 12 / 1 | |
| 1.5.2 | 12 / 1 | |
| 1.5.1 | 12 / 1 | |
| 1.5.0 | 12 / 1 | |
| 1.4.0 | 12 / 1 | |
| 1.3.0 | 13 / 1 | |
| 1.2.1 | 13 / 1 | |
| 1.2.0 | 13 / 1 | |
| 1.1.2 | 13 / 1 | |
| 1.1.1 | 13 / 1 | |
| 1.1.0 | 13 / 1 | |
| 1.0.0 | 13 / 1 |
v1.10.5
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.10.4
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-spectral-bot) than the most recent previously approved version (stoplight-devops) on 2026-06-30, but stoplight-spectral-bot 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.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.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.9.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.9.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.9.1
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. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.8.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.7.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.7.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.7.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-08-03. It has since remained available on npm for 1448 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.6.2
2 findingsThis version was published by a different npm account (stoplight-spectral-bot) than the most recent previously approved version (stoplight-devops) on 2022-07-28. It has since remained available on npm for 1454 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.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.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.5.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.5.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.4.0
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.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.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.1.1
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.