@studyportals/cdk-cloudfront-auth
CDK Constructs for adding authentication for a CloudFront Distribution
Supply chain provenance
Status for the latest visible version.
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
Keywords
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| source-diff | obfuscated-file:lib/pre-token-generation-trigger.js | AI (source-diff): tsc-emitted CJS with standard __importStar helpers and aws-cdk-lib requires; compiled output, not obfuscation. | ai | |
| maintainer-change | maintainer-added | AI (maintainer-change): Stale org-wide maintainer transition, long-stable, not a fresh takeover signal. | ai | |
| maintainer-change | maintainer-removed | AI (maintainer-change): Matches same stable transition as maintainer-added. | ai | |
| provenance | publisher-changed-stale | AI (provenance): Publisher change is 953 days stale, inconsistent with account compromise. | ai | |
| semgrep | semgrep:base64-decode | AI (semgrep): Standard URL-safe base64 decode for JWT/cookie handling in CloudFront auth; not a payload obfuscation pattern. | ai | |
| phantom-deps | phantom-dep:@types/aws-lambda | AI (phantom-deps): @types/aws-lambda is a type-only package used by convention in AWS Lambda TypeScript projects; not a real phantom dep. | ai |
Versions (showing 9 of 9)
| Version | Deps | Published |
|---|---|---|
| 1.0.1 | 5 / 28 | |
| 1.0.0 | 5 / 29 | |
| 0.2.7 | 5 / 31 | |
| 0.2.5 | 5 / 31 | |
| 0.2.4 | 3 / 32 | |
| 0.2.3 | 3 / 32 | |
| 0.2.2 | 3 / 32 | |
| 0.2.1 | 3 / 32 | |
| 0.2.0 | 2 / 32 |
v1.0.1
2 findingsNewly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.0
2 findingsNewly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.2.5
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.2.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.2.3
2 findingsThis version was published by a different npm account (prestonvantonder) than the most recent previously approved version (dandobrescu) on 2023-12-13. It has since remained available on npm for 953 days without being unpublished, which is inconsistent with an account takeover — those are typically removed by npm shortly after discovery.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.2.2
2 findingsThis version was published by a different npm account (prestonvantonder) than the most recent previously approved version (dandobrescu) on 2023-12-13. It has since remained available on npm for 953 days without being unpublished, which is inconsistent with an account takeover — those are typically removed by npm shortly after discovery.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.2.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.2.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.