@ackplus/nest-auth
Powerful CRUD operations for NestJS with TypeORM - automatic REST endpoints, advanced filtering, relations, pagination, and more
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 |
|---|---|---|---|---|
| provenance | no-provenance | AI (provenance): No provenance is common (~88% of npm); no other risk signals present for this package. | ai | |
| phantom-deps | phantom-dep:tslib | AI (phantom-deps): tslib is a known implicit TypeScript runtime dep; stable false positive for this package. | ai | |
| phantom-deps | phantom-dep:reflect-metadata | AI (phantom-deps): reflect-metadata is a standard NestJS implicit dep; stable false positive. | ai | |
| phantom-deps | phantom-dep:class-transformer | AI (phantom-deps): class-transformer is commonly used implicitly via NestJS decorators; stable false positive. | ai | |
| phantom-deps | phantom-dep:@nestjs/platform-express | AI (phantom-deps): Referenced in config files as expected for NestJS packages; stable false positive. | ai | |
| phantom-deps | phantom-dep:qs | AI (phantom-deps): qs is declared as a direct dependency in package.json; phantom-dep is a false positive. | ai | |
| phantom-deps | phantom-dep:pluralize | AI (phantom-deps): pluralize is declared as a direct dependency in package.json; phantom-dep is a false positive. | ai |
Versions (showing 23 of 23)
| Version | Deps | Published |
|---|---|---|
| 1.1.68 | 10 / 30 | |
| 1.1.29 | 10 / 29 | |
| 1.1.28 | 11 / 3 | |
| 1.1.27 | 11 / 3 | |
| 1.1.26 | 11 / 3 | |
| 1.1.25 | 11 / 3 | |
| 1.1.24 | 11 / 3 | |
| 1.1.23 | 11 / 3 | |
| 1.1.22 | 11 / 3 | |
| 1.1.21 | 11 / 3 | |
| 1.1.20 | 11 / 3 | |
| 1.1.19 | 11 / 3 | |
| 1.1.18 | 11 / 3 | |
| 1.1.17 | 11 / 3 | |
| 1.1.16 | 11 / 3 | |
| 1.1.15 | 11 / 3 | |
| 1.1.14 | 11 / 3 | |
| 1.1.13 | 11 / 3 | |
| 1.1.12 | 11 / 3 | |
| 1.1.11 | 11 / 3 | |
| 1.1.10 | 11 / 3 | |
| 1.1.9 | 19 / 0 | |
| 1.1.0 | 17 / 0 |
v1.1.29
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.1.28
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.1.27
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.1.26
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.1.25
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.1.24
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.1.23
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.1.22
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.1.21
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.1.20
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.1.19
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.1.18
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.1.17
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.1.16
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.1.15
2 findings[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
This version was published by a different npm account (ajaykhandla) than the most recent previously approved version (ckhandla94) on 2025-12-05, but ajaykhandla 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.
v1.1.14
2 findings[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
This version was published by a different npm account (ajaykhandla) than the most recent previously approved version (ckhandla94) on 2025-12-05, but ajaykhandla 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.
v1.1.13
2 findings[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
This version was published by a different npm account (ajaykhandla) than the most recent previously approved version (ckhandla94) on 2025-12-05, but ajaykhandla 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.
v1.1.12
2 findings[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
This version was published by a different npm account (ajaykhandla) than the most recent previously approved version (ckhandla94) on 2025-12-04, but ajaykhandla 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.
v1.1.11
2 findings[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
This version was published by a different npm account (ajaykhandla) than the most recent previously approved version (ckhandla94) on 2025-11-29, but ajaykhandla 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.
v1.1.10
2 findings[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
This version was published by a different npm account (ajaykhandla) than the most recent previously approved version (ckhandla94) on 2025-11-29, but ajaykhandla 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.
v1.1.9
2 findings[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
This version was published by a different npm account (ajaykhandla) than the most recent previously approved version (ckhandla94) on 2025-11-29, but ajaykhandla 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.
v1.1.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.