@feathersjs/generators
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 |
|---|---|---|---|---|
| dependencies | unvetted-dep:@featherscloud/pinion | AI (dependencies): @featherscloud/pinion is the official Pinion scaffolding tool for FeathersJS; its use is documented and intentional in this generators package. Stable across versions. | ai |
Versions (showing 31 of 31)
| Version | Deps | Published |
|---|---|---|
| 5.0.46 | 5 / 32 | |
| 5.0.45 | 5 / 32 | |
| 5.0.44 | 5 / 32 | |
| 5.0.43 | 5 / 32 | |
| 5.0.42 | 5 / 32 | |
| 5.0.41 | 5 / 32 | |
| 5.0.40 | 5 / 32 | |
| 5.0.39 | 5 / 32 | |
| 5.0.37 | 5 / 32 | |
| 5.0.36 | 5 / 32 | |
| 5.0.35 | 5 / 32 | |
| 5.0.34 | 5 / 32 | |
| 5.0.33 | 5 / 32 | |
| 5.0.32 | 5 / 32 | |
| 5.0.31 | 5 / 32 | |
| 5.0.30 | 5 / 32 | |
| 5.0.29 | 5 / 32 | |
| 5.0.28 | 5 / 32 | |
| 5.0.27 | 5 / 32 | |
| 5.0.26 | 5 / 32 | |
| 5.0.25 | 5 / 32 | |
| 5.0.24 | 5 / 32 | |
| 5.0.23 | 5 / 32 | |
| 5.0.22 | 5 / 32 | |
| 5.0.21 | 5 / 32 | |
| 5.0.20 | 5 / 32 | |
| 5.0.19 | 5 / 32 | |
| 5.0.18 | 5 / 32 | |
| 5.0.17 | 5 / 32 | |
| 5.0.16 | 5 / 32 | |
| 5.0.15 | 5 / 32 |
v5.0.33
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.0.32
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.0.31
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.0.30
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.0.29
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.0.28
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.0.27
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.0.26
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.0.25
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v5.0.24
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.0.23
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.0.22
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.0.21
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.0.20
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.0.19
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.0.18
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.0.17
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.0.16
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v5.0.15
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.