@feathersjs/configuration
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:@types/config | AI (dependencies): @types/config is the official TypeScript types for the 'config' package, a legitimate runtime dep for this configuration module. Stable false positive for this package. | ai | |
| phantom-deps | phantom-dep:@types/config | AI (phantom-deps): @types/config is a type-only dependency used by convention; not being directly imported is expected behavior for this package. | ai |
Versions (showing 12 of 12)
| Version | Deps | Published |
|---|---|---|
| 5.0.45 | 5 / 6 | |
| 5.0.44 | 5 / 6 | |
| 5.0.43 | 5 / 6 | |
| 5.0.42 | 5 / 6 | |
| 5.0.41 | 5 / 6 | |
| 5.0.40 | 5 / 6 | |
| 5.0.39 | 5 / 6 | |
| 5.0.37 | 5 / 6 | |
| 5.0.36 | 5 / 6 | |
| 5.0.35 | 5 / 6 | |
| 5.0.34 | 5 / 6 | |
| 4.5.19 | 3 / 8 |
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.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. Consider requesting the maintainer enable provenance via CI/CD.
v5.0.39
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.0.37
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
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.