@palmetto/nestjs-mongoose
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
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| bogus-package | bogus-package | AI (bogus-package): Internal org package; missing metadata is consistent with private monorepo publishing pattern, not spam/malware. | ai | |
| phantom-deps | phantom-dep:@palmetto/zod-mongoose-schema | AI (phantom-deps): Same-org dependency; phantom-dep heuristic likely misfires on indirect/re-exported usage. | ai | |
| npm-metadata | no-description | AI (npm-metadata): Scoped org package in a monorepo; missing description is a style issue, not a malware indicator. | ai |
Versions (showing 17 of 17)
| Version | Deps | Published |
|---|---|---|
| 3.4.0 | 1 / 13 | |
| 3.3.0 | 1 / 13 | |
| 3.2.2 | 1 / 13 | |
| 3.2.1 | 1 / 13 | |
| 3.2.0 | 1 / 13 | |
| 3.1.0 | 1 / 15 | |
| 3.0.1 | 1 / 15 | |
| 3.0.0 | 1 / 15 | |
| 2.4.2 | 1 / 14 | |
| 2.4.1 | 1 / 14 | |
| 2.4.0 | 1 / 13 | |
| 2.3.2 | 1 / 13 | |
| 2.3.1 | 1 / 10 | |
| 2.3.0 | 2 / 10 | |
| 2.2.7 | 2 / 10 | |
| 2.2.6 | 2 / 10 | |
| 2.2.5 | 2 / 10 |
v3.4.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.3.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.2.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.2.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.2.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.1.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.0.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.0.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.4.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.4.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.4.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.3.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.3.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.3.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.2.7
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. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.2.5
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.