← Home

@lark-apaas/nestjs-datapaas

npm
11
Versions
—
License
No
Install Scripts
Missing
Provenance

Supply chain provenance

Status for the latest visible version.

No SLSA provenance npm registry signatures gitHead linked

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

bytednpmfengtianran_bytedxiaochuanzhang_bytedbyted.lycoirefduanlikang_byteyuki-bytedanceaihao.0331yanmingjiangchengshihao1prgrmr_byte

Keywords

pluginnestjsservertypescript

Accepted risks

Findings the reviewer chose to accept rather than block on.

SourceRuleReasonAccepted byWhen
install-scripts install-script:postinstall AI (install-scripts): Postinstall applies patches via patch-package; consistent with patches/ dir in published files. ai
phantom-deps phantom-dep:patch-package AI (phantom-deps): patch-package is invoked via scripts config, not direct import; stable false positive. ai
phantom-deps phantom-dep:reflect-metadata AI (phantom-deps): Known NestJS implicit runtime dependency; not directly imported by convention. ai
phantom-deps phantom-dep:@types/pg AI (phantom-deps): Type-only package; not imported at runtime, stable false positive. ai

Versions (showing 11 of 11)

Version Deps Published
1.0.21 3 / 14
1.0.20 3 / 14
1.0.19 3 / 14
1.0.15 4 / 14
1.0.8 4 / 14
1.0.6 4 / 14
1.0.4 4 / 14
1.0.3 4 / 14
1.0.2 4 / 14
1.0.1 4 / 14
1.0.0 4 / 14

v1.0.21

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v1.0.20

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v1.0.15

2 findings
HIGH Package has 'postinstall' script install-scripts

Script: npm run apply-patch

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v1.0.8

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v1.0.6

2 findings
HIGH Package has 'postinstall' script install-scripts

Script: npm run apply-patch

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v1.0.4

2 findings
HIGH Package has 'postinstall' script install-scripts

Script: npm run apply-patch

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v1.0.3

2 findings
HIGH Package has 'postinstall' script install-scripts

Script: npm run apply-patch

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v1.0.2

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v1.0.1

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v1.0.0

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.