@stoplight/json-schema-sampler
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
Keywords
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): Stoplight org team roster update, consistent across sibling packages. | ai | |
| maintainer-change | maintainer-removed | AI (maintainer-change): Same org roster churn, not a takeover indicator. | ai | |
| provenance | publisher-changed-stale | AI (provenance): Long-stable publish under same org, not consistent with takeover. | ai | |
| phantom-deps | phantom-dep:@types/json-schema | AI (phantom-deps): Types package used by convention, not directly imported. | ai | |
| npm-metadata | suspicious-initial-version | AI (npm-metadata): 0.0.0 is this package's genuine first npm release, not a throwaway squat. | ai |
Versions (showing 7 of 7)
| Version | Deps | Published |
|---|---|---|
| 0.3.0 | 2 / 46 | |
| 0.2.3 | 2 / 46 | |
| 0.2.2 | 2 / 46 | |
| 0.2.1 | 2 / 46 | |
| 0.2.0 | 2 / 46 | |
| 0.1.0 | 2 / 46 | |
| 0.0.0 | 1 / 43 |
v0.2.3
2 findingsThis version was published by a different npm account (eadams-stoplight) than the most recent previously approved version (paulatulis) on 2022-11-17. It has since remained available on npm for 1339 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.
v0.2.2
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 (mmiask) than the most recent previously approved version (paulatulis) on 2021-10-13, but mmiask 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.
v0.2.1
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 (paulatulis) than the most recent previously approved version (p0lip) on 2021-09-21, but paulatulis 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.
v0.2.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.