@aws/dynamodb-auto-marshaller
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 |
|---|---|---|---|---|
| maintainer-change | maintainer-added | AI (maintainer-change): Long-standing AWS SDK team maintainer roster change, no malicious behavior. | ai | |
| provenance | publisher-changed-stale | AI (provenance): Stale 2017 publisher change, long-stable, not a takeover pattern. | ai | |
| publish-pattern | new-deps-added | AI (publish-pattern): tslib is a trivial, ubiquitous TS runtime helper. | ai |
Versions (showing 11 of 11)
| Version | Deps | Published |
|---|---|---|
| 0.7.1 | 1 / 6 | |
| 0.7.0 | 1 / 8 | |
| 0.6.1 | 1 / 6 | |
| 0.6.0 | 1 / 6 | |
| 0.5.0 | 1 / 6 | |
| 0.4.1 | 1 / 6 | |
| 0.4.0 | 1 / 6 | |
| 0.3.0 | 1 / 6 | |
| 0.2.1 | 1 / 6 | |
| 0.2.0 | 1 / 5 | |
| 0.1.0 | 0 / 5 |
v0.7.0
2 findingsThis version was published by a different npm account (jsq) than the most recent previously approved version (aws-sdk-bot) on 2018-07-10. It has since remained available on npm for 2935 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.6.1
2 findingsThis version was published by a different npm account (jsq) than the most recent previously approved version (aws-sdk-bot) on 2018-06-28. It has since remained available on npm for 2947 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.6.0
2 findingsThis version was published by a different npm account (jsq) than the most recent previously approved version (aws-sdk-bot) on 2018-06-16. It has since remained available on npm for 2959 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.5.0
2 findingsThis version was published by a different npm account (jsq) than the most recent previously approved version (aws-sdk-bot) on 2018-05-17. It has since remained available on npm for 2989 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.4.1
2 findingsThis version was published by a different npm account (jsq) than the most recent previously approved version (aws-sdk-bot) on 2018-04-24. It has since remained available on npm for 3012 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.4.0
2 findingsThis version was published by a different npm account (jsq) than the most recent previously approved version (aws-sdk-bot) on 2018-01-08. It has since remained available on npm for 3118 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.3.0
2 findingsThis version was published by a different npm account (jsq) than the most recent previously approved version (aws-sdk-bot) on 2017-12-22. It has since remained available on npm for 3135 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
2 findingsThis version was published by a different npm account (jsq) than the most recent previously approved version (aws-sdk-bot) on 2017-12-01. It has since remained available on npm for 3156 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.0
2 findingsThis version was published by a different npm account (jsq) than the most recent previously approved version (aws-sdk-bot) on 2017-11-28. It has since remained available on npm for 3159 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.1.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.