@feathersjs/rest-client
REST client services for different Ajax libraries
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
Keywords
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| dependencies | unvetted-dep:@feathersjs/errors | AI (dependencies): First-party FeathersJS ecosystem package published by the same maintainer; unvetted status is a pipeline gap, not a real risk. | ai | |
| dependencies | unvetted-dep:@feathersjs/commons | AI (dependencies): First-party FeathersJS ecosystem package published by the same maintainer; unvetted status is a pipeline gap, not a real risk. | ai | |
| dependencies | unvetted-dep:@feathersjs/feathers | AI (dependencies): First-party FeathersJS ecosystem package published by the same maintainer; unvetted status is a pipeline gap, not a real risk. | ai | |
| dependencies | unvetted-dep:@types/superagent | AI (dependencies): DefinitelyTyped type definitions for superagent; well-known, widely used, no security concern. | ai | |
| phantom-deps | phantom-dep:@types/superagent | AI (phantom-deps): @types/superagent is a type-only dependency; not directly imported at runtime but legitimately declared for TypeScript consumers of this package. | ai |
Versions (showing 12 of 12)
| Version | Deps | Published |
|---|---|---|
| 5.0.45 | 5 / 15 | |
| 5.0.44 | 5 / 15 | |
| 5.0.43 | 5 / 15 | |
| 5.0.42 | 5 / 15 | |
| 5.0.41 | 5 / 15 | |
| 5.0.40 | 5 / 15 | |
| 5.0.39 | 5 / 15 | |
| 5.0.37 | 5 / 15 | |
| 5.0.36 | 5 / 15 | |
| 5.0.35 | 5 / 15 | |
| 5.0.34 | 5 / 15 | |
| 4.5.19 | 3 / 16 |
v5.0.45
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 (marshallswain) than the most recent previously approved version (daffl) on 2026-06-04, but marshallswain 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.
v5.0.44
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v5.0.43
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.0.42
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.0.41
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.0.40
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v5.0.39
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v5.0.37
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v5.0.36
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v5.0.35
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.0.34
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.5.19
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.