@aligent/cdk-static-hosting
 : Standard tsc-compiled CDK construct output; long lines are TypeScript compiler artifacts, not obfuscation. | ai | |
| source-diff | obfuscated-file:lib/path-remap.js | AI (source-diff): Standard tsc-compiled CDK construct output; long lines are TypeScript compiler artifacts, not obfuscation. | ai | |
| source-diff | obfuscated-file:lib/static-hosting.js | AI (source-diff): Standard tsc-compiled CDK construct output; long lines are TypeScript compiler artifacts, not obfuscation. | ai | |
| provenance | publisher-changed | AI (provenance): Transition to GitHub Actions publisher is consistent with CI/CD automation; backed by SLSA provenance attestation. | ai | |
| maintainer-change | maintainer-removed | AI (maintainer-change): Maintainer removal aligns with org-level CI/CD automation takeover of publishing; no malicious indicators present. | ai |
Versions (showing 19 of 19)
| Version | Deps | Published |
|---|---|---|
| 2.11.10 | 2 / 12 | |
| 2.11.9 | 2 / 12 | |
| 2.11.8 | 2 / 12 | |
| 2.11.7 | 2 / 12 | |
| 2.11.6 | 2 / 12 | |
| 2.11.5 | 2 / 12 | |
| 2.11.4 | 2 / 12 | |
| 2.11.3 | 2 / 12 | |
| 2.11.1 | 2 / 12 | |
| 2.11.0 | 2 / 12 | |
| 2.10.0 | 2 / 12 | |
| 2.9.3 | 2 / 12 | |
| 2.9.2 | 2 / 12 | |
| 2.9.1 | 2 / 12 | |
| 2.9.0 | 2 / 12 | |
| 2.8.2 | 2 / 12 | |
| 2.8.1 | 2 / 9 | |
| 2.8.0 | 2 / 9 | |
| 2.7.3 | 2 / 9 |
v2.11.10
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v2.11.9
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v2.11.8
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v2.11.7
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v2.11.5
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v2.11.4
2 findingsThis version was published by a different npm account than previous versions on 2026-02-20. This could indicate a legitimate maintainer transition or an account compromise.
Published via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v2.11.3
2 findingsThis version was published by a different npm account than previous versions on 2026-02-11. This could indicate a legitimate maintainer transition or an account compromise.
Published via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v2.11.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.11.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.10.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.9.3
4 findingsNewly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Newly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Newly 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.
v2.9.2
4 findingsNewly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Newly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Newly 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.
v2.9.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.9.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.8.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.8.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.8.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.7.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.