← Home

@stoplight/spectral-parsers

6
Versions
License
No
Install Scripts
Missing
Provenance

Supply chain provenance

Status for the latest visible version.

No SLSA provenance npm registry signatures gitHead linked

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

stoplight-devopsstoplight-spectral-bot

Accepted risks

Findings the reviewer chose to accept rather than block on.

SourceRuleReasonAccepted byWhen
maintainer-change maintainer-added AI (maintainer-change): Known org CI bot transition, verified across many approved packages. ai
maintainer-change maintainer-removed AI (maintainer-change): Consistent with org-wide bot migration, not a takeover. ai
provenance publisher-changed-stale AI (provenance): Long-stable publish (1428d), matches bot with strong track record. ai
publish-pattern new-deps-added AI (publish-pattern): tslib is a standard trusted TS helper library. ai
npm-metadata no-description AI (npm-metadata): Monorepo sub-package from Stoplight; missing description is a cosmetic issue, not a security signal for this well-established package. ai
provenance no-provenance AI (provenance): Stoplight publishes via a bot account without Sigstore provenance; consistent across all versions and not indicative of malicious activity. ai

Versions (showing 6 of 6)

Version Deps Published
1.0.5 4 / 0
1.0.4 4 / 0
1.0.3 4 / 0
1.0.2 4 / 0
1.0.1 4 / 0
1.0.0 3 / 0

v1.0.4

1 finding
INFO No provenance attestation provenance

[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v1.0.3

2 findings
MEDIUM Publisher changed: marbemac → stoplight-spectral-bot (on 2023-07-14, unremoved on npm for 1103d) provenance

This version was published by a different npm account (stoplight-spectral-bot) than the most recent previously approved version (marbemac) on 2023-07-14. It has since remained available on npm for 1103 days without being unpublished, which is inconsistent with an account takeover — those are typically removed by npm shortly after discovery.

INFO No provenance attestation provenance

[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v1.0.2

2 findings
MEDIUM Publisher changed: marbemac → stoplight-spectral-bot (on 2022-08-22, unremoved on npm for 1428d) provenance

This version was published by a different npm account (stoplight-spectral-bot) than the most recent previously approved version (marbemac) on 2022-08-22. It has since remained available on npm for 1428 days without being unpublished, which is inconsistent with an account takeover — those are typically removed by npm shortly after discovery.

INFO No provenance attestation provenance

[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v1.0.1

1 finding
INFO No provenance attestation provenance

[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v1.0.0

1 finding
INFO No provenance attestation provenance

[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.