@maioradv/nestjs-core
NestJS helpers by MaiorADV
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-peer-dep:handlebars | AI (dependencies): Peer dependency on stable handlebars; consumer controls version. | ai | |
| publish-pattern | dormant-publish | AI (publish-pattern): Publisher has clean track record (23 approved, 0 rejected); new deps are all established NestJS ecosystem packages. | ai | |
| publish-pattern | new-deps-added | AI (publish-pattern): All 21 added deps are well-known NestJS/AWS/logging packages; no suspicious or novel packages introduced. | ai | |
| dependencies | unvetted-dep:nest-winston | AI (dependencies): nest-winston is a well-known NestJS Winston integration; stable false positive for this package. | ai | |
| dependencies | unvetted-dep:handlebars | AI (dependencies): handlebars is a widely-used templating library; stable false positive for this package. | ai | |
| provenance | no-provenance | AI (provenance): Publisher consistently publishes without provenance; not a security concern for this package. | ai | |
| phantom-deps | phantom-dep:file-type | AI (phantom-deps): Declared as runtime dep and peer dep; phantom-dep heuristic false positive for this package. | ai | |
| phantom-deps | phantom-dep:@nestjs/platform-express | AI (phantom-deps): Declared as runtime dep and peer dep; phantom-dep heuristic false positive for this package. | ai |
Versions (showing 16 of 16)
| Version | Deps | Published |
|---|---|---|
| 2.3.5 | 24 / 7 | |
| 2.3.2 | 23 / 7 | |
| 2.2.9 | 23 / 7 | |
| 2.2.6 | 23 / 7 | |
| 2.2.4 | 23 / 7 | |
| 2.2.2 | 22 / 7 | |
| 2.2.1 | 22 / 7 | |
| 2.2.0 | 22 / 7 | |
| 2.1.9 | 22 / 7 | |
| 2.1.8 | 1 / 28 | |
| 2.1.5 | 22 / 6 | |
| 2.1.4 | 22 / 6 | |
| 2.1.2 | 22 / 6 | |
| 2.0.4 | 22 / 6 | |
| 2.0.3 | 22 / 6 | |
| 2.0.0 | 22 / 6 |
v2.3.5
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.3.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.2.9
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.2.6
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.2.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.2.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.2.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.2.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.1.9
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.1.8
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.1.5
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.1.4
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.1.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.0.4
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.0.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.0.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.