@valtimo/swagger
2
Versions
EUPL-1.2
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, so a manually published version cannot be tied back to a reviewed commit.
Maintainers
devops-ritense
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| source-diff | obfuscated-file:esm2022/lib/swagger-routing.module.mjs | AI (source-diff): Standard Angular ESM2022 compiler output with long lines; not obfuscation. | ai | |
| source-diff | obfuscated-file:esm2022/lib/swagger.component.mjs | AI (source-diff): Standard Angular ESM2022 compiler output with long lines; not obfuscation. | ai | |
| phantom-deps | phantom-dep:tslib | AI (phantom-deps): tslib is a standard implicit TypeScript runtime dependency; stable for this package. | ai | |
| bogus-package | bogus-package | AI (bogus-package): Scoped monorepo package; missing metadata is typical and not indicative of malice. | ai |
v12.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.