jspm-github
jspm GitHub endpoint
Supply chain provenance
Status for the latest visible version.
Without SLSA provenance there is no cryptographic link between this tarball and the public source — the axios compromise (March 2026) relied on exactly this gap.
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): crisptrutski added as maintainer on a well-established jspm project by trusted publisher guybedford; consistent with legitimate project contributor onboarding. | ai | |
| maintainer-change | maintainer-removed | AI (maintainer-change): guybedford is the primary jspm ecosystem maintainer; removal of crisptrutski appears to be routine cleanup, not a takeover signal. | ai | |
| publish-pattern | new-deps-added | AI (publish-pattern): netrc is a legitimate dependency for reading .netrc credentials — appropriate for a GitHub endpoint package. Addition is contextually justified. | ai | |
| provenance | no-provenance | AI (provenance): Provenance is absent on ~88% of npm packages; not a disqualifier for established publishers with strong track records. | ai | |
| phantom-deps | phantom-dep:github | AI (phantom-deps): github is explicitly declared in package.json as a git URL dependency; phantom-dep rule is a false positive for this intentional pattern. | ai | |
| npm-metadata | no-description | AI (npm-metadata): Long-established package (4599 days old) with 100 versions; missing description is a cosmetic issue, not a malware indicator. | ai | |
| npm-metadata | url-dep:github | AI (npm-metadata): The git URL points to the publisher's own fork of node-github, consistent with jspm's early tooling patterns. This is a stable, intentional dependency choice for this package. | ai | |
| semgrep | semgrep:child-process-import | AI (semgrep): jspm-github legitimately executes git commands via child_process; this is core functionality for a GitHub endpoint package, not a malicious signal. | ai | |
| dependencies | unvetted-dep:expand-tilde | AI (dependencies): expand-tilde is a common path utility; appropriate dependency for this package and stable false positive. | ai | |
| dependencies | unvetted-dep:request | AI (dependencies): request is a standard HTTP client dependency appropriate for a GitHub endpoint package; stable false positive for this package. | ai |
Versions (showing 26 of 26)
| Version | Deps | Published |
|---|---|---|
| 0.14.10 | 10 / 1 | |
| 0.13.26 | 11 / 1 | |
| 0.13.22 | 11 / 1 | |
| 0.13.21 | 11 / 1 | |
| 0.13.14 | 11 / 1 | |
| 0.13.10 | 11 / 1 | |
| 0.13.9 | 11 / 1 | |
| 0.13.7 | 11 / 1 | |
| 0.13.3 | 10 / 1 | |
| 0.12.0 | 10 / 0 | |
| 0.11.6 | 10 / 0 | |
| 0.11.5 | 9 / 0 | |
| 0.11.3 | 9 / 0 | |
| 0.11.1 | 9 / 0 | |
| 0.10.7 | 9 / 0 | |
| 0.10.6 | 9 / 0 | |
| 0.10.0 | 9 / 0 | |
| 0.9.6 | 7 / 0 | |
| 0.9.1 | 6 / 0 | |
| 0.8.0 | 6 / 0 | |
| 0.5.1 | 7 / 0 | |
| 0.5.0 | 6 / 0 | |
| 0.2.2 | 5 / 0 | |
| 0.0.6 | 5 / 0 | |
| 0.0.2 | 5 / 0 | |
| 0.0.1 | 2 / 0 |
v0.14.10
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.13.26
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.13.22
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.13.21
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.13.14
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.13.10
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.13.9
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.13.7
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.13.3
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.12.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.11.6
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.11.5
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.11.3
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.11.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.10.7
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.10.6
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.10.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.9.6
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.9.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.8.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.5.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.5.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.2.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.6
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.